Unable to login to Win2k8 servers

Published 13 years ago

We are having intermittent issues in our office where we are unable to login to win2k8 servers at our datacenter over vpn via Remote desktop manager. This only happens on a specific domain, and it works fine in other domains. This has happened on both Windows 7 and Windows 8 laptops, and as well the built in RDC will not start on the windows 8 laptop if the Remote desktop manager is installed.

What happens is the login fails with an incorrect username and password which we know is right, and after monitoring the server it does not show any failed login attempts. The workaround is to uninstall remote desktop manager reboot and reinstall and it works again for awhile and then it will stop working again. Any help would be appreciated.

All Comments (4)

David Hervieux

Published 13 years ago

Does it work if you open it in exrernal mode? Have you verified our faq?

http://help.remotedesktopmanager.com/troubleshooting_automaticlogon.htm

David Hervieux

_rayden_

Published 13 years ago

Could it be a DNS (over VPN) issue since this is intermittent? Are you using FQDM for the server? Could be connecting to the wrong server. When it fails to connect, can you connect using RDC?

I'm on Win 8 and have no trouble launching the built-in RDC with RDM installed - I even run both at the same time. Any error when launching it?

jtysdal

Published 13 years ago

I think you may be right about the DNS thing, it's strange because I can ping the computer over the vpn but am unable to connect to it via DNS name or FQDN. But if I just manually enter the IP address of it, it connects with no issues.

Not sure where to go from there though.

_rayden_

Published 13 years ago

Your laptop may be attempting to use the DNS servers of your local connection instead of routing DNS queries for that domain over the VPN. You need to make sure that the DNS servers for the domain and the domain name itself are showing up on the virtual VPN adapter when you do ipconfig /all. The "Connection-specific DNS Suffix" needs to have your domain in it: i.e. company.local. That's how your laptop will know to route DNS queries involving that domain over the VPN to the domain's DNS servers.

You can manually check if your domain's DNS servers are responding properly by doing an nslookup:
nslookup myserver 111.222.333.444
nslookup myserver.company.local 111.222.333.444

(where 111.222.333.444 = IP of domain DNS server)