VPN Routing Problem-Windows 2003 Server/Vista Client
I am running a Windows 2003 server with 2 NICS in my office. The
internal LAN in the office is on 192.168.1.xxx, subnet mask
255.255.255.0. The Second NIC installed for VPN has IP
address: 192.168.1.95. I have configure RAS to work on the Second NIC.
It uses DHCP to give out IP addresses to VPN clients in the
192.168.0.xxx range.My home network and Vista client machine are on 192.168.15.xxx.I
can connect and register my Vista client machine on the network, but I
cannot ping any of the computers, including the server, in the office
network. I believe I have to set up some sort of a static route or a
classless route, or something like that, so that the VPN client machine
(192.168.0.xxx) can hop over to the office network (192.168.1.xxx). Can anyone help? By
the way, I know that the router is passing the traffic correctly
because if I set up RAS to distribute an address to the VPN client in
the 192.168.1.xxx range using the existing NIC (not the second NIC in
the server), everything works fine.
March 18th, 2007 4:19am
Hi,
This is because the machines in the network 192.168.1.xxx does not know where to send the packets destined to 192.168.0.xxx. You need to add a static route on the office machines such that to reach 192.168.0.xxx the gateway is your VPN server (192.168.1.95). This should solve the problem.
Let me know if your issue still not resolved after the above configuration.
Free Windows Admin Tool Kit Click here and download it now
March 19th, 2007 2:51pm
The VPN clients are 192.168.0.xxx. Therefore, don't I need a static route that specifies that the packets FROM 192.168.0.xxx should be sent to 192.168.1.xxx? If so, how do I do this? Also, assuming the way you wrote it is correct, how do I do that?
March 19th, 2007 6:30pm