[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 689
  • Last Modified:

Unable to RDP to Windows Server 2008 R2 Service Pack 1

All of a sudden I have had I am having an issue on two differnt servers.  Both running Windows 2008 R2 Service Pack 1.  

The server is setup as a Terminal Server with Licensing installed and the RDP CALS applied.  It has been running for months without an issue.

Any ideas?  Anyone know of recent updates that may have created this issue?
0
razorsharpskill
Asked:
razorsharpskill
  • 6
  • 4
1 Solution
 
thomasdavisCommented:
If updates have been applied re-Check firewall settings, AV protection settings, make sure RDP is enabled still. You can test by disabling AV and firewall to see if you can connect again.
0
 
razorsharpskillAuthor Commented:
Already checked the firewall settings and AV.  I am able to ping it from another workstation.  I am just getting the error unable to reach the server when attempting the RDP connection.
0
 
thomasdavisCommented:
When trying to RDP are you using the IP or name? Have you tried both?
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
thomasdavisCommented:
check to see if listening on 3389 netstat -a
0
 
razorsharpskillAuthor Commented:
Tried both.  Not a DNS issue.  This server is also a SQL Server.  I can create an ODBC connection and connect to the database remotely.  I can UNC to the server and open the AdminShare C$.

I have tried uninstalling any updates that were applied to the server without success.  Then also tried reinstalling the updates without success.
0
 
razorsharpskillAuthor Commented:
It is listening on 3389.
0
 
thomasdavisCommented:
Just to check the option to allow connection from any computers running rdp is checked.
0
 
razorsharpskillAuthor Commented:
The option to allow connections from any computer is checked in the computer properties.
0
 
razorsharpskillAuthor Commented:
Found that there was malware on the server using Port 3389.  Changed the Port to something obsure like 3395 and was able to login via RDP.  This lead to the checking for Malware and checking what was locking up Port 3389.

Thank you for all your help.
0
 
razorsharpskillAuthor Commented:
Found the problem was malware.
0

Featured Post

Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

  • 6
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now