XP Remote Desktop issues

[Ulfwald]

Ok, here is the situation:

Windows XP on a Windows 2000 AD Domain. Guy wants to access the PC from Home. The office is on DSL with a linksys router/firewall.

Machine is set up on the domain, and i can access the ts web from within the domain, but If i am remote, I cannot. Port 3389 is opened and forwarded to the machines static IP address.
The error message is a VB script error.

The 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 also possible that network probles are preventing your connection. Please try reconnecting again later. If the problem continues to occur, contact your administrator.

I set up the XP remote desktop according to what microsoft says to do. forwarded port 3389 and 80 to the internal ip address of 192.168.1.230, and I get the remote log in screen, but when I try to access the desktop, it gives methe above error message.

I can even connect to the static IP from within the firewall, and it even connects up. but not if a machine is outside the firewall. XP's firewall is turned off. Please help. I have troubleshot this to the best I can.

 

[Zugzwang152]

This is XP Pro correct? XP Home cannot serve as a RD server...


Have you enabled Remote Desktop connections in System Properties/Remote?

 

[Ulfwald]

YES: XP PRO: YES REMOTE DESKTOP IS ENABLED.

 

[dphantom]

This question looks like one from a similar thread. See "remote desktop with xp". Here's what one member (Slikkster) suggested. See the thread for all the context.

In your router, map the port numbers you've chosen to your various machines IP addresses and the 3389 port. For example, map:

Port 4000 to 192.168.1.1:3389

Port 4001 to 192.168.1.2:3389

(whatever your IP addresses are...I just used the above as examples.)

Now, when you are trying to connect from an external address, you would type in the external address of your router, followed by a colon and the port number for your machine in question. So, say your router was 24.232.3.4 and you wanted to reach your internal machine at 192.168.1.2, you would direct Remote Desktop at work to:

24.232.3.4:4001

Since you have remote connections enabled, the above should work.

 

[Ulfwald]

DPHANTOM: Tried that. can't get it to work.

I think I am going to try VNC 4 for this.

 

[JackMDS]

Originally posted by: Ulfwald
DPHANTOM: Tried that. can't get it to work.

I think I am going to try VNC 4 for this.

Yap, that is what I would do under such situation.

Link to: Ultr@VNC (Remote Control for your Network/Internet) - Installation, and Settings

:sun:

 

[Wik]

Did you open the ports on the DSL modem? In most cases, the DSL modem is also a router. So your linksys router is actually already on a private IP.

 

[Zugzwang152]

Originally posted by: Wik
Did you open the ports on the DSL modem? In most cases, the DSL modem is also a router. So your linksys router is actually already on a private IP.

Hmm, this is interesting. Why would you need a router built in when in most cases its just for 1 computer?

 

[Ulfwald]

The machine is on a small domain, behind a firewall. The modem is nothing but a modem. it is not a router/firewall as well.

 

[dphantom]

try something like VNC. Jack above likes UltraVNC, a very good product. Some of my staff also use RealVNC

http://www.realvnc.com/

 

[saxophonoia]

What service pack is on the machine?

 

[Ulfwald]

Machine is running SP2, but I have the firewall turned off, since it is behind a linksys firewall.