In addition to my last response I have noticed that when I reboot the problem server it will apparently apply the group policy without issues for 15 minutes or so and then will fail to do so from that point forward. When viewing the userenv log file after a reboot and after giving the gpupdate command, it shows no 59 errors and nothing shows up in the event log. Wait about 15 minutes or so and the event log shows the 1054 error and the userenv log shows the 59 error.
Donavon -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Donavon Yelton Sent: Monday, January 15, 2007 10:44 AM To: ActiveDir@mail.activedir.org Subject: RE: [ActiveDir] 1054 Error (Windows cannot contact DC - Group Policy) Hi Steve, When running nltest /dsgetdc:<domainname> on the problem member server I get the following (NOTE: I ran it twice, once for DOMAIN and again for DOMAIN.LOCAL which is the full name. I noticed that the flags for each are different): C:\Documents and Settings\supervisor>nltest /dsgetdc:domain DC: \\ATHENA Address: \\192.168.1.6 Dom Guid: 0c93e47c-f1a8-4e05-916c-d6e6670f2c96 Dom Name: DOMAIN Forest Name: domain.local Dc Site Name: Default-First-Site-Name Our Site Name: Default-First-Site-Name Flags: PDC GC DS LDAP KDC TIMESERV GTIMESERV WRITABLE DNS_FOREST CLOSE_S ITE The command completed successfully C:\Documents and Settings\supervisor>nltest /dsgetdc:domain.local DC: \\athena.domain.local Address: \\192.168.1.6 Dom Guid: 0c93e47c-f1a8-4e05-916c-d6e6670f2c96 Dom Name: domain.local Forest Name: domain.local Dc Site Name: Default-First-Site-Name Our Site Name: Default-First-Site-Name Flags: PDC GC DS LDAP KDC TIMESERV GTIMESERV WRITABLE DNS_DC DNS_DOMAIN DNS_FOREST CLOSE_SITE The command completed successfully I have already tried to disable slow link detection on the problem member server however I had to do so by going into gpedit.msc and setting it to 0 as that registry location doesn't exist on Windows 2003 Server R2 x64 (when searching on Google I could not find the location of this key in this version of windows). Also of note is that I have went so far as forcing 100Mb connection on the active NIC on the problem member server but it also did not solve the issue so I set it back to auto. The NIC in the machine is a 1Gb card. This morning I removed it from the domain and added it back. The group policy seemed to work for a bit but after about 15 minutes of tests I got the 1054 error again. Strangely if I do a gpupdate /force I don't get the 1054 error in the event log and instead get a 1704 (Security policy in the Group policy objects has been applied successfully). Donavon -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steve Linehan Sent: Monday, January 15, 2007 10:20 AM To: ActiveDir@mail.activedir.org Subject: RE: [ActiveDir] 1054 Error (Windows cannot contact DC - Group Policy) It appears that you are having problems with slow link detection from the log below. You can try disabling it on the client to see if that corrects the problem by following the steps in this article for disabling slow link detection: http://support.microsoft.com/kb/910206/en-us. I would not recommend this as a long term solution but simply a troubleshooting step to see if it is indeed a problem with Slow link detection. I believe the LDAP error 59 later in the log is spurious and caused by the abortion of slow link detection. However just in case you can also validate that you can successfully make a DSGetDCName() call by using nltest /dsgetdc:<domainname> and see if it returns the same error on the machine in question? Let us know the results of each test an maybe we can provide some additional insight. Thanks, -Steve ________________________________ From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Donavon Yelton [EMAIL PROTECTED] Sent: Monday, January 15, 2007 6:37 AM To: ActiveDir@mail.activedir.org Subject: [ActiveDir] 1054 Error (Windows cannot contact DC - Group Policy) I have a new member server (Windows 2003 R2 x64) in my Windows 2003 domain (not R2). My setup contains two Windows 2003 DC's, both being DNS servers with the PDC being a WINS server. I have been working on a problem with a 1054 error in the event log for the mentioned Windows 2003 R2 x64 member server that has been added recently. Error 1054 as a refresh is the following: Windows cannot obtain the domain controller name for your computer network. (An unexpected network error occurred. ). Group Policy processing aborted. I worked on solutions all day Friday to no avail so I am seeking assistance on this matter. No other member of the domain has this error that I am aware of. SRV records for the DC's are in the DNS and is setup correctly on the troubled member server. I have looked through WINS and saw no apparent problems with its setup either. I have updated the drivers and firmware for the network cards in the new member server and in both DC's. I will say that I have a strange issue on my local PC from time to time (and I'll assume this happens on other domain member's PC's as well) where I cannot logon to Active Directory Users and Computers by using the domain as a locator, however I am able to go into it if I selectively choose a specific DC from the list. When running netdiag on the problem member server I see no issues and when running netdiag and dcdiag on the DC's I see no issues. I am able to get to SYSVOL from the problem member server by going to \\domain\sysvol\domain<file://\\domain\sysvol\domain>. I have turned on logging of USERENV on the problem member server and I get this in the log: USERENV(37c.66c) 07:00:02:294 PingComputer: PingBufferSize set as 2048 USERENV(37c.66c) 07:00:02:294 PingComputer: Adapter speed 1000000000 bps USERENV(37c.66c) 07:00:02:294 PingComputer: First time: 2482 USERENV(37c.66c) 07:00:02:294 PingComputer: Second time: 2482 USERENV(37c.66c) 07:00:02:294 PingComputer: First and second times match. USERENV(37c.66c) 07:00:02:294 PingComputer: First time: 2482 USERENV(37c.66c) 07:00:02:294 PingComputer: Second time: 2482 USERENV(37c.66c) 07:00:02:294 PingComputer: First and second times match. USERENV(37c.66c) 07:00:02:294 PingComputer: First time: 2482 USERENV(37c.66c) 07:00:02:294 PingComputer: Second time: 2482 USERENV(37c.66c) 07:00:02:294 PingComputer: First and second times match. USERENV(37c.66c) 07:00:02:294 PingComputer: No data available USERENV(37c.66c) 07:00:02:294 ProcessGPOs: DSGetDCName failed with 59. I am very close to calling Microsoft to help resolve the issue but I thought I'd run it by you guys. I'm in the unfortunate position of being the only IT personnel here and having to be a jack of all trades as it would be. I typically have no problem solving an issue like this, especially with the help of Google but this problem just goes beyond stumping me. Any help is appreciated. Donavon Yelton Manager of Information Systems Carpenter Industries, Inc. (704) 743-2068 http://www.dennis-carpenter.com<http://www.dennis-carpenter.com/> ________________________________ THIS MESSAGE CONTAINS INFORMATION INTENDED ONLY FOR THE USE OF THE INDIVIDUAL OR ENTITY NAMED ABOVE. IF THE READER OF THIS MESSAGE IS NOT THE RECIPIENT, OR THE EMPLOYEE OR AGENT RESPONSIBLE TO DELIVER IT TO THE INTENDED RECIPIENT, YOU ARE HEREBY NOTIFIED THAT ANY DISSEMINATION, DISTRIBUTION OR COPYING OF THIS MESSAGE IS STRICTLY PROHIBITED. IF YOU HAVE RECEIVED THIS MESSAGE IN ERROR, PLEASE NOTIFY US IMMEDIATELY VIA RETURN-E-MAIL AND DELETE THIS MESSAGE FROM YOUR SYSTEM. THANK YOU. Carpenter Industries, Inc. ________________________________ List info : http://www.activedir.org/List.aspx List FAQ : http://www.activedir.org/ListFAQ.aspx List archive: http://www.activedir.org/ma/default.aspx List info : http://www.activedir.org/List.aspx List FAQ : http://www.activedir.org/ListFAQ.aspx List archive: http://www.activedir.org/ma/default.aspx List info : http://www.activedir.org/List.aspx List FAQ : http://www.activedir.org/ListFAQ.aspx List archive: http://www.activedir.org/ma/default.aspx
