Solved

Remote Desktop stopped working after Windows Update

Posted on 2006-11-10
11
299 Views
Last Modified: 2008-02-01
2003 enterprise with Sp1 and all updates.

I can no longer connect via RDP to this server from the LAN.  When I run netstat -an | find /i "listening" the port is there.  The firewall is turned off.

Here's the kicker:  when I telnet to server 3389, I am just returned a quick command prompt.  It doesn't get through, but it doesn't return an error.

Any ideas?
0
Comment
Question by:wylde342
  • 3
  • 2
  • 2
  • +2
11 Comments
 
LVL 9

Expert Comment

by:ParadiseITS
ID: 17915577
Is this a Terminal Server or just an administrative RDC connection?


If it is just the admin RDC, My suggestion is to disable Remote Connections then reenable them.  And even reboot (if possible).


If that doesn't work, can you send me the list of the latest updates that were applied?
0
 

Author Comment

by:wylde342
ID: 17915601
It's a Terminal Server but I also use RDC on it.  I tried exactly what you said and am awaiting the reboot. I also removed Microsoft Baseline Security Analyzer b/c it errors out 4 times when the server starts up.  Just guessing....
0
 
LVL 33

Expert Comment

by:NJComputerNetworks
ID: 17915611
"when I telnet to server 3389, I am just returned a quick command prompt."  This sounds like a successful Telnet test to me..  

So you type

telnet servername 3389 <enter>

then the screen flashes and a "_" is displayed... then you click any key and your are returned to the cmd prompt?  if so, this means you are successful in your telnet test.


what error do you get when you try to RDP to the server.?
0
Enterprise Mobility and BYOD For Dummies

Like “For Dummies” books, you can read this in whatever order you choose and learn about mobility and BYOD; and how to put a competitive mobile infrastructure in place. Developed for SMBs and large enterprises alike, you will find helpful use cases, planning, and implementation.

 

Author Comment

by:wylde342
ID: 17915631
No, it just automatically cycles back to the command prompt.  In other words, I end up at the command prompt again immediately.
0
 
LVL 33

Expert Comment

by:NJComputerNetworks
ID: 17915638
Maybe the TS server ran out of licenses?  what error do you get when you try to RDP to it?


Also try this:

mstsc.exe /v servername  /console  <enter>


This will give you console access and should allow you in even if the TS licenses are not available.
0
 

Author Comment

by:wylde342
ID: 17915776
The fix...

Turned off Remote Desktop.  Uninstalled MBSA.  Rebooted  - "Gold Jerry...gold!"

Like the rest of you, I hate to reboot servers during production - but sometimes it's the easiest fix!
0
 
LVL 9

Expert Comment

by:ParadiseITS
ID: 17915822
Hmm.. interesting.. I don't think MSBA had anything to do with it... although when something throws errors like that, you never know!!
0
 
LVL 51

Expert Comment

by:Netman66
ID: 17919419
This is a common issue people have directly after updating and rebooting.  I suspect (as I have been trying to determine the exact cause) that pending file operations from the update that occur during the next reboot interfere with the TS service enough that it doesn't work.

A second reboot after patching is the only way to fix this that I have been able to determine.

0
 
LVL 51

Expert Comment

by:Netman66
ID: 18098106
The only viable answer was provided - until MS fixes this I haven't seen anything else that will bring it back to life.
0
 
LVL 1

Accepted Solution

by:
Computer101 earned 0 total points
ID: 18119253
PAQed with points refunded (500)

Computer101
EE Admin
0

Featured Post

Secure Your Active Directory - April 20, 2017

Active Directory plays a critical role in your company’s IT infrastructure and keeping it secure in today’s hacker-infested world is a must.
Microsoft published 300+ pages of guidance, but who has the time, money, and resources to implement? Register now to find an easier way.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

This may not be a text book method to resolve VSS backup issues but it seemed to have worked on few of the Windows 2003 servers we had issues while performing a Volume Shadow Copy backup. If you have issues while performing a shadow copy backup usin…
On July 14th 2015, Windows Server 2003 will become End of Support, leaving hundreds of thousands of servers around the world that still run this 12 year old operating system vulnerable and potentially out of compliance in many organisations around t…
A short tutorial showing how to set up an email signature in Outlook on the Web (previously known as OWA). For free email signatures designs, visit https://www.mail-signatures.com/articles/signature-templates/?sts=6651 If you want to manage em…

749 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question