There are currently no logon servers available to service the logon request

2 Windows Servers 2003. Server A is main server, Server B is backup. When server A is down, an error message "There are currently no logon servers available to service the logon request" pops up when a drive on another server (server c) is attempted.

How do I resolve?
Who is Participating?
CorpCompConnect With a Mentor Commented:
Also check your DNS.  If Server B uses Server A for DNS, and not itself, it will not be able to query DNS for logon servers.
Is server A a Domain Controller?
"pops up when a drive on another server (server c) is attempted."

what is a "drive" attempt?
Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

renniscomAuthor Commented:
Server A is a domain controller. Server B is the backup DC
To have logon functionality you need a Global catalog server available. So you should assign Server B as a Global catalog server now.

renniscomAuthor Commented:
I will check this and advise accoordingly within 24hrs
renniscomAuthor Commented:
Server B was already a global catalog server and dns was pointing to itself
run a dcdiag and netdiag on Server B and post the results back here please.
rhinocerosConnect With a Mentor Commented:
1. Server B is a global catalg server and also one of AD DNS server (Same as Server A)

2. Server C's IP setting
   Primary DNS: Server A
   Secondary DNS: Server B

3. So Server C is able to logon to domain when Server A is down.
renniscomAuthor Commented:
Issue resolved! Thanks for the assist
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.