RDP port fails to load on XP Pro svc pack 2

RDP was working fine on this new Dell with XP Pro. With no changes to the
machine, RDP will no longer open port 3389. The Term. Server service is
running and Fast User Switching (which is supposed to be a dependency) works
fine. I have reviewed the RDP registry settings and 3389 is defined there ok.
Windows firewall shows 3389 enabled but it makes no difference with it turned
on or off. Remote users is enabled. Searching this forum and Google and
looking at all mentioned checks shows all to be ok. Also copied in all RDP*
files from a known good machine's system32 folder and that did nothing.

Any clues will be appreciated.

Les

Are you running NAV 2005 or OneCare Live Beta? Both of those have caused
problems for other folks...

If you do a "netstat -an" command from the command line is the PC listening
on port 3389?

http://theillustratednetwork.mvps.or...eshooting.html

--

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...

"LesH" <LesH@discussions.microsoft.com> wrote in message
news:C2EFCB9C-0B79-4D35-87C5-E2BEB9447FA9@microsoft.com...
> RDP was working fine on this new Dell with XP Pro. With no changes to the
> machine, RDP will no longer open port 3389. The Term. Server service is
> running and Fast User Switching (which is supposed to be a dependency)
> works
> fine. I have reviewed the RDP registry settings and 3389 is defined there
> ok.
> Windows firewall shows 3389 enabled but it makes no difference with it
> turned
> on or off. Remote users is enabled. Searching this forum and Google and
> looking at all mentioned checks shows all to be ok. Also copied in all
> RDP*
> files from a known good machine's system32 folder and that did nothing.
>
> Any clues will be appreciated.
>
> Les

This PC has Symantec Corporate Anti-Virus version 8 running. I have 19 more
just like it that are running ok. We have been running with this
configuration for several years.

No the listener port 3389 is not running which is why Remote Desktop will
not connect.

Thanks for your reply.

Les

"Sooner Al [MVP]" wrote:

> Are you running NAV 2005 or OneCare Live Beta? Both of those have caused
> problems for other folks...
>
> If you do a "netstat -an" command from the command line is the PC listening
> on port 3389?
>
> http://theillustratednetwork.mvps.or...eshooting.html
>
> --
>
> 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...
>
> "LesH" <LesH@discussions.microsoft.com> wrote in message
> news:C2EFCB9C-0B79-4D35-87C5-E2BEB9447FA9@microsoft.com...
> > RDP was working fine on this new Dell with XP Pro. With no changes to the
> > machine, RDP will no longer open port 3389. The Term. Server service is
> > running and Fast User Switching (which is supposed to be a dependency)
> > works
> > fine. I have reviewed the RDP registry settings and 3389 is defined there
> > ok.
> > Windows firewall shows 3389 enabled but it makes no difference with it
> > turned
> > on or off. Remote users is enabled. Searching this forum and Google and
> > looking at all mentioned checks shows all to be ok. Also copied in all
> > RDP*
> > files from a known good machine's system32 folder and that did nothing.
> >
> > Any clues will be appreciated.
> >
> > Les
>
>
>

Sooner, thanks to your reply, I was looking back in the event viewer in the
System area and spotted
this event:
"cannot load illegal module C:\windows\system32\drivers\tdtcp.sys"

I copied in this file and c:\windows\system32\drivers\termdd.sys to the
failed system from a working system and rebooted the failed system. Thank
God, the sucker is working fine. Been at this for two days and missed that
event message somehow.

Thanks,
Les




"Sooner Al [MVP]" wrote:

> Are you running NAV 2005 or OneCare Live Beta? Both of those have caused
> problems for other folks...
>
> If you do a "netstat -an" command from the command line is the PC listening
> on port 3389?
>
> http://theillustratednetwork.mvps.or...eshooting.html
>
> --
>
> 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...
>
> "LesH" <LesH@discussions.microsoft.com> wrote in message
> news:C2EFCB9C-0B79-4D35-87C5-E2BEB9447FA9@microsoft.com...
> > RDP was working fine on this new Dell with XP Pro. With no changes to the
> > machine, RDP will no longer open port 3389. The Term. Server service is
> > running and Fast User Switching (which is supposed to be a dependency)
> > works
> > fine. I have reviewed the RDP registry settings and 3389 is defined there
> > ok.
> > Windows firewall shows 3389 enabled but it makes no difference with it
> > turned
> > on or off. Remote users is enabled. Searching this forum and Google and
> > looking at all mentioned checks shows all to be ok. Also copied in all
> > RDP*
> > files from a known good machine's system32 folder and that did nothing.
> >
> > Any clues will be appreciated.
> >
> > Les
>
>
>

