Windows Server 2003 problem

Gamingmatty

Junior Member
Feb 3, 2005
2
0
0
I have a 2003 server that works fine all day long and then dies sometime in the night when no users are working. My event viewer is riddled with these two errors. A simple reboot fixes the problem for about 20 hours. I have tried all kinds of things. I have not reinstalled the OS, but I have reinstalled active directory. Nothing I can find on a google search fixed the problem. When I try to manage active directory users and computers I get "The server is not operational" Any suggestions?



System Log error: Event 1030
Windows cannot query for the list of Group Policy objects. Check the event log for possible messages previously logged by the policy engine that describes the reason for this.

Application Log error: Event 1053
Windows cannot determine the user or computer name. (Not enough storage is available to complete this operation. ). Group Policy processing aborted.
 

djdrastic

Senior member
Dec 4, 2002
441
0
0
1)Have you done a netdiag / dcdiag as to ascertain what the problem might be ?
2)Have you checked your DNS Servers REcords ? Might be time to flush some of those old caches if need be
3) Are all the roles only on that dc ?
4)Does nslookup Work Correctly ?
5)Have you set any strange SMB Signing Requests etc?


Dns causes an insane ammout of AD Trouble when not working correctly [ and for good reason as it is completely dependant on dns to work properly]
 

Gamingmatty

Junior Member
Feb 3, 2005
2
0
0
I cannot run the netdiag or dcdiag commands. They are not recognized commands. I have all the utilities i can find installed.

I have flushed the dns records

All the roles are on this domain controller. DNS, Routing and Remote Access, File Server, Print server.

nslookup says "cannot find server name for address 192.168.0.100: non existant-domain"

The information that i get from DNS event viewer is:
The DNS server could not signal the service "NAT". The error was 1168. There may be interoperability problems between the DNS service and this service.

ICS is the service that deals with NAT and it is up and running. But NAT is performed on my router, not on the server.

I still don't understand why a reboot makes the server run perfectly all day long. Then sometime in the night it dies.
 

stash

Diamond Member
Jun 22, 2000
5,468
0
0
On your 2003 CD, go to the support, tools folder and run suptools.msi. This will install the support tools which includes netdiag and dcdiag. You can then either log off and log back on to put the support tools directory in your path, or change dirs in the command line to c:\program files\support tools.

Then run netdiag /v and dcdiag /v.

My guess is that RRAS is screwing up your DNS. The external NIC is most likely registering in DNS which will cause problems for AD.