can't route traffice across vpn connection

  • Thread starter Thread starter marsman
  • Start date Start date
M

marsman

I have created a vpn connection between two Windows 2003 Servers
though the internet. From the servers I am able to ping computers and
printers in the other network. I can't ping from pc's in one network
to the pc's or printers in the other network.

Tracing route to 172.30.2.120 over a maximum of 30 hops

1 <10 ms <10 ms <10 ms newyork1.mytest.com[192.168.168.1]
2 70 ms 70 ms 70 ms chicago1.mytest.com [192.168.168.81]
3 * * * Request timed out.
4 * * * Request timed out.


As you can see from the trace route I reach the local server and then
the remote server but I don't receive a reply from the printer on the
remote network.

any thoughts
 
I have created a vpn connection between two Windows 2003 Servers
though the internet. From the servers I am able to ping computers and
printers in the other network. I can't ping from pc's in one network
to the pc's or printers in the other network.

Tracing route to 172.30.2.120 over a maximum of 30 hops

1 <10 ms <10 ms <10 ms newyork1.mytest.com[192.168.168.1]
2 70 ms 70 ms 70 ms chicago1.mytest.com [192.168.168.81]
3 * * * Request timed out.
4 * * * Request timed out.


As you can see from the trace route I reach the local server and then
the remote server but I don't receive a reply from the printer on the
remote network.
Click to expand...

Most of the time, such (initial) problems are due to a failure
to provide ROUTES on the VPN and other involved routers.

You must be able to trace the path (manually, mentally) from
router to router by using what is in each routers routing table.

For instance, if you wish to reach a network not listed explicitly,
that packet is going to the DEFAULT router which is probably
not down the VPN but rather to the ISP for general Internet
access.

Generally, you must add Static routes in the RRAS interface (or,
less commonly use a Dynamic Routing algorythm like OSPF
to propagate the information.)
 
Back
Top