NokiX Posted January 15, 2016 Posted January 15, 2016 Hi All, We are having an issue with one of our 2008 R2 virtual servers in which it's not allowing RDP connections. We are not sure why this is the case as no configuration changes have been made however we have attempted to enabled/disable the RDP service and have also disabled the firewall entirely but we are still unable to RDP. We can of course go through hyper-v to manage the server that way but it's not ideal so I wondered if anyone else has had RDP service issues similar to this. It's worth noting when we stop the remote desk services it seems to crash attempting to stop the service and hangs on the 'stopping' phase so I'm not sure if there is an issue with the service itself! Regards, Chris.
NokiX Posted January 15, 2016 Author Posted January 15, 2016 Yes it is possible to ping the server and you can access shares without any problem it's just the RDP service this seems to effect.
Davit2005 Posted January 15, 2016 Posted January 15, 2016 (edited) Not a license issue?? That was assuming you are using it for remote access or something Or does it not even allow 1 RDP connection? Edited January 15, 2016 by Davit2005
NokiX Posted January 15, 2016 Author Posted January 15, 2016 No the licensing isn't an issue here but we only noticed it recently as we are working on a new cluster setup and found that we were unable to remote onto this machine when in the past it was never an issue. The remote connection attempt will simply time out like the RDP service isn't even running which is the odd thing about it since it's setup in the same was as every server.
NokiX Posted January 16, 2016 Author Posted January 16, 2016 re-boot I've lost count how many times i've tried that
twin--turbo Posted January 16, 2016 Posted January 16, 2016 disable rdp. ok download "tcplisten" to the server and start it and put it on port 3389. then telnet to the server on port 3389 and see if tcp listen responds. that will narrow down network/firewall or RDP. 1
NokiX Posted January 16, 2016 Author Posted January 16, 2016 disable rdp. ok download "tcplisten" to the server and start it and put it on port 3389. then telnet to the server on port 3389 and see if tcp listen responds. that will narrow down network/firewall or RDP. Will try that on Monday although it shouldn't be the firewall since it's disabled but saying that RDP is supposed to be enabled so I wouldn't be surprised if the firewall was in fact still on even when it's supposed to be disabled.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now