Discussion Locked

no domain server available

0 helpful
12 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Hi, I have one machine that everytime after a reboot, I try to log it onto the domain and it says no domain controller available, yet I know that it is. Then I logoff and try it again, it is usually there after the 2cd or 3rd try. Do you have any suggestions?

12 replies

by dstjohn

This will happen if the client's registry in the Security Accounts Manager (SAM) database is missing or corrupt. The quickest workaround is to rename the machine, delete the machine's old account in server manager, and re-join the domain with administrator credentials (needed to create a computer account on the domain).

by michealirwin

This problem happens to almost everyone I've ever spoken to who runs MS networks. It can have several reasons, so giving more info (OS on each end of attempted connection, type of connection, etc.) would have helped.

If you go to microsoft.com, click on the Search option at the top of the screen, and enter "no domain server available" you'll get about 100 hits, giving you some idea of the frequency of this problem. Read through them until you find some that fit your situation and then try their recommendations.

Good luck

by matt

One thing you may want to try, is see if you can see the rest of the network. If you can browse to other machines, internet if you have full network access, or the server, then I'm not exactly sure. If you can't see anything else, try putting another hub in place, even just a temporary 5 port. I had this problem and it turns out one of our hubs could not handle new NICs. Got a link light but couldn't not browse the network or get on the internet. Worth a shot.

Matt

by does not compute!

Anyone got any advice on speeding up the brownser, I find that browsing the netware 4.11/Windows NT4 Domian is very slow is there any advice on speeding up the ratea t which I can browse ?

by shawkengin

when you login either successfully or not, check the eventviewer log and u may find the exact problem causing the login issues. Could be lots of issues, name conflicts on the network, whatever switch on the LAN is not fast enabled so may have to wait a few seconds before you get an address, or could be that you have too many concurrent connections on your LAN and DHCP (if that is your network) does not issues a lease sooner. Ms site is indeed the best place to look for answers like this that will be taylored to your problem more effectively.

Hope that helps.

by hedgeek

Learn to use the knowledge base portion (accessed on the MS homepage in the support drop-down menu), which will help you narrow down the number of responses. Its a great resource. You may also have to add the new system name into the server manager prior to logging on the first time, which is something I've come across a few times. Hope this helps.

K

by madness

A quick thing to check.
Are you using Cisco Switches? Check Cisco's site about this. There is an issue with Cisco switches and no domain. Ya just gotta keep hitting cancel then ok. I know it's not cool. Try explaining that to a DR. They don't understand a thing and they went to school for 8+ years

by brucegyl

May be simple. Logon server is processing too many other requests at the time you request authorization (which is why you can logon on 2d or 3d try). Depends on many parameters.. the MS database is an excellent place to read up on this. Parameters like "is your Primary Domain Controller running DHCP or WINS?" You might even try preloading the IP adress of the PDC on the client using LMHOSTS.sam (explained by reading this file (in your windows directory). This could be of some help.

by chris joseph

I am having the same problems with NT 4.0 sp6a and client Win98 machines. "The domain password you supplied is not correct, or access to your logon server has been denied." You get this error and then hit ok, retype your password, and your in. It isfrustrating to say the least. Here are a couple of things to try that have not worked for me.

First, see if your Wins server has both primary and secondary wins servers filled in on the WINS servers TCP/IP properties. If not fill in the second server if your network has only one then use the same ip. Another thing is making sure that the clients computer names do not contain trailing spaces if so delete space, restart.

by robinkrieger

I just had the same problem and just solved it. You should go to the Wins Manager and delete all the entries for the machine in the database and also remove the static mapping for this machine. Then reboot and it will register itself again with the Wins server.

This discussion is closed to new replies.