Link to home
Start Free TrialLog in
Avatar of CanOfWorms
CanOfWormsFlag for United States of America

asked on

RDP stops listening

I have a Windows 2008 32Bit Terminal Server that has been running for over a year with no hitches.

All of the sudden clients can not connect. Telnet to the server on 3389 fails. Telnet to 3389 locally from the server itself fails.

Running qwinsta responds:
C:\Users\NetAdminUser>qwinsta
 SESSIONNAME       USERNAME                 ID  STATE   TYPE        DEVICE
 services                                    0  Disc
>console           NetAdminUser                 1  Active

All services are running, RDP Connection is enabled, I deleted the Connection and recreated it. Still not able to connect with RDP client or telnet on 3389.

Anyone have any ideas?
Avatar of Radhakrishnan
Radhakrishnan
Flag of India image

Hi,

Could you check on the firewall. If you go in to the firewall rules area there is a button you can click to change the settings. There should be a large scroll box listing lots of different programs and should they be allowed or denied.

Find Remote Desktop Access and make sure there is a check mark there for your domain access.
Checked the firewall?

Any updates gone on lately?
Avatar of CanOfWorms

ASKER

Firewall turned off.
Might have had updates but not certain.
No updates were installed. I did find a couple JAVA:TrojanDownloader infections. Cleaned but still not working. I am going to change the listening port and see if that helps.
Even changing the default TCP/IP listening Port from 3389 to 3399 does not allow connection. I am stumped.
SOLUTION
Avatar of George Khairallah
George Khairallah
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I understand the need to get it working, but it may have been an MS update that broke something - what's to say it won't happen again?

At least it's working for now - good luck and glad you resolved it.
Luckily there was no Microsoft Updates done for many months, so that was not the cause. Admittedly I am still nervous about it happening again as we don’t know what caused it.
Problem seemed to be related to the Terminal Services Role itself. Cause unknown.