"No logon server available"

Symptoms: you can ping the server by ip and name but can't map the shared drive by using net use \\ip or \\servername.  If you try, you may receive the "No logon server available".

Resolutions: This sounds like cache credential issue. 1) make sure the computers in the same network, the same workgroup/domain and have created the same username. 2) use net to cache the credential. 3) The user profiles may been damaged.

"No domain server was available to validate your password"

Symptoms: when trying to logon a domain from win9x, you may receive a message "The following error occurred while loading protocol number 0. Error 38: The computer name you specified is already in use..." and then "No domain server was available to validate your password".

Resolution: 1) make no two host name in the network. 2) check WINS and make sure no one host uses two IPs. If it does, delete all of them and reboot the computer.

"No domain server was available..." while the dialup connection is active

Symptom: you have  windows 2000 domain controller with DNS, DHCP, WINS and Dialup connection. Whenever the dialup connection is active, none client can't logon and gets a message "No domain server was available to to validate your password. You may not be able to gain access to some network resources"

Resolution: Make sure you don't have "Register this connection's addresses in DNS" checked under TCP/IP Advanced DNS settings. To check this, go to the Properties of the connection> the Properties of the TCP/IP>Advanced>DNS, uncheck "Register this connection's addresses in DNS"