VPN connection can see other networks

[Paul Edwards]

When connecting to our VPN server I can's see/ping other networks. This
is critical because the VPN server is on 192.168.1.X and our DNS server
is on 192.168.6.X. So since I can's get to the DNS server I can't
resolve UNC names in our AD domain.

Please help. I have been fighting with this for the past week.

Thanks

 

[Eric Daniel]

Try setting up a static route in Routing & Remote Access
so that all your 192.168.1.X traffic will go to your
hardware router in your rack. Try 192.168.1.0 to
192.168.1.1 where .1 is your hardware router. That will
take care of the routing to the DNS server. You should be
able to ping through by name after that.

Regards,

Eric

 

[Paul Edwards]

Thanks Eric

When you say "where .1 is your hardware router" Would that be the
192.168.1.1 router (where the VPN is) or the 192.168.6.1 router (where
the DNS server is).

Which router address would I use in your example.

Thanks

 

[pauled]

I am connecting from my home PC.

The VPN server is on 192.168.1.1 network and the DNS server is on
192.168.6.1. The IP address for the server is 192.168.6.202.

THanks

 

[pauled]

I added the following static route.

Destination - 192.168.6.0 (Network where DNS is located)
Network Mask - 255.255.255.0
Gateway - 192.168.1.1 (This router is on the same network as VPN server)
Interface - (LAN Card 192.168.1.102)

Once I added this route I can now ping via UNC name to the 192.168.6.0
network from the VPN server. But I still can't ping the 192.168.6.0 network
from my home computer (VPN client)

Thanks

 

[Bill Grant]

It really depends on your config. What IP addresses are running on the
LAN segment where the server is?

If the remotes use "on-subnet" addresses (ie the same IP subnet as the
server's LAN NIC), the remote traffic is just forwarded on to the LAN using
normal hardware addressing. So a request from a remote user should behave
just like a request from a LAN user. The request would go to a router and be
handled as normal. When the request comes back on to the LAN from the
router, the server does proxy ARP for the client, gets the frame and
forwards it over the PPP/PPTP link.

If your remotes are in their own subnet (off-subnet addressing), you
need to enable IP routing on the RRAS server to handle routing between the
remotes and the LAN.