DNS failure and Event 1054

[ahspao]

I am a newbie to Windows 2003 Server but I setup a server 4 days ago. It runs, AD, DNS, DHCP. I setup 10 user accounts and everything has been working fine. Today I shut it down to plug it into a UPS and when I powered it up, it gave me the USERENV Event 1054 error. I researched it a little and ran the DCDIAG program but I dont get much to start on. The internet still works on all the clients, they just cant authenticate to the DC. I have a single label domain name so I saw the KB on that and went into the policy editor and told it to update to top-level domains (

http://support.microsoft.com/defaul...ft.com/default.aspx?scid=kb;en-us;300684&FR=1

) this article. I didnt do the registry stuff, just method 2. I'm convinced that I have a DNS problem because the DC can't identify itself even though its on the same machine. I dont want to re-install everything and have to go rejoin the domain on 10 clients, is there anyway to find the problem ?

 

[GlenJohnson]

Try this.

1. Open Network Connections in Control Panel.
2. Right-click Local Area Connection, and then click Properties.
3. Click Internet Protocol (TCP/IP), and then click Properties.
4. Type the correct DNS address in the Preferred DNS server box.
5. Click OK.

From MS.

Glen A. Johnson
If you're a kid at heart, check out Tek-Tips Disney
Yeah, I was stuck in Disney's Tower of Terror once.

 

[ahspao]

I already had them in there. The address 192.168.10.2 (which is the server itself) and 192.168.10.1 (which is the router) The current setup is...dhcp gives the client machines the .2 address as DNS, and the server forwards it to the router .1, then the router does the rest I presume since websites are still working. I'm debating if I should just change the domain name to xxx.local and see if it fixes anything ??? Any other options..