Discussion Locked

vpn connection to nt server

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have 1 ntserver running sp6.
Loaded are TCP\IP and PPTP.
2 nic cards installed one on the Internet and one on my internal network.
I can login to the server via VPN.
But i am unable to communicate with the internal network from the client vpn user desktop. (ie-Ping )
i do not have pptp filtering on.
How do i route my vpn client over to the resources on my internal network?

9 replies

by mtodd_robinson

Do you have IP forwarding enabled? It is located on the last tab of the IP properties popup. This allows routing between the 2 NICs.

Todd

by stillatit

When you log into the vpn, the vpn system gives you an IP address. You can either specify an address or take the one the server offers. The server routes this address back to the user.

The problem comes in when the address you use is unknown to the rest of your network. For example, if your network is 192.168.0.0 and you give out an address on 192.168.1.0, the machines in your network do not have a return route for the traffic.

Possible solutions include:
1. Put the subnet the vpn server gives out into a static route in your main (default) router. A station on your net, not knowing how to send to you, sends to the router, which knows to route the traffic to the vpn server. (This is the one we use.)
2. If you do not have a defaultrouter on your network, have all staions point to the vpn server as a default gateway.
3. Put a static route for the subnet, pointing at the vpn server, in each computer you will want to talk to from the vpn.
4. If you are running multiple segments on your LAN you may need static routes in more than one router depending on where your intenet access enters your network.

Good luck.

by shmaltz

Make sure on both ends, the clients and the server its setup to logon to entire notwork not only to the server.

by tyler.anderson

I had this same issue. I had clients logging in to a PIX that also happened to be the default gateway for the network, and I could log in but coudn't ping. I simply gave the clients IP addresses on a differant subnet, which caused the packets to go back to where the VPN was terminating and thus sent back to me. If your connection point isn't the default gateway, you can just add a static route.

This discussion is closed to new replies.