Terminal Services over VPN

Archived from groups: microsoft.public.windowsnt.terminalserver.connectivity (More info?)

I am trying to troubleshoot a strange problem for one of my clients and
having some problems figuring out what's going on.

They have a Windows 2000 Server, running Terminal Services in Remote
Administration mode. We have VPN setup on the server (using Windows built
in VPN feature - RRAS). From any remote machine, I can connect to the
server with VPN, I can ping the server, telnet into the server, even access
PCAnywhere on the server over the VPN using the servers private IP.
However, when I try to connect with Remote Desktop, I get the following
message:

"The Client Could not Connect to the Remote Computer. Remote connections
might not be enabled or the comptuer may be too busy... etc."

There is a Sonicwall TZ 170 in front of the server, but port 3389 is open
going both ways. In fact, I can connect using Remote Desktop to the public
IP when I am not connected to the VPN, which means that the firewall is
definitely letting the traffic through, but once I connect to the VPN I
cannot connect using Remote Desktop to the private IP. We are hoping to
resolve the issue with the VPN so we can close off Terminal Service access
to the public IP.

Any advice is greatly appreciated.

Thank you!

Sincerely,
Matt Schwartz