VPN and Remote Desktop

[Mattb7]

I have SonicWall Global VPN client set up to connect to a server at a different office. From home, not behind a router I can connect to the server and then use remote desktop to get on to it. At my office I am behind a Linksys Hpro200 phoneline router and cannot get to the server. When I connect to the sonicwall vpn, it says it's connected, but when i try to start remote desktop i get the 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 problems are preventing your connection.
I have contacted Linksys and have forwarded ports 500, 47, 1723, 50, and 3389. I have the most recent firmware and it still doesnt work. This is driving me nuts. Please help!
TIA
Matt

 

[Peping]

Mattb7,

Open Ports 80 and 3389.

Peping

 

[c1utch]

Is your RDP client trying to connect via the server name or just its IP address?

Chris

 

[Mattb7]

It is trying to connect with the IP address, and that works fine from home when not behind a router.

 

[mbroeder]

I am having a problem with one user that was able to connect once through Remote Desktop then following attempts to connect have resulted in the following error: The client could not establish a connection to the remote computer
The most likely causes for this error are
1) remote connections might not be enabled at the remote computer
2) maximum number of connections was exceeded at the remote computer
3) a network error occurred while establishing the connection.

In the event log I get the following warning: The terminal server cannot issue a license.
She went to another computer and it did the same thing, allowed her the first time and then subsequent attempts are denied.
I see two licenses under Terminal services temporary licenses. And there are no active jobs, for her, under terminal services.
Any ideas would be greatly appreciated.
Thanks in advance

 

[larlew]

I am seeing the exact same problem.
Was this problem ever resolved??

 

[ElTech]

I have not been able to fix this issue.
I tried the following so far:

removed and re-installed the Remote Desktop Client
Upgraded my Router's Firmware

 

[larlew]

I've solved my problem. I have the Norton Personal Firewall (NIS 2003) running on my Windows XP Pro system. The firewall was set to automatically configure internet access for the Microsoft Remote Desktop application. For some reason the firewall would only allow port 3389 to pass if someone was logged on to the system locally!

Once I connected remotely and logged out - my system would no longer accept traffic on port 3389 and I would receive the dreaded "client could not establish a connection" error message. I suppose I would have been okay if I had disconnected without logging off the system.

I manually created a new rule so that port 3389 is always open and my problem is solved. FYI- my system sits behind a Linksys router and port 3389 is being forwarded.

 

[kofu]

I had the exact problem even having the firewall disabled. FYI, my router is Netgear MR814 and port 3389 is forwarded. I even have the UPnP enabled even though I believe UPnP can't do remote desktop.