XP Home RDS Client Error

[techkate]

I have a question about Remote Desktop. I've never used it before, but now that my husband has to use it for work I've found that I'm having some problems with it...

I have XP Home SP 1. No firewalls are running. The windows firewall is not enabled on either my LAN connection or my VPN connection.

Also, under computer properties, I have the box 'allow remote assistance invitations to be sent from this computer' checked. I also have the box that says 'allow this computer to be controlled remotely' checked, although I believe that does not apply in this case.

I can successfully connect to the VPN, and I can also ping the computer that I am supposed to remote into. However, when I click 'Connect' in the Remote Desktop program, I get the following error:

Client could not connect to the Remote Computer.

Remote connections might not be enabled or the computer might be too busy to accept new connections.  It is possible that network problems are preventing your connection.

Please try connecting again later.

Is there any way to test my ability to connect to this port or something like that? Any assistance or suggestions are greatly appreciated.

Thanks for your time,
Katie

 

[techkate]

Sorry...make that RDP rather than RDS...

 

[linney]

Just to be clear Home will connect via Remote Desktop to Pro, but Pro will not connect by Remote Desktop to Home.

How to Use the Remote Desktop Feature of Windows XP Professional

http://support.microsoft.com/default.aspx?scid=kb;en-us;315328&FR=1&PA=1&SD=HSCH

 

[techkate]

Here's some more information.

I'm having trouble connecting remotely to an XP Pro machine on a VPN from an XP Home SP1 computer at my house.

Let's call the XP Pro unit Unit A and the XP Home Unit Unit B.

The VPN looks to be connecting and running correctly. All necessary functionality seems to be there and in good working order.

As a recap, I cannot establish a remote desktop session TO Unit A FROM Unit B. I get the following error:

Client could not connect to the Remote Computer.

Remote connections might not be enabled or the computer might be too busy to accept new connections.  It is possible that network problems are preventing your connection.

Please try connecting again later.

Running netstat on Unit A shows that port 3389 is listening, and also on Unit A, all properties under the 'Remote' tab in the computer properties dialog shows that Remote Desktop is enabled in all aspects.

However, I am able to establish a remote desktop session to Unit A FROM my workplace on a computer running XP Pro SP1.

What could possibly be stopping me on Unit B from establishing a remote desktop session with Unit A?

 

[aftertaf]

are you using the host name or the ip address ??

Aftertaf (david)
MCSA 2003

 

[techkate]

I've tried it all...I think.

Once I get to the vpn, I can ping by name and IP. In the computer name field, I've entered the computer name, the Ip, and also combinations of the computer name and domain like 'workcomputername.workdomain.com'. I've tried different variations of domain, with the domain name, and also .com following it, etc. I've tried entering no login information and only the computer name, and I've also tried all computer information.

The thing is, when I successfully established a session from my work computer, (Unit C), I went home and tried entering the same exact information and I still got that error.

I've also tried using the full domain username, like 'domain\username' and things like that. It is just so freakin frustrating, unfortunately I don't have the cash to upgrade to XP Pro, but I am assuming that would help.

 

[bcastner]

Start by upgrading your RDP program:

http://download.microsoft.com/download/8/e/8/8e88f947-3b95-49b8-a76d-b647bb86e4b4/MSRDPCLI.EXE

This is the RDP client program used with Service Pack 2. It will install on non-SP2 level machines.

 

[techkate]

I can't recall the exact webpage, but I have tried downloading the RDP client recently from a Microsoft site. But, perhaps that wasn't the most recent version. On the install I tried, it said I already have the program installed. But anything is worth a try, and I'll give it a shot when I get home today.

Thanks!

 

[aftertaf]

from home, you use a VPN connection to connect to 'A' via it's VPN... is that right?

from work, with 'C' you can connect to 'A'. Is this with the same type of VPN connection?

have you tried connecting from 'A' to 'C'-silly question. Home edition doesn't have the remote server...

in your client vpn connection on 'A', there isn't a use default gateway option you can tick?

i agree, damn pain!!

but if xp pro can accept connections, xp home can establish them!...
does xp home have remote assistance?

Aftertaf (david)
MCSA 2003

 

[techkate]

Yes, 'B' and 'C' use the same exact VPN to connect to 'C', and the same exact username to connect to the VPN. Also the same Remote Desktop credentials.

Well, connecting from 'A' (husband's work pc) to 'C' (my work pc) in theory should work but I don't have VPN access to 'C'. What I think you mean is connecting from 'B' (my home pc) to 'C' (my work pc). I think this would be a good test of 'B's ability to establish any session whatsoever, not just to 'A'. Once again, though, I don't have VPN access to 'C'.

Default gateway option...hmm...I can't recall...I'll look into that tonight as well...

From my understanding, yes it does. At least thats what it looks like.

 

[techkate]

Ok, stupid answer to the problem. I thought[/] I had my ZoneAlarm firewall all taken care of. I removed the program from my startup...but I never knew of the True Vector service, which was set to automatic startup. Seems as though this was the culprit.

Thanks for all your help!