I have a W2K Server that returns a couple of Service Events error messages at boot. The messages appear to be related and a sample message follows: Source: NETLOGON Event ID: 5775 Deregistration of the DNS record '_gc_tcp Default-First-Site._sites DERRELLNET.local.600 IN SRV 0 100 3268 mcsi_nt1.DERRELNET.local.'failed with the following error: DNS bad key. There are no problems seeing this computer on the network or accessing any of it shares; nor does this computer have a problem accessing other computers on the network. The network is composed of: 1- W2K Server 1- W2K Pro Workstation 2- W98 Workstations The Server uses internet acces via an external modem and satelite dish. Anyone have an idea what is causing this error and how to resolve it? Does DNS need to be removed and restablished? I looked for a EVENT ID# 5775 at the MS Knowledge base w/o success. Regards,

You may need to remove and reinstall DNS--but first, let's make sure that it is installed correctly. Is it active directory integrated? In the TCP/IP properties, do you have this server's IP address for the Preferred DNS server? And the Alternate needs to be blank. Then open the DNS console. Do you have a Forward Lookup Zone? If you have a "." folder, delete it because this is for DNS root servers on the internet. Right click on the FLZ folder and choose properties, select the Forwarders tab--this is where you put your ISP's DNS server IP addresses. Within the FLZ folder, you need to have a SOA, showing the server's fully qualified domain name--this must match what is shown if you right click on my computer and properties and the name is show as something like, "[1],administrator.servername.mycompany.com.". The Server Name should look the same, servername.mycompany.com., and another entry that is servername with type host and data has IP address. Now create a Reverse Lookup Zone, Standard Primary for now, create a new pointer record, double-click the server name, double-click the FLZ folder, double-click the the server name, click OK. Now open a Command Prompt and type "nslookup ", without the quotes and insert the server's NetBIOS name. It should return something like this: Server: servername.mycompany.com Address: 192.168.0.1 Name: servername.mycompany.com Address: 192.168.0.1 What this proves--the Server's NetBIOS name is being resolved to the fully qualified domain name and IP address--proves that DNS is working. Insert your W2K CD, select browse, select Support folder, select Tools folder, double-click setup.exe and do a typical install. Once that is complete, open a command prompt and run this command, "netdiag /fix >c:\netdiag.txt". Look at the netdiag.txt file on the C root and see if DNS passes. If it Failed, if you will email me the file I will analize if for you. Any questions? Let me know if I missed any steps--I'm doing it all from memory as I don't have a W2K Server booted right now. But I don't think that I missed anything. I don't have access to my data base right now and can't remember what 5775 is. But if this doesn't fix it, let me know and I'll tell you what 5775 is. Good luck.

W2K Stud, Thanks for the help. I will do as you instruct and post the results on Monday or Tuesday. Regards

I have the same error. It also seems to be affecting the ability to join another server into the domain as a BDC. The second machine will join as a workstation but not as a member or additional machine.

I implemented the suggestions to determine if DNS was working... The server is no longer connected to the internet via the satelite dish and eternal modem nor any other device. Is it active directory integrated? In the TCP/IP properties, do you have this server's IP address for the Preferred DNS server? No, it was set as 127.0.0.1 I adjsuted it to 192.168.0.1. I immediatly received a message complaining that this was the same address as the NIC...did I want to proceed...selected yes And the Alternate needs to be blank. Yes... Then open the DNS console. Do you have a Forward Lookup Zone? If you have a "." folder, delete it because this is for DNS root servers on the internet. The "." folder was present and I deleted it. Right click on the FLZ folder and choose properties, select the Forwarders tab--this is where you put your ISP's DNS server IP addresses. OK... Within the FLZ folder, you need to have a SOA, showing the server's fully qualified domain name--this must match what is shown if you right click on my computer and properties and the name is show as something like, "[1],administrator.servername.mycompany.com.". The Server Name should look the name, servername.mycompany.com., and another entry that is servername with type host and data has IP address. Yes, the name was the same...except in the SOA the name was all lowercase and a "right-click" brings up a name which is both lower and uppercase...mcsi_1nt1.DERRELLNET.local Now create a Reverse Lookup Zone, Standard Primary for now, create a new pointer record, double-click the server name, double-click the FLZ folder, double-click the the server name, click OK. The process was a little different than as described...good job from memory! and, I was fumbling along and selected 168.0.1 as a setting. Now open a Command Prompt and type "nslookup ", without the quotes and insert the server's NetBIOS name. It should return something like this: Server: servername.mycompany.com Address: 192.168.0.1 Name: servername.mycompany.com Address: 192.168.0.1 What this proves--the Server's NetBIOS name is being resolved to the fully qualified domain name and IP address--proves that DNS is working. This returned an "unknown zone" for the top part and the 2nd part returned the correct information. Insert your W2K CD, select browse, select Support folder, select Tools folder, double-click setup.exe and do a typical install. Once that is complete, open a command prompt and run this command, "netdiag /fix >c:\netdiag.txt". Look at the netdiag.txt file on the Croot and see if DNS passes. If it Failed, if you will email me the file I will analize if for you. Done, I will email the file to W2KPRO. Any questions? Let me know if I missed any steps--I'm doing it all from memory as I don't have a W2K Server booted right now. But I don't think that I missed anything. I don't have access to my data base right now and can't remember what 5775 is. But if this doesn't fix it, let me know and I'll tell you what 5775 is. Good luck