Well if the PC is not listening on TCP Port 3389 you never will connect. I
would disable/uninstall the Symantec package to see if that makes a
difference.

--

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...

"LesH" <LesH@discussions.microsoft.com> wrote in message
news:C301AB7C-56E2-4B7F-9534-BBDD0C2473DD@microsoft.com...
> This PC has Symantec Corporate Anti-Virus version 8 running. I have 19
> more
> just like it that are running ok. We have been running with this
> configuration for several years.
>
> No the listener port 3389 is not running which is why Remote Desktop will
> not connect.
>
> Thanks for your reply.
>
> Les
>
> "Sooner Al [MVP]" wrote:
>
>> Are you running NAV 2005 or OneCare Live Beta? Both of those have caused
>> problems for other folks...
>>
>> If you do a "netstat -an" command from the command line is the PC
>> listening
>> on port 3389?
>>
>> http://theillustratednetwork.mvps.or...eshooting.html
>>
>> --
>>
>> 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...
>>
>> "LesH" <LesH@discussions.microsoft.com> wrote in message
>> news:C2EFCB9C-0B79-4D35-87C5-E2BEB9447FA9@microsoft.com...
>> > RDP was working fine on this new Dell with XP Pro. With no changes to
>> > the
>> > machine, RDP will no longer open port 3389. The Term. Server service is
>> > running and Fast User Switching (which is supposed to be a dependency)
>> > works
>> > fine. I have reviewed the RDP registry settings and 3389 is defined
>> > there
>> > ok.
>> > Windows firewall shows 3389 enabled but it makes no difference with it
>> > turned
>> > on or off. Remote users is enabled. Searching this forum and Google and
>> > looking at all mentioned checks shows all to be ok. Also copied in all
>> > RDP*
>> > files from a known good machine's system32 folder and that did nothing.
>> >
>> > Any clues will be appreciated.
>> >
>> > Les
>>
>>
>>

Ok... Thanks for the update and glad to hear its working...

--

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...

"LesH" <LesH@discussions.microsoft.com> wrote in message
news:FD6E2536-AEE6-4224-9420-25D8188F7416@microsoft.com...
> Sooner, thanks to your reply, I was looking back in the event viewer in
> the
> System area and spotted
> this event:
> "cannot load illegal module C:\windows\system32\drivers\tdtcp.sys"
>
> I copied in this file and c:\windows\system32\drivers\termdd.sys to the
> failed system from a working system and rebooted the failed system. Thank
> God, the sucker is working fine. Been at this for two days and missed that
> event message somehow.
>
> Thanks,
> Les
>
>
>
>
> "Sooner Al [MVP]" wrote:
>
>> Are you running NAV 2005 or OneCare Live Beta? Both of those have caused
>> problems for other folks...
>>
>> If you do a "netstat -an" command from the command line is the PC
>> listening
>> on port 3389?
>>
>> http://theillustratednetwork.mvps.or...eshooting.html
>>
>> --
>>
>> 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...
>>
>> "LesH" <LesH@discussions.microsoft.com> wrote in message
>> news:C2EFCB9C-0B79-4D35-87C5-E2BEB9447FA9@microsoft.com...
>> > RDP was working fine on this new Dell with XP Pro. With no changes to
>> > the
>> > machine, RDP will no longer open port 3389. The Term. Server service is
>> > running and Fast User Switching (which is supposed to be a dependency)
>> > works
>> > fine. I have reviewed the RDP registry settings and 3389 is defined
>> > there
>> > ok.
>> > Windows firewall shows 3389 enabled but it makes no difference with it
>> > turned
>> > on or off. Remote users is enabled. Searching this forum and Google and
>> > looking at all mentioned checks shows all to be ok. Also copied in all
>> > RDP*
>> > files from a known good machine's system32 folder and that did nothing.
>> >
>> > Any clues will be appreciated.
>> >
>> > Les
>>
>>
>>