Hey all.

I am having RDP issues w/ one of my workstations.

This particular workstation is WinXP SP3. What happens is that I cannot make
an RDP connection to it. When I try to - almost immediately I get an error
saying I cannot make the connection: "This computer can't connect to the
remote computer", and feels as if some sort of firewall was blocking the
connection.

There are no firewalls on both computers. The said WS *is* able to make RDP
connection to our servers here, and to some other workstations, however, to
some - it can't connect (it seems that it particularly can't make the
connection to other SP3 WS's.

The WS has Symantec AntiVirus 10.1.8 installed. I have tried
enabling/disabling the firewall, adding the ports to exceptions, stopping
the serivce (all those on the said WS and my own from which I'm trying to
make the connection). After trying different ways, I have reinstalled the
OS, however, no use - I still have got the problem. I have tried
uninstalling the SAV completely, including every single registry entry for
it. I have tried changing the network cards (and some other things which I
don't remember right now).

When using netstat, I can't see the XP listening on 3389, although this is
the port specified to be open in the registry.

Any ideas? Any? I've Googled through hundreds of pages, but nothing seems to
help.

I'd be happy to get any advice. TIA.

--

- - - - - - - - - -
Jonathan M. Boyko
"Aba Computer Systems LTD."

"All that is necessary for evil to succeed is for good men to do nothing."
-Edmund Burke

>I am having RDP issues w/ one of my workstations.
>
>This particular workstation is WinXP SP3. What happens is that I cannot make
>an RDP connection to it. When I try to - almost immediately I get an error
>saying I cannot make the connection: "This computer can't connect to the
>remote computer", and feels as if some sort of firewall was blocking the
>connection.
>
>There are no firewalls on both computers. The said WS *is* able to make RDP
>connection to our servers here, and to some other workstations, however, to
>some - it can't connect (it seems that it particularly can't make the
>connection to other SP3 WS's.
>
>The WS has Symantec AntiVirus 10.1.8 installed. I have tried
>enabling/disabling the firewall, adding the ports to exceptions, stopping
>the serivce (all those on the said WS and my own from which I'm trying to
>make the connection). After trying different ways, I have reinstalled the
>OS, however, no use - I still have got the problem. I have tried
>uninstalling the SAV completely, including every single registry entry for
>it. I have tried changing the network cards (and some other things which I
>don't remember right now).
>
>When using netstat, I can't see the XP listening on 3389, although this is
>the port specified to be open in the registry.
>
>Any ideas? Any? I've Googled through hundreds of pages, but nothing seems to
>help.
>
>I'd be happy to get any advice. TIA.

XP SP3 comes with the new RDP 6.1 client and, usually, the destination
IP shouldn't matter. Is the windows firewall on the trouble WS on or
off? Firewall service enabled or disabled?

You could try and see if this hotfix and accompanying registry setting
helps: http://support.microsoft.com/kb/956072

Is the NIC driver current? Is the subnetting or VLAN stuff going on?

- Thee Chicago Wolf

Hi.

I've tried the hotfix you've provided, however, to no avail.

I've tried several configurations at the problematic WS and mine (which is
just fine) - firewall wise. At the moment the FW service is running but the
FW itself is in Off state. At both WS's the RDP is in the exception list.
I've tried enabling and disabling FW's at both WS's. I've tried disabling
the FW service. Nothing works.

Although the error does not indicate the connection is being refused, it
sure seems so, as the RDP doesn't wait for a timeout to give me the error,
it happens almost instantaneously.

--

- - - - - - - - - -
Jonathan M. Boyko
"Aba Computer Systems LTD."

"All that is necessary for evil to succeed is for good men to do nothing."
-Edmund Burke
"Thee Chicago Wolf" <.@.> wrote in message
news:4fvsj4tfcfr9bcqhe1f70s1pi1n4llpsis@4ax.com...
> >I am having RDP issues w/ one of my workstations.
>>
>>This particular workstation is WinXP SP3. What happens is that I cannot
>>make
>>an RDP connection to it. When I try to - almost immediately I get an error
>>saying I cannot make the connection: "This computer can't connect to the
>>remote computer", and feels as if some sort of firewall was blocking the
>>connection.
>>
>>There are no firewalls on both computers. The said WS *is* able to make
>>RDP
>>connection to our servers here, and to some other workstations, however,
>>to
>>some - it can't connect (it seems that it particularly can't make the
>>connection to other SP3 WS's.
>>
>>The WS has Symantec AntiVirus 10.1.8 installed. I have tried
>>enabling/disabling the firewall, adding the ports to exceptions, stopping
>>the serivce (all those on the said WS and my own from which I'm trying to
>>make the connection). After trying different ways, I have reinstalled the
>>OS, however, no use - I still have got the problem. I have tried
>>uninstalling the SAV completely, including every single registry entry for
>>it. I have tried changing the network cards (and some other things which I
>>don't remember right now).
>>
>>When using netstat, I can't see the XP listening on 3389, although this is
>>the port specified to be open in the registry.
>>
>>Any ideas? Any? I've Googled through hundreds of pages, but nothing seems
>>to
>>help.
>>
>>I'd be happy to get any advice. TIA.
>
> XP SP3 comes with the new RDP 6.1 client and, usually, the destination
> IP shouldn't matter. Is the windows firewall on the trouble WS on or
> off? Firewall service enabled or disabled?
>
> You could try and see if this hotfix and accompanying registry setting
> helps: http://support.microsoft.com/kb/956072
>
> Is the NIC driver current? Is the subnetting or VLAN stuff going on?
>
> - Thee Chicago Wolf

>I've tried the hotfix you've provided, however, to no avail.
>
>I've tried several configurations at the problematic WS and mine (which is
>just fine) - firewall wise. At the moment the FW service is running but the
>FW itself is in Off state. At both WS's the RDP is in the exception list.
>I've tried enabling and disabling FW's at both WS's. I've tried disabling
>the FW service. Nothing works.
>
>Although the error does not indicate the connection is being refused, it
>sure seems so, as the RDP doesn't wait for a timeout to give me the error,
>it happens almost instantaneously.

This is a weird issue especially since other SP3 machines work fine
and you've also reformatted and re-installed XP. When you re-installed
the OS, was this from a slipstreamed SP3 CD? Are things like BIOS
current? NIC driver is current as well? Single NIC or dual-NIC WS?

Since you say you're able to RDP to a server but just not some other
WS, it almost makes me think the LAN connection to those others is
somehow getting tripped up. Firewall is always going to give RDP an
automatic exception by design and by default so it can't be firewall
related. PING and tracert the IPs that you are able to RDP to and then
do the ones you cannot reach. How is the LAN set up? Is the server you
can reach on the same subnet? What about the WSs that you cannot RDP
into? Are you static IP or DHCP/BootP?

It wouldn't hurt to install this KB hotfix as it is an updated
component of RDP: http://support.microsoft.com/kb/957070
At worst, you'll still be where you're at.

- Thee Chicago Wolf

>I've tried the hotfix you've provided, however, to no avail.
>
>I've tried several configurations at the problematic WS and mine (which is
>just fine) - firewall wise. At the moment the FW service is running but the
>FW itself is in Off state. At both WS's the RDP is in the exception list.
>I've tried enabling and disabling FW's at both WS's. I've tried disabling
>the FW service. Nothing works.
>
>Although the error does not indicate the connection is being refused, it
>sure seems so, as the RDP doesn't wait for a timeout to give me the error,
>it happens almost instantaneously.

Oh yes, one more thing. By default, QoS service is in the Local Area
Connection Properties, uninstall it an reboot and see if that helps
any.

- Thee Chicago Wolf