Avatar of CanOfWorms
CanOfWorms
Flag 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?
Windows Server 2008

Avatar of undefined
Last Comment
CanOfWorms

8/22/2022 - Mon
Radhakrishnan

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.
Tony J

Checked the firewall?

Any updates gone on lately?
CanOfWorms

ASKER
Firewall turned off.
Might have had updates but not certain.
I started with Experts Exchange in 2004 and it's been a mainstay of my professional computing life since. It helped me launch a career as a programmer / Oracle data analyst
William Peck
CanOfWorms

ASKER
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.
CanOfWorms

ASKER
Even changing the default TCP/IP listening Port from 3389 to 3399 does not allow connection. I am stumped.
SOLUTION
George Khairallah

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question
SOLUTION
Log in to continue reading
Log In
Sign up - Free for 7 days
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
ASKER CERTIFIED SOLUTION
Log in to continue reading
Log In
Sign up - Free for 7 days
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
Tony J

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.
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
CanOfWorms

ASKER
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.
CanOfWorms

ASKER
Problem seemed to be related to the Terminal Services Role itself. Cause unknown.