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

Doodad Boy
Doodad Boy used Ask the Experts™
on
Unable to login sever due to error prompt "There are currently no logon servers available to service the logon request". However server disk able to map and access. Server become normal and able to login with domain after a reboot.
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Doodad BoySupprt

Author

Commented:
What are the network login port which is used upon login to the server with domain. I suspect this might be cause by port exhaust issue. Because all become normal and able to login with domain after rebooted the server
looks like Network or DNS problems.
Do you see this at a simple server or RDS-/Citrix-/Termnal- server.
Is the server pingable while the problem exist?
How many users are affected?
How many servers are affected?
How long is the Uptime (<15 minutes or >1h)
Which AV do you use?
Ravi Kumar AtreyCloud Specialist- Azure

Commented:
try to remove your system from domain and add it again by renaming it. It has lost the Domain configurations.
Ensure you’re charging the right price for your IT

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!

Distinguished Expert 2018

Commented:
What are the DNS settings like on that machine? If there's a DNS server that is outside of your network, you will have issues.

Start there, then work on tracking how the system is performaing.
Technical Specialist
Awarded 2017
Distinguished Expert 2018
Commented:
Server become normal and able to login with domain after a reboot.
Is server fully patched? You linked 2003/2008. If that is the case, I recommend you add a host-based firewall on it to block all traffic except for the required services.
Doodad BoySupprt

Author

Commented:
Hi Team,

Server configured IP still able to ping during the reported issue.

Server disk and file share able to access via network.

Only not able to login with domain via rdp.

Server has been configured with internal DNS server as per confirmed by our AD team.

This is normal fileshare server where people rdp to the server.

Around only 12 users are accessing the server

As for now, only this file share server having this kind of issue.

Whenever the issue happen, we will be rebooting the server, then users able to rdp the server

Symantec has been used as AV for this server.

We also tried to remove and add the server from domain, seem the issue still persist and become very frequent.

This is Windows 2008 r2 Vmware virtual server.

I suspect this might be a port exhaust issue.

Any tool  or query can be used if the issue happen again
I agree with Rami, disjoin, rename reconnect to the domain, the profile will be fine, I get this one every once in a while.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial