host master 
United States
Member since
9/26/2007
Registered Users
Posts: 14
 |
| 9/26/2007 05:43 PM |
|
SBS2003 sp2, getting the :
Windows cannot obtain the domain controller name for your computer network. (An unexpected network error occurred. ). Group Policy processing aborted.
event log error.
After rebooting, error goes away for about 24 hours. I have the latest drivers for the embedded network card (Nvidia NForce 65.2.1.0).
There is a single network connection, and the NS is set to 127.0.0.1. There are no other member servers, just 5 XPpro clients. The server's connected to a Dell 2508 8-port unmanaged Gigabit switch
I've read a number of technotes about possible issues contributing to this warning. The last thing I tried was locking the card to "Force 100 Full Duplex", but I'm still getting the error every 10 minutes or so.
I would ignore the problem but one XP client is unable to authenticate with the server when this happens, and loses access to network resources. The other clients don't seem to be affected, but they have Exchange-account-connected Outlook 2003 running all the time, so they may be maintaining a "heartbeat" with the server.
Any suggestions would be appreciated!
|
|
|
|
|
|
Mariette Knap
The Netherlands
Member since
3/24/2005
Forum Admins
Posts: 12952
|
| 9/26/2007 06:45 PM |
|
Please, post an ipconfig /all from the server and a workstation. Open a command prompt by opening Start -> Run from the Start Menu and type cmd. From the command prompt type ipconfig /all >ip.txt. Attach this file to your answer.
|
|
| Mariëtte Knap Smallbizserver.Net Administrator | Mission accomplished. We have joined the branch office to our SBS 2003 Headquarters and have the same user experience on the branch office as we have on our local network at the Headquarters. Want to know how? Signup up for a subscription and get instant access to the article series 'How to add an additional Domain Controller from a remote office to the SBS domain' |
|
|
|
|
host master
United States
Member since
9/26/2007
Registered Users
Posts: 14
|
| 9/27/2007 05:49 PM |
|
Thanks for helping. Attached is the IP config for both machines.
Two things to note...
Firstly, on the server, I originally had the Primary DNS set to 192.168.1.200, and I tried setting it to 127.0.0.1 to see if the problems went away (they didn't).
Secondly, I see that the DNS is not set correctly on the client computer. I only noticed when I exported the ipconfig and looked at it.
Would the client's DNS config be causing errors to show up in the server's log, or are these unrelated?
|
 Attachment: 1927494791771.txt
|
|
|
|
|
Mariette Knap
The Netherlands
Member since
3/24/2005
Forum Admins
Posts: 12952
|
| 9/27/2007 06:28 PM |
|
Please, read:
Your network setup is wrong and DNS on your server must point to the server itself. Did you use the CEICW to configure the server for internet access?
|
|
| Mariëtte Knap Smallbizserver.Net Administrator | Mission accomplished. We have joined the branch office to our SBS 2003 Headquarters and have the same user experience on the branch office as we have on our local network at the Headquarters. Want to know how? Signup up for a subscription and get instant access to the article series 'How to add an additional Domain Controller from a remote office to the SBS domain' |
|
|
|
|
host master
United States
Member since
9/26/2007
Registered Users
Posts: 14
|
| 9/27/2007 07:29 PM |
|
Hi: As I mentioned in the previous post, I had the DNS on the server pointing to itself, at 192.168.1.200, and I was receiving the same error. I only changed it to 127.0.0.1 to see if that made any difference (it didn't). I have set it back to 192.168.1.200 and I'm still receiving the errors.
I did use the CEICW, and the server is working properly in all respects except for the "Windows cannot obtain the domain controller name for your computer network. (An unexpected network error occurred. ). Group Policy processing aborted." error.
Is there something else wrong with the configuration? Bear in mind that this is a single-NIC configuration, with the router itself (192.168.1.1) providing DHCP for the network. The server has a fixed IP of 192.168.1.200.
I updated the DNS on the XP Pro client to point at the SBS server, but I'm still getting the errors in the error log.
|
|
|
|
|
|
Mariette Knap
The Netherlands
Member since
3/24/2005
Forum Admins
Posts: 12952
|
| 9/27/2007 07:53 PM |
|
The fact that your clients get a foreign DNS server makes me believe that you entered wrong information somewhere. Can you rerun the CEICW and when asked for DNS servers fill in the IP addresses of your ISP DNS servers?
You should have the SBS setup as the DHCP and DNS server. Disable the DHCP server on that router and change your SBS to hand out IP addresses.
|
|
| Mariëtte Knap Smallbizserver.Net Administrator | Mission accomplished. We have joined the branch office to our SBS 2003 Headquarters and have the same user experience on the branch office as we have on our local network at the Headquarters. Want to know how? Signup up for a subscription and get instant access to the article series 'How to add an additional Domain Controller from a remote office to the SBS domain' |
|
|
|
|
host master
United States
Member since
9/26/2007
Registered Users
Posts: 14
|
| 9/27/2007 08:30 PM |
|
Thanks for your reply. To better explain:
This network was set up several years ago. The router is connected directly to a DSL modem, and it has always been the DHCP server. All the workstations were in a Workgroup, and were configured to get IPs from the router's DHCP server.
I added the SBS server a few weeks ago. When I went through the config, I elected NOT to install the DHCP server since one was already running on the network. I then went through all the other configuration settings for a single-NIC server configuration.
I then created user accounts for each person on the SBS server.
I then went to each XP Pro workstation, had it join the domain, and logged in with the domain user. I connected Outlook 2003 to the SBS/Exchange server account for that user, and imported their PST files from the local user account.
On most of the computers, I updated the network configuration to point the primary DNS at the SBS server. I didn't see any harm in letting them continue to get their IP from the router's DHCP server (and in any case, this doesn't appear to be related to the problem I'm experiencing in this thread).
On one workstation, I neglected to change the primary DNS to the SBS server, although I have done so now.
I am still getting the 1054 error on the server however, even with the primary DNS set as it's own IP address.
There are only a few computers on this subnet, and I can easily just change them to fixed IPs instead of using any DHCP server, but I really don't see how it's related to the errors on the SBS server.
|
|
|
|
|
|
host master
United States
Member since
9/26/2007
Registered Users
Posts: 14
|
| 9/27/2007 08:39 PM |
|
Posted By Mariette Knap on 9/27/2007 07:53 PM
The fact that your clients get a foreign DNS server makes me believe that you entered wrong information somewhere. Can you rerun the CEICW and when asked for DNS servers fill in the IP addresses of your ISP DNS servers?
You should have the SBS setup as the DHCP and DNS server. Disable the DHCP server on that router and change your SBS to hand out IP addresses.
|
|
|
|
|
|
Mariette Knap
The Netherlands
Member since
3/24/2005
Forum Admins
Posts: 12952
|
| 9/27/2007 11:08 PM |
|
Posted By host master on 9/27/2007 08:39 PM
Sorry, I forget to add that, yes, the ISP's DNS servers are configured on the SBS server.
Where did you enter those? Not on the Nic I hope...?
|
|
| Mariëtte Knap Smallbizserver.Net Administrator | Mission accomplished. We have joined the branch office to our SBS 2003 Headquarters and have the same user experience on the branch office as we have on our local network at the Headquarters. Want to know how? Signup up for a subscription and get instant access to the article series 'How to add an additional Domain Controller from a remote office to the SBS domain' |
|
|
|
|
host master
United States
Member since
9/26/2007
Registered Users
Posts: 14
|
| 9/27/2007 11:48 PM |
|
Hi Mariette: Thanks for continuing to try to help, but we seem to be talking in circles unfortunately. I've already sent you the ipconfig output for the server, and you can see the ISP's NS is NOT configured on the NIC, just the local address of the SBS server.
I've also already said that I ran the connection wizard when I first installed SBS, and the only "non-standard" thing I did in the configuration was leave the DHCP server on the router. I barely remember now, but I believe at one point during setup I was prompted to enter the ISP DNS, and I did.
Here's the server's ipconfig as it's currently set:
Windows IP Configuration
Host Name . . . . . . . . . . . . : sbs-server1
Primary Dns Suffix . . . . . . . : mydomain.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : mydomain.local
Ethernet adapter Server Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NVIDIA nForce Networking Controller
Physical Address. . . . . . . . . : 00-19-DB-4B-83-B0
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.200
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 127.0.0.1
Primary WINS Server . . . . . . . : 192.168.1.200
|
|
|
|
|
|
Mariette Knap
The Netherlands
Member since
3/24/2005
Forum Admins
Posts: 12952
|
|
host master
United States
Member since
9/26/2007
Registered Users
Posts: 14
|
| 9/28/2007 07:06 PM |
|
Hi Mariette:
I reset the Primary DNS back to the server IP:
Windows IP Configuration
Host Name . . . . . . . . . . . . : sbs-server1
Primary Dns Suffix . . . . . . . : mydomain.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : mydomain.local
Ethernet adapter Server Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NVIDIA nForce Networking Controller
Physical Address. . . . . . . . . : 00-19-DB-4B-83-B0
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.200
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.200
Primary WINS Server . . . . . . . : 192.168.1.200
I went through the entire 1054 event page, but didn't see anything that specifically relates to this problem. I'm still not clear if the 1054 error on the server is being generated by the server, or is a response to a client computer trying to download the GPO from the server.
|
|
|
|
|
|
host master
United States
Member since
9/26/2007
Registered Users
Posts: 14
|
| 9/28/2007 07:15 PM |
|
Hmmm...maybe I'm getting closer...here's the debug log for userenv...any ideas what's failing?
USERENV(168.e8c) 13:14:25:328 ProcessGPOs:
USERENV(168.e8c) 13:14:25:328 ProcessGPOs:
USERENV(168.e8c) 13:14:25:328 ProcessGPOs: Starting computer Group Policy (Background) processing...
USERENV(168.e8c) 13:14:25:328 ProcessGPOs:
USERENV(168.e8c) 13:14:25:328 ProcessGPOs:
USERENV(168.e8c) 13:14:25:328 EnterCriticalPolicySectionEx: Entering with timeout 600000 and flags 0x0
USERENV(168.e8c) 13:14:25:328 EnterCriticalPolicySectionEx: Machine critical section has been claimed. Handle = 0xaa4
USERENV(168.e8c) 13:14:25:328 EnterCriticalPolicySectionEx: Leaving successfully.
USERENV(168.e8c) 13:14:25:328 ProcessGPOs: Machine role is 3.
USERENV(168.e8c) 13:14:25:328 PingComputer: PingBufferSize set as 2048
USERENV(168.e8c) 13:14:25:328 PingComputer: Adapter speed 10000000 bps
USERENV(168.e8c) 13:14:25:328 PingComputer: First time: -2
USERENV(168.e8c) 13:14:25:328 PingComputer: Second time: -2
USERENV(168.e8c) 13:14:25:328 PingComputer: First and second times match.
USERENV(168.e8c) 13:14:25:328 PingComputer: First time: -2
USERENV(168.e8c) 13:14:25:328 PingComputer: Second time: -2
USERENV(168.e8c) 13:14:25:328 PingComputer: First and second times match.
USERENV(168.e8c) 13:14:25:328 PingComputer: First time: -2
USERENV(168.e8c) 13:14:25:328 PingComputer: Second time: -2
USERENV(168.e8c) 13:14:25:328 PingComputer: First and second times match.
USERENV(168.e8c) 13:14:25:328 PingComputer: No data available
USERENV(168.e8c) 13:14:25:328 PingComputer: PingBufferSize set as 2048
USERENV(168.e8c) 13:14:25:328 PingComputer: Adapter speed 10000000 bps
USERENV(168.e8c) 13:14:25:328 PingComputer: First time: -2
USERENV(168.e8c) 13:14:25:328 PingComputer: Second time: -2
USERENV(168.e8c) 13:14:25:328 PingComputer: First and second times match.
USERENV(168.e8c) 13:14:25:328 PingComputer: First time: -2
USERENV(168.e8c) 13:14:25:328 PingComputer: Second time: -2
USERENV(168.e8c) 13:14:25:328 PingComputer: First and second times match.
USERENV(168.e8c) 13:14:25:328 PingComputer: First time: -2
USERENV(168.e8c) 13:14:25:328 PingComputer: Second time: -2
USERENV(168.e8c) 13:14:25:328 PingComputer: First and second times match.
USERENV(168.e8c) 13:14:25:328 PingComputer: No data available
USERENV(168.e8c) 13:14:25:328 ProcessGPOs: DSGetDCName failed with 59.
USERENV(168.e8c) 13:14:25:328 ProcessGPOs: No WMI logging done in this policy cycle.
USERENV(168.e8c) 13:14:25:328 ProcessGPOs: Processing failed with error 59.
USERENV(168.e8c) 13:14:25:328 LeaveCriticalPolicySection: Critical section 0xaa4 has been released.
USERENV(168.e8c) 13:14:25:328 ProcessGPOs: Computer Group Policy has been applied.
USERENV(168.e8c) 13:14:25:328 ProcessGPOs: Leaving with 0.
USERENV(168.e8c) 13:14:25:328 EnterCriticalPolicySectionEx: Entering with timeout 600000 and flags 0x0
USERENV(168.e8c) 13:14:25:328 EnterCriticalPolicySectionEx: Machine critical section has been claimed. Handle = 0xaa4
USERENV(168.e8c) 13:14:25:328 EnterCriticalPolicySectionEx: Leaving successfully.
USERENV(168.e8c) 13:14:25:343 LeaveCriticalPolicySection: Critical section 0xaa4 has been released.
USERENV(168.e8c) 13:14:25:343 GPOThread: Next refresh will happen in 5 minutes
|
|
|
|
|
|
Mariette Knap
The Netherlands
Member since
3/24/2005
Forum Admins
Posts: 12952
|
|
host master
United States
Member since
9/26/2007
Registered Users
Posts: 14
|
| 9/28/2007 10:35 PM |
|
But why would this be an issue when there is only one SBS server and a couple of clients?
|
|
|
|
|
|
Mike Richard
United States
Member since
3/28/2008
Registered Users
Posts: 5
|
| 5/26/2008 07:54 PM |
|
Has this issue been resolved? I have the same problem including no errors for about 24 hours after reboot. This server was running for about 3 weeks without errors before this started and there have been no configuation changes.
Thanks,
Mike |
|
|
|
|
|
Marina Roos
The Netherlands
Member since
3/24/2005
Forum Admins
Posts: 12627
|
| 5/26/2008 11:16 PM |
|
Hi Mike,
There can be many reasons for these errors and the causes can be several.
Please, post an ipconfig /all from the server and a workstation. Open a command prompt by opening Start -> Run from the Start Menu and type cmd. From the command prompt type ipconfig /all >ip.txt. Attach this file to your answer.
|
|
| Marina Roos Smallbizserver.Net Administrator | Mission accomplished. We have joined the branch office to our SBS 2003 Headquarters and have the same user experience on the branch office as we have on our local network at the Headquarters. Want to know how? Signup up for a subscription and get instant access to the article series 'How to add an additional Domain Controller from a remote office to the SBS domain' |
|
|
|
|
robert pearman
United Kingdom
Member since
2/23/2007
Platinum Membership
Posts: 1786
|
| 5/27/2008 04:37 PM |
|
on the server when you go into nslookup, does it resolve the name of the server correctly?
do you have a reverse dns lookup zone on the server?
any other intermittent errors on the server? |
|
|
|
|
|
host master
United States
Member since
9/26/2007
Registered Users
Posts: 14
|
| 5/27/2008 05:12 PM |
|
Hi Mike: No, I was never able to resolve the issue...if you've read the thread you see I wasn't able to get anywhere.
After re-reading the 1054-errors page a number of times, I finally added a NIC to the server, bypassing the onboard controller...this did not help either.
I just ran the best practices analyzer and received all green checkmarks...so no problems there either.
One thing I ran up against recently was the DC and clients falling out of time sync...it seems like none of the computers were able to get to time.windows.com to set their clocks. I updated all the machines on the domain to use different timeservers and that problem went away, but the 1054 errors have resumed.
|
|
|
|
|
|
Paul Broadwith
United Kingdom
Member since
3/27/2006
Registered Users
Posts: 1
|
| 5/27/2008 05:58 PM |
|
I have fixed this problem on three separate servers (two HP's and 1 Dell). Like both Mike and host master I tried all of the troubleshooting docs and articles to get it working and everything I tried was fine. The errors only started appearing after the server was up for a certain period of time (different each time and different on each server).
The solution for me every time so far as been to simply update the NIC drivers. I know this sounds daft, but it's worked each time. On the HP servers I applied the latest Support Pack and on the Dell I simply update both NIC's drivers.
Like some this isn't the holy grail of solutions as I know others on other sites have tried it and it doesn't work for them, however give it a try. The worst that can happen is you have new NIC drivers! |
|
|
|
|
|