Re: RDP issues

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



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@xxxxxxxxxx
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


.



Relevant Pages

  • Re: I am having connectivity problems
    ... firewall and turned ON Windows firewall. ... When I tried to install SP2 I was unable to get it thru Windows Update. ... does the connection problem persist? ...
    (microsoft.public.windows.inetexplorer.ie6.browser)
  • Re: Serious Security Issue in Windows XP SP2s Firewall
    ... Subject: AW: Serious Security Issue in Windows XP SP2's Firewall ... If you update a WinXP SP-1 with enabled Internet ... Connection Firewall ...
    (Focus-Microsoft)
  • RE: Serious Security Issue in Windows XP SP2s Firewall
    ... file and printer sharing is available for network login from any network (I ... Internet Connection Sharing of the PC has to be disabled." ... Serious Security Issue in Windows XP SP2's Firewall ...
    (Focus-Microsoft)
  • Re: Still cant connect to RWW or OWA remotely
    ... No, I don't have a 3rd party firewall, and it's a pretty plain vanilla WinXP ... Connected to the network like the other workstations, ... I could go to any workstation and connect to them just fine. ... match the broadband connection, the two NIC firewall, the remote ...
    (microsoft.public.windows.server.sbs)
  • Re: Big hole??
    ... > firewall then even they can't get in, ... > supposedly safe SP2 for Windows XP invites any Internet ... > Connection Sharing of the PC has to be disabled. ... > in fact is a common configuration and not a rare sight. ...
    (microsoft.public.windowsxp.general)