Go Premium for a chance to win a PS4. Enter to Win

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

Remote Desktop stopped working after Windows Update

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
wylde342
Asked:
wylde342
  • 3
  • 2
  • 2
  • +2
1 Solution
 
ParadiseITSCommented:
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
 
wylde342Author Commented:
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
 
NJComputerNetworksCommented:
"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
Prepare for your VMware VCP6-DCV exam.

Josh Coen and Jason Langer have prepared the latest edition of VCP study guide. Both authors have been working in the IT field for more than a decade, and both hold VMware certifications. This 163-page guide covers all 10 of the exam blueprint sections.

 
wylde342Author Commented:
No, it just automatically cycles back to the command prompt.  In other words, I end up at the command prompt again immediately.
0
 
NJComputerNetworksCommented:
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
 
wylde342Author Commented:
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
 
ParadiseITSCommented:
Hmm.. interesting.. I don't think MSBA had anything to do with it... although when something throws errors like that, you never know!!
0
 
Netman66Commented:
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
 
Netman66Commented:
The only viable answer was provided - until MS fixes this I haven't seen anything else that will bring it back to life.
0
 
Computer101Commented:
PAQed with points refunded (500)

Computer101
EE Admin
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

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