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

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.
Doodad BoySupprtAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Doodad BoySupprtAuthor 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
0
Dirk KotteSECommented:
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?
0
Ravi Kumar AtreyCloud Specialist- AzureCommented:
try to remove your system from domain and add it again by renaming it. It has lost the Domain configurations.
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

masnrockCommented:
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.
0
Shaun VermaakTechnical Specialist/DeveloperCommented:
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.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Doodad BoySupprtAuthor 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
0
DanOwnerCommented:
I agree with Rami, disjoin, rename reconnect to the domain, the profile will be fine, I get this one every once in a while.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS

From novice to tech pro — start learning today.