Server 2K /DNS/AD
Posted on 2012-03-13
I am cryng "Uncle!" About 2 weeks ago our server quit serving. When I dove into the problem the DNS and WINS were both missing from the server. How they became MIA is still an unknown. I thought I had successfully reinstalled the DNS and WINS but there have been pesky issues all along. We have a Hardware Firewall - Watchguard Firebox "Edge" that the server (pe600sc) connects to and the rest of the computers are suppose to be connected from the server to firewall. After much tweaking and testing I thought I had it all configured correctly except that on the NIC card I had to list the Watchguard Firebox as the Primary DNS as well as it being the Gateway while the true primary DNS, (PE600SC) had to be listed as alternative DNS. If I switched the order - no internet connection for any computer. (No DNS server found)
To complicate matters late last week I was trying to figure this out and must have replaced something in the DNS stuff so I no longer have access to Active Directory.
I tried to do Recovery Console but kept getting blue screen /fatal error (no, I didn't write the # down). But I also did not disconnect the ethernet cable from server to see if logging on w/o connections to firewall etc. would make the program run.
I have tried the nltest/SC_CHANGE_PWD:,domain name> and that portion was successful. Burt when I went to the second command:
netdom reset p3600sc /domain:ns1.acousticalresources
it failed saying that the specified domain could not be contacted or does not exist.
I cannot Bind to AD.
When I run dcdiag I get error 1323, then when I add user name & password to dcdiag I receive Error 31 "Filename, Directory name or Volume Label Syntax is incorrect.
For some reason I cannot attach a file to this request (Netdiag.log)
I don't know whether it is because the server is so old and the IE connection is IE 6.0 and it won't update IE because the server is too old
We have 6 client computers all running Windows XP Pro.
Thanks for your help - I am hoping it is something easier than reformatting the harddrive/server and starting over.