cheesebugah
asked on
The server denied the connection - RDP
Hello,
We have a Windows 2003 server running Exchange 2003. We cannot RDP into this server anymore for some unknown weird reason. It worked just fine up until a few days ago. It tells us "The server denied the connection." I have tried every fix I have found on the net for this and nothing has worked so far. I've checked all of the permissions, group policy, local policy, seemingly everything. We have rebooted the server. Does any one else have any ideas? It is a VM.
Thanks,
Mike
We have a Windows 2003 server running Exchange 2003. We cannot RDP into this server anymore for some unknown weird reason. It worked just fine up until a few days ago. It tells us "The server denied the connection." I have tried every fix I have found on the net for this and nothing has worked so far. I've checked all of the permissions, group policy, local policy, seemingly everything. We have rebooted the server. Does any one else have any ideas? It is a VM.
Thanks,
Mike
Is the VM syncing time with the host? Can you log into it via the console?
ASKER
Yes, I can log into it via the Vsphere Client console.
What about the time syncing?
ASKER
The time is fine.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Can you please explain how to RDP using loopback? The firewall is off. AV is off. The registry key is set correctly.
ASKER
When I go to Remote Desktop Users it says:
Domain\me already has access? What the heck is going on here? This totally has me baffled.
Domain\me already has access? What the heck is going on here? This totally has me baffled.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I tried restarting the Terminal Services service, but it is grayed out now? Odd???
Sorry! Haven't been able to check back. For loopback rdp to the address 127.0.0.1 - this tells the machine to RDP to itself. Do this while logged in locally to the terminal server. I will look into what you have posted since my last comment
ASKER
I believe the fix was changing the network adapter in Terminal Services Configuration on the server and then rebooting.
Thanks,
Mike
Thanks,
Mike