Unable to establish RDT thru VPN

[G Holmes]

Need help....!

I think this might be an issue with IIS on my SBS2000 server. The SBS2000
server is the end of the VPN not my router it is in PPTP passthru.
I "can" establish a solid VPN from my home pc to the server @ work.
I "can" see all shares on the server and interact thru explorer.
I "can" establish an RDT session with the server.
I "can't" establish an RDT with my workstation thru either name or IP.
I "can't" ping any workstations thru the VPN.
I have assigned static IP's for my machine and others on the network typ
SBS2000 - 10.0.1.xx. I can establish RDT between all the machines on the
loop by using IP addressing. (strange observation) In RDT window "browse" no
machines show up but by using their IP I can make a connection.?

Do I need to poke a hole thru IIS or someplace else to get to my
workstation.?
IP routing "is" enabled in RRAS but do I need to do the same in IIS ??

Thanks
Gene

 

[Alan Wood [MSFT]]

Hi Gene,
There is no need to do anything with IIS. Remote Desktop\RDP have
nothing to do with IIS unless you are using the TSAC Client which is a plug
in for IIS to provide a remote desktop connection. I have to assume you
are using the Remote Desktop client that comes with XP. Please let me know
if this is true.

In anycase, with a VPN connection to the server, you should be able to PING
the clients on the internal network. This is the problem we need solve.
The RDP connections will start working after this is resolved. Can you
please confirm that the clients Default Gateways on the internal network
are pointing the SBS server? If no, can you confirm what the IP address
that the VPN client WAN adapter gets when you VPN in? If this IP address
is a different subnet than what the internal clients are on, you will have
to create a route back from the router to the SBS server for the internal
clients to communicate with the VPN CLIENTS.

It appears you are just running into a routing issue here. Some more
network information is needed.
PPP CLIENT WAN IP ADDRESS=
DEFAULT GATEWAY ON INTERNAL CLIENTS=

These can be found using the IPCONFIG /ALL command at the command prompt.

Another test you could do is from an internal client run TRACERT IPADDRESS
(where the IPADDRESS is the IPADDRESS of a connected VPN Client)

Does this go to the Server or Router. If to the router you need to fix this
issue at the router with a static route to the VPN clients subnet to the
SBS server.

Hope this Helps!

Alan Wood[MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Marina Roos]

I'm not sure if it even can be done in SBS 2000, but the workstations to
which you want to RDT should be XP. It can be done in SBS 2003, but only
with XP-workstations.

 

[G Holmes]

Thanks Alan....I didn't really want to go digging into IIS !!!
I personnaly didn't set this system up....just trying to figure it out. I
know all stations on all loops can access the internet with a permission
set.
All internal workstations are running XP Pro.
Home workstations are XP Pro also.
All workstations "will" RDT within the loop 10.0.1.xx of dedicated IP's and
all I care about are these ones for outside RDT.

I am unsure of the workstation gateway setting at this moment. I would have
to check that Monday unless there is a way to retrieve it from the server
because I can RDT with it at will.
But I am sure that the VPN server IP is 192.168.7.100 and the client is
192.168.7.xxx (variable) on connection.

Loopback = 127.0.0.1
Internal = 192.168.7.100

(3) NIC's in this machine:
1 to the router..192.168.7.2
1 to 10.0.1.xx = Dedicated IP's
1 to 10.0.0.xx = DHCP

If this is a enough to help me....let me know. If not let me know what
else you need.

Thanks
Gene

 

[G Holmes]

FIXED.!!
It appears that by forcing the workstations on the static loop to use the
server 10.0.x.xx IP on that sub as the default gateway, all is fixed.! RDT
over the VPN working like a bear.
I want to thank all who tried different solutions.

Gene