vmware - "There are currently no logon servers available to service the logon request" when trying to remote desktop to a VM after power failure

  • w128

    I have SQL Server 2008 R2 running on a virtual machine (vmware, Windows Server 2008 R2). I was connected to the SQL Server from another virtual machine via SQL Server Management Studio, then a power failure occurred.

    After powering everything back on, my problem is that now I can't connect to the SQL Server using the same account as before (from Management Studio), nor can I remote desktop/login to the VM using this account. I get "server not found/not accessible" error in SQL Server Management Studio, and if try to connect to the VM using remote desktop, the error displayed when trying to log in is:

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

    However, the VM/server is running (as indicated in the hyperv), I can connect (remote desktop) to it using another account and I can connect to the SQL Server using this account from Management Studio. Rebooting the VM, turning it off and on etc. doesn't help.

    Any ideas what can be done would be appreciated.

  • Answers
    Know someone who can answer? Share a link to this question via email, Google+, Twitter, or Facebook.

    Related Question

    dns - Cannot remote desktop to Windows Server 2008 R2 by machine name
  • IrishBoiler

    Recently installed Windows Home Server 2011. For those that don't know, it runs on Windows Server 2008 R2 SP1. Unfortunately, I cannot remote desktop to box by machine name I gave it. I set the computer name to during install to ATLAS. I have confirmed it is called ATLAS on the machine. No idea how, but even after I run ipconfig /flushdns and then run nslookup, I get the following:

    nslookup atlas

    nslookup server (correct IP)

    IPv6: Works
    IPv4: Works
    "ATLAS" machine name: No
    "Server" machine name: Works

    Any ideas how I can fix this or how it keeps setting the machine name to "server" ?

    Update: Here are the results of two different ping tests. Notice that when I ping ATLAS, it doesn't have a DNS suffix.

    ping atlas Pinging ATLAS [] with 32 bytes of data:

    nslookup server Pinging server.gateway.2wire.net [] with 32 bytes of data:

  • Related Answers
  • Can Poyrazoğlu

    Are you sure that the firewall settings are configured correctly? Most probably a firewall issue.

  • IrishBoiler

    In the end, I gave up and just added it to the hosts file on my laptop. While it works, I was hoping for a more universal solution.