[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

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

RDP Quit Working last week

We have a colo location with 4 servers.  All of the servers have allowed our staff to RDP to each server.  Last week, one server quit allowing RDP connections.  We get the following error message: "Your Remote Desktop session has ended, possibly for one of the following reasons: The administrator has ended the session., An error occurred while the connection was being established., A network problem occurred."  Since it is only one of the four servers with the problem, I assume it is not a network issue.  I can remote into the server using VNC, Dameware and ILo, so it appears to be tied to RDP.  Of course I don't want to use VNC, ILo or Dameware for our staff, so I need the RDP sessions to work.  Our GPO has the windows firewall off so I don't believe it to be a firewall issue.  
I read in one area that windows defender can disable the port used by RDP.  How can I enable this port again and how can I create an exemption in Windows defender that will prevent this from happening again.
0
sfletcher1959
Asked:
sfletcher1959
  • 3
  • 2
1 Solution
 
Alex AppletonBusiness Technology AnalystCommented:
Can you telnet to the server on the RDP port?  You should get a blinking cursor that tells you that the connection is ok.

Disable the Defender service to verify it is causing the issue.  I have never seen or ran into issues where Windows Defender was blocking access inbound on a terminal server.
0
 
sfletcher1959Author Commented:
If I try to telnet to our server on the 3389 port is gives me a can not connect error, but it shows the port number as 23.  So not sure what that is telling us.  The syntax I used was "telnet 19x.xxx.xxx.xxx:3389" and I hit enter.  Is this correct?  I don't see a sevice called windows defender.  Is it named something else?
0
 
Alex AppletonBusiness Technology AnalystCommented:
Proper syntax is telnet <server IP> port.  Not :port
0
 
sfletcher1959Author Commented:
I am able to telnet to the server.  I am able remote connect using VNC, Dameware but not with RDC.  A screen capture is attached of the error we receive.
Desktop-Remote-Connection-Error.doc
0
 
sfletcher1959Author Commented:
Gave up, called Microsoft and paid for a support ticket.  They couldn't fix it either, but about 6 days ago, it started working again.  Who knows?!?!?!?
0

Featured Post

NFR key for Veeam Agent for Linux

Veeam is happy to provide a free NFR license for one year.  It allows for the non‑production use and valid for five workstations and two servers. Veeam Agent for Linux is a simple backup tool for your Linux installations, both on‑premises and in the public cloud.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now