Problem: There are currently no logon servers available to service the logon request.
I have added a new windows 2003 server to the network, It is configured as a domain controller and DNS server for a total of 2 dns servers on the same network.
The new comain “cityhall.int” shows up fine on the network and i can see and access the other domain “Cityofabbeville,int” but the cityofabbeville.int can see cityhall.int but can not access it.
When I try to join a computer to cityhall.int it is unable to locate the domain.
I notices the following error in the system event log. There are no apparent DNS event issues
The Security System detected an authenticaton error for the server ldap/W3kABB1.cityhall.int.
The failure code from the authentication protocal Kerberos was “There are currently no logon servers available to service the logon request.
Event id: 40960
category: SPENGO (Negotiator)
Solution: There are currently no logon servers available to service the logon request.
There can be multiple causes of your problem:
You just brought a new server on line. To complete the process, the server has to register its own host A record and SVR record in DNS. To do this, Type the following at the command prompt:
net stop netlogon
net start netlogon
flushing DNS will remove all old or improper DNS records
registering dns records registers your Host A record
restarting the netlogon will register your SVR records.
Speaking of SVR records, here is your second potential problem:
The cause or your problem may be the result of a faulty default DNS server cached record Cityofabbeville,int.
2003 server has a quirk in it. When the netlogon service is restarted it registers the SRV record of both NICs on the DNS server. As you know DNS is the service that provides the DNS translation to the Authenticating server. If DNS sees two SRV records, Cityofabbeville,int picks up on the NIC that shouldn’t be providing DNS to the clients, you may get “no netlogon servers can be found” for your authentication server and see the errors above.
The quirk in 2003 server is regardless of deselecting the option registering the SRV record when netlogon is restarted, it will still register the SRV record. There is a patch to resolve this. But, let’s make sure this is the problem. Go into DNS and see if your multihomed DNS server has two SRV records. One will be internal and the other external of your LAN. If you have an SRV record that doesn’t belong, you should remove these records. This is only a temp fix for troubleshooting because upon a restart of the netlogon service will put those records back in DNS.
Then, I would go to the XP clients and check out the IPconfig /all. See if you have picked up on a DNS server that is not correct. If so, you will not be able to get the DNS query for the Authenticating server to propogate back. So, you will not be able to communicate with the Authenticating server. Hence, you will not be able to authenticate and recieve errors like you are seeing. Flush the DNS cache and manually configure your list of preferred DNS servers to the correct NICS.
There is a fix to the 2003 server. It is a patch.