Solved

port 3389 blocked/not listening after multiple reboots

Posted on 2012-03-16
14
342 Views
Last Modified: 2014-05-14
Hi. I cannot RDP to the server after having trouble booting the server.  This is Win 2003 Server.  Port 3389 is not listening.  All TS services are enabled. Remote Desktop is enabled in Control Panel, System.  When I do netstat -an |find "3389" I get the response UDP 0.0.0.0:3389   *:* instead of the expected response.  Can you help?
0
Comment
Question by:KaceSolver
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 6
  • 6
14 Comments
 
LVL 11

Expert Comment

by:Khandakar Ashfaqur Rahman
ID: 37731466
Check your Firewall and also check if 3389 port is in exception.Also be sure that Anti-Virus isn't blocking RDP
0
 

Author Comment

by:KaceSolver
ID: 37731537
I have done all of these.
0
 
LVL 11

Expert Comment

by:Khandakar Ashfaqur Rahman
ID: 37731564
Into your server:
telnet 127.0.0.1 3389

Then into client pc:
telnet "Server IP" 3389

What do you see ?
0
Create the perfect environment for any meeting

You might have a modern environment with all sorts of high-tech equipment, but what makes it worthwhile is how you seamlessly bring together the presentation with audio, video and lighting. The ATEN Control System provides integrated control and system automation.

 

Author Comment

by:KaceSolver
ID: 37731584
I don't get the flashing cursor - cannot telnet the port.  It isn't listening.
0
 
LVL 11

Expert Comment

by:Khandakar Ashfaqur Rahman
ID: 37731618
If you can't telnet into your server(telnet 127.0.0.1) it means service isn't running properly.You need to check services and dependencies.Start and restart service again if requires.
0
 

Author Comment

by:KaceSolver
ID: 37732324
Yes I have already tried stopping and restarting services.  I have also tried deleting the RDP-TCP connection in TS and reinstated it.  I have also booted with Remote Desktop enabled and then tried re-enabling it but the port is not listening.
0
 
LVL 11

Expert Comment

by:Khandakar Ashfaqur Rahman
ID: 37732345
Remove Remote Desktop then install again.
0
 

Author Comment

by:KaceSolver
ID: 37732466
I have done that too I'm afraid. I also reinstalled SP2 but when I rebooted it did not like the new configuration and used a previous config.  Not sure if that helps work it out?
0
 
LVL 11

Expert Comment

by:Khandakar Ashfaqur Rahman
ID: 37732501
Run Microsoft Baseline Security Analuzer:
http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=19892

Check if there's any update missing or post the result.
Are you using group policy ?
Also check the Event log if there's any error
0
 

Author Comment

by:KaceSolver
ID: 37736932
Hi.  I'll try this shortly when I can get access to the sever and will post the result. I can' see anything in event viewer that helps and we are not using group policy. Thanks.
0
 
LVL 11

Expert Comment

by:Khandakar Ashfaqur Rahman
ID: 37736941
Also try the following:

Open command prompt and type:
tasklist /svc


Post the output.
0
 

Accepted Solution

by:
KaceSolver earned 0 total points
ID: 37761192
This was tracked down to RDP crashing the print spooler caused when a Mac computer connected.  It was the Officejet driver that the Mac was using that had been installed on the server.  We discovered that with the print spooler disabled we could connect.  After removing all the printer drivers from the server everyone could connect again, including the Mac.
0

Featured Post

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.

Question has a verified solution.

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

A common practice in small networks is making file sharing easy which works extremely well when intra-network security is not an issue. In essence, everyone, that is "Everyone", is given access to all of the shared files - often the entire C: drive …
Many of us in IT utilize a combination of roaming profiles and folder redirection to ensure user information carries over from one workstation to another; in my environment, it was to enable virtualization without needing a separate desktop for each…
Michael from AdRem Software explains how to view the most utilized and worst performing nodes in your network, by accessing the Top Charts view in NetCrunch network monitor (https://www.adremsoft.com/). Top Charts is a view in which you can set seve…
If you’ve ever visited a web page and noticed a cool font that you really liked the look of, but couldn’t figure out which font it was so that you could use it for your own work, then this video is for you! In this Micro Tutorial, you'll learn yo…

707 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