There are currently no logon servers available to service the logon request - how to fix this error?

  • Thread starter Thread starter Daniel
  • Start date Start date
D

Daniel

There are currently no logon servers available to service the logon
request - how to fix this error? i get it when trying to access a share one
hop away.
here is port scan from the machine i am using to try to access the share of
the machine with the share:
Interesting ports on <domain name>:
Not shown: 1696 closed ports
PORT STATE SERVICE
80/tcp open http
135/tcp open msrpc
139/tcp open netbios-ssn
445/tcp open microsoft-ds
1031/tcp open iad2
2301/tcp open compaqdiag
3389/tcp open ms-term-serv
9535/tcp open man
MAC Address: <mac addy> (Compaq Computer)
Device type: general purpose
Running: Microsoft Windows 2003/.NET|NT/2K/XP
OS details: Microsoft Windows 2003 Server Standart Edition SP1, Microsoft
Window
s 2003 Server, 2003 Server SP1 or XP Pro SP2
Network Distance: 1 hop
 
Multi-posted in at least three separate newsgroups.
Please use cross-posting if you wish to address
several newsgroups, and keep your Subject line short
to avoid truncation.
 
Daniel said:
There are currently no logon servers available to service the logon
request - how to fix this error? i get it when trying to access a share one
hop away.
here is port scan from the machine i am using to try to access the share of
the machine with the share:
Interesting ports on <domain name>:
Not shown: 1696 closed ports
PORT STATE SERVICE
80/tcp open http
135/tcp open msrpc
139/tcp open netbios-ssn
445/tcp open microsoft-ds
1031/tcp open iad2
2301/tcp open compaqdiag
3389/tcp open ms-term-serv
9535/tcp open man
MAC Address: <mac addy> (Compaq Computer)
Device type: general purpose
Running: Microsoft Windows 2003/.NET|NT/2K/XP
OS details: Microsoft Windows 2003 Server Standart Edition SP1, Microsoft
Window
s 2003 Server, 2003 Server SP1 or XP Pro SP2
Network Distance: 1 hop

That error occurs for a number of reasons.

DNS misconfigured
Broken trust
WAN Link down
Other routed link down.
Domain Controller or service down.


Assuming a Windows domain, your member workstations and servers must be
able to contact a domain controller to authenticate the user. This
requires 2 basic things -

1) a working network connection on the client, server, and domain
controller.
2) name resolution so the client and server can contact the domain
controller.

In addition, if external trusts are in place between domains, the domain
controllers in each domain must be able to contact a DC in the other domain.

....kurt
 
Back
Top