Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Port 3389 Won't Open


  • Please log in to reply
7 replies to this topic

#1 DanFM

DanFM

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:11:32 AM

Posted 07 July 2008 - 11:29 PM

I can not establish "remote desktop" connection with my desktop computer because the port 3389 on it does not want to open.
The 3389 port remains closed after numerus different things I tried.
When I do "netstat -a" on the computer the port 3389 is not showing up.

Have no issues networking to/from this computer on my home LAN.

I do have a router, software firewall and antivirus software.
However, in order to see if any of them is cause of this, I have shut them down all three and connected the computer directly to the cable modem but the "netstat -a" still not showing the 3389 port.

Needless to say, I did enable in the Windows "Allow users to connect remotely to this computer".
User name to connect is good.

I went to registry and checked if another port is used for remote desktop; not the case.

The terminal services is started and is in manual mode.

The related services have following status:

Remote Access Auto Connection Manager Not running Manual
Remote Access Connection Manager Started Manual
Remote Desktop Help Session Manager Not Started Manual
Remote Packet Capture Protocol v.0 (experimental) Not Started Manual
Remote Procedure Call (RPC) Started Automatic
Remote Procedure Call (RPC) Locator Not Started Manual
Remote Registry Started Automatic

How can I get it open?
Thanks

BC AdBot (Login to Remove)

 


#2 raw

raw

    Bleeping Hacker


  • Members
  • 2,577 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Texas
  • Local time:12:32 PM

Posted 08 July 2008 - 08:35 PM

I don't use RD, but I found this troubleshooting guide. Hope it helps.
http://theillustratednetwork.mvps.org/Remo...leshooting.html

rawsig.png

 rawcreations.net          @raw_creations


Current systems: WHAT OS, BackTrack-raw, PCLinuxOS, Peppermint OS 6, Kali Linux

and a custom Linux From Scratch server hosting a bunch of top secret stuff.


#3 DanFM

DanFM
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:11:32 AM

Posted 09 July 2008 - 11:27 AM

Thanks for the link.
I've tried couple of utilities mentioned there. They also confirmed what netstat was giving me, which is that 3389 is not listening, however those utilities are reporting utilities only, they can not do ports opening.

I also tried reinstaling remote desktop although I think that the remote desktop utility is just using port 3389 and is not the one actually in charge of opening it (it should get open by by selecting remote access option at control panel\system\remote ).
After downloading it, the installation could not be done because it reported I already have remote desktop "built-in" in my system

I also tried changing in the registry the remote port to a number different than 3389, but that port did not get open either after selecting remote access at control panel\system\remote tab.

#4 raw

raw

    Bleeping Hacker


  • Members
  • 2,577 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Texas
  • Local time:12:32 PM

Posted 09 July 2008 - 06:35 PM

I think that the remote desktop utility is just using port 3389 and is not the one actually in charge of opening it

You are correct ... Terminal Services is responsible for opening 3389.
Which version of Windows are you using?
This may or may not apply to you.
Windows 2000 has a known issue here:
http://support.microsoft.com/kb/270588/en-us

The terminal services is started and is in manual mode.

Are there any TS errors in Event Viewer?

rawsig.png

 rawcreations.net          @raw_creations


Current systems: WHAT OS, BackTrack-raw, PCLinuxOS, Peppermint OS 6, Kali Linux

and a custom Linux From Scratch server hosting a bunch of top secret stuff.


#5 DanFM

DanFM
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:11:32 AM

Posted 09 July 2008 - 11:19 PM

Which version of Windows are you using?

XP Pro, I forgot to mention that.

This may or may not apply to you.
Windows 2000 has a known issue here:
http://support.microsoft.com/kb/270588/en-us

I've checked the registry entry they were referring to, it is ok.

Are there any TS errors in Event Viewer?

There is one warning after a fresh computer start-up, however I do not think it is related to this. It refers to a third computer on my network: "The browser was unable to retrieve a list of servers from the browser master \\My_Third_Computer_Name on the network \Device\NetBT_Tcpip_{AC125467-95E1-48F0-A086-90A65D6610B7}. The data is the error code."

#6 raw

raw

    Bleeping Hacker


  • Members
  • 2,577 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Texas
  • Local time:12:32 PM

Posted 10 July 2008 - 06:27 PM

More questions...
Have you added the users to Remote Desktop Users?
http://www.helpwithwindows.com/WindowsXP/howto-14.html

rawsig.png

 rawcreations.net          @raw_creations


Current systems: WHAT OS, BackTrack-raw, PCLinuxOS, Peppermint OS 6, Kali Linux

and a custom Linux From Scratch server hosting a bunch of top secret stuff.


#7 DanFM

DanFM
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:11:32 AM

Posted 11 July 2008 - 01:31 AM

Feel free to ask.
Users are there.

#8 raw

raw

    Bleeping Hacker


  • Members
  • 2,577 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Texas
  • Local time:12:32 PM

Posted 11 July 2008 - 09:06 PM

After a ton of searching (literally hours) here is the last best solution I can find.

1. Re-registering Remote Desktop using the command line that
follows...Reboot the PC after doing this...

regsvr32 remotepg.dll

2. Otherwise do a repair install of Windows XP.

http://michaelstevenstech.com/XPrepairinstall.htm

NOTE the warnings on the page...


Disclaimer: I do not support messing with the registry.
Use this info at your own risk.
Having said that I provide you with this link to a forum thread with a batch file that appears
to have solved the problem for the user.
http://www.governmentsecurity.org/archive/t14980.html

rawsig.png

 rawcreations.net          @raw_creations


Current systems: WHAT OS, BackTrack-raw, PCLinuxOS, Peppermint OS 6, Kali Linux

and a custom Linux From Scratch server hosting a bunch of top secret stuff.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users