not listening on port 3389

5 views
Skip to first unread message

jds

unread,
Nov 27, 2006, 9:41:01 PM11/27/06
to
I recently reformatted my system and have got everything back into perfect
condition except I cannot get RD to work. Attempting to connect returns the
generic error message of "The client could not connect to the remote
computer..." Before reformatting, RD worked just fine. I have done all the
usual stuff and tried a lot of other tricks too. Also, I have found a problem
identical to mine, with no resolution at:
http://groups.google.com/group/microsoft.public.windowsxp.work_remotely/browse_thread/thread/9c0f1a7e03260c3b/ced8f94d263f1fc3?lnk=st&q=remote+desktop+not+listening+port+3389&rnum=3&hl=en#ced8f94d263f1fc3

FYI:
RD doesn't even work in my home LAN; nothing has changed except for
reformatting my PC.

All other network functions work to and from my PC

I have tried the suggestions in several forums to no avail. I have also
tried changing the port number

I have verified that 'terminal services' is running, but there is no
listening on port 3389. Again, the problem is just like the one in the Google
Groups link.

I have no software firewall running at present - not even Windows firewall.
I am runnng AVG, which shouldn't make a difference

I have tried reaching the PC by its NetBIOS name as well as its IP

I really, really, really, want to avoid reformatting my PC if at all
possible - I don't want to have to do it again.
Everything seems to be the way it should be (setting appear correct,
services are running, etc), except it's not listening on port 3389! I've
tried to find a solution, tried what I did find, but I couldn't find much for
concrete solutions. One thing I'm concerned about is changing the
authentication settings. I seem to remember finding a setting with 3
different levels of authentication for RD and may have adjusted it. Does
anyone know what I'm talking about?

I'd really appreciate any suggestions, links, solutions, etc that anyone may
have. Thanks!


Sooner Al [MVP]

unread,
Nov 28, 2006, 6:24:25 AM11/28/06
to
So your not running anything like NAV worm protection or OneCare Live that
may be blocking incoming RDP requests?

How about any VPN client software? I have seen reports of a Cisco VPN client
that causes issues with RDP...

http://tinyurl.com/moeye
http://tinyurl.com/jf96z

Anything in the event logs that may provide a clue...

--

Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the
mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...

"jds" <j...@discussions.microsoft.com> wrote in message
news:758AC68B-5137-4A85...@microsoft.com...

John

unread,
Nov 28, 2006, 10:53:08 AM11/28/06
to
Do you have a password set on the account you want to remote in with? Sounds
stupid but it is a requirement.

"jds" <j...@discussions.microsoft.com> wrote in message
news:9DBA9947-0893-418E...@microsoft.com...
> No, I do not have any NAV products, in fact I uninstalled AVG, but it made
no
> difference. Now I have no antivirus or firewall software installed at
> present. I'm not using any VPN software, so that's out. I check the logs
in
> computer management and didn't see anything that seemed to be relevant to
RD
> ffailure. Any other logs that I may have missed?
> Do you have any other troubleshooting steps? Thanks for the info so far.


Sooner Al [MVP]

unread,
Nov 28, 2006, 2:26:54 PM11/28/06
to
If you have tried the reregistering of Remote Desktop, ie. run the
command...

regsvr32 remotepg.dll

...then reboot the PC, and that did not fix it then I suggest a repair
installation. Note the warnings on the page...

http://michaelstevenstech.com/XPrepairinstall.htm
http://support.microsoft.com/kb/917964

Good luck...

--

Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the
mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...

"jds" <j...@discussions.microsoft.com> wrote in message

Reply all
Reply to author
Forward
0 new messages