Remote Desktop stopped working.

My server is running Windows Server 2003 R2. I use Remote Desktop quite a bit. Everything was working just fine until a few days ago. I now can't get into my server through RDP. I have checked all my ports on firewalls, routers and on the server itself. I have checked anti-virus software and everything else that could be blocking the connection. Everything looks the same as it did when RDP was working. It worked at 5pm on night, the next morning at 7am it wasn't working. We didn't do anything to the server between then. I am not sure what else to look for. Any ideas why RDP would stop working randomly?
brasimanAsked:
Who is Participating?
 
brasimanConnect With a Mentor Author Commented:
It was my firewall. I had to replace it.
0
 
KimputerCommented:
What does the log book say about this (connect a few times, then look at the event viewer). Also, sometimes something as easy as a reboot will resolve this issue.
0
 
RizzleCommented:
Have you checked on the server that RDP is still enabled and that your account still has permission to RDP onto the server? Has a reboot of the server been attempted to see if RDP works? Also have you tsadmin.exe to see if its due to having too many disconnected sessions?

Maybe this KB might help: http://support.microsoft.com/kb/2477023
0
Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
Seth SimmonsSr. Systems AdministratorCommented:
when you try to connect, what is the error?
is it listening on port 3389?
0
 
brasimanAuthor Commented:
Thanks for the quick replies! I have rebooted the server probably 4-5 times and I still can't connect.

Which log would it be in the Event Viewer?

I will also look at the Microsoft link now. Thanks!
0
 
brasimanAuthor Commented:
Yes, 3389. When i try to connect, it errors saying:

Remote Desktop can't connect to the remote computer for one of these reasons:
1. Remote access to the server is not enabled
2. The remote computer is turned off
3. The remote computer is not available on the network

Make sure the remote computer is turned on and connected to the network, and that remote access is enabled.

I have verified all of that and everything looks good on the server. If it helps, i can connect to the server through RDP when inside the network. When i'm outside, using the outside IP, that is when i get the error. Does that help troubleshoot this?
0
 
RizzleCommented:
But when externally aren't you using a VPN to get back through to your internal LAN? Maybe try restarting the firewall service on the server to see if helps. Is anyone else able to access this server externally? Has this been tried via IP and Hostname externally and internally?
0
 
brasimanAuthor Commented:
Correct. I am not using a VPN right now. I am using Remote Desktop. I will try restarting the firewall service.

No, nobody is able to access the server externally.

Yes, we have tried with IP and Hostname. Externally, neither work. Internally, both work.
0
 
RizzleCommented:
Stupid question but can any other server be accessed externally via RDP?
0
 
brasimanAuthor Commented:
Do you mean another server here? Or just any server? I have one server here. There aren't any others. All port forwarding is pointing to my one server here. I do have a few other servers at different locations that I can access.
0
 
lluddenCommented:
How are you passing the data through your internet firewall?  If you have a rule set up to do port forwarding, check to make sure the rule is correct and that the IP addresses haven't changed on any of the internal machines.
0
 
RizzleCommented:
Any other server internally facing behind the Firewall. Like the above comment check the IP on the server you want to RDP to and the rule on the router/firewall to ensure the correct IP is still being forwarded. Could be the IP of the server has changed, did it have a static IP setup before?
0
 
Ratnesh MishraCommented:
Hello Brasiman,
Try few steps from my side and provide me the information you got .
1. Go to the console of the Server and try mstsc to the localhost and IP of the server. Please let me know whats the output ? If you are able to get the RDP on the same machine ,it means RDP at the server end is working fine.

2. Try mstsc /admin or mstsc /console from the desktop you are facing the issue. I do hope that you are facing the issue from all the desktop.

3. What if you try to take the access of files and folders through UNC i.e //IP of server .

4. What if you try to take access of services or event viewer remotely through mmc.

5. Please check event id 56 in the event viewer.

6. Try telnet 3389, Are you able to get it ? if you haven't changed the TS listening port.

7. Don't forget to check that Name resolution is fine and there is no conflict with the IP.

Please provide the information as asked above. It will lead us in making the action plan to get the resolution.
0
 
KimputerCommented:
As you said in works internally, and not externally, it's either a jump in IP numbers (maybe your ISP assigned you new IP addresses? Check with myipaddress.com) or your firewall lost its configuration (or someone else changed it).
0
All Courses

From novice to tech pro — start learning today.