can't see other networks

[pauled]

When I connect to our office VPN server from my home PC I can only see the
local network that the VPN server is on (192.168.1.0)

Seeing the other networks through the VPN connection is critical because our
DNS server is on 192.168.6.0 network.

On my home PC I can ping only the local network (192.168.1.0).
When I run a tracerout to the 192.168.6.0 network it goes out on my internet
connection and not through the VPN tunnel.

How do I fix this?
Do I need to add static routes? If so, what info needs entered. I have all
the router numbers but I am just not sure what numbers go where.

Thanks in advanced

 

[Herb Martin]

When I connect to our office VPN server from my home PC I can only see the
local network that the VPN server is on (192.168.1.0)

What do you mean by "see" (and one never "sees" a "network" but only
machines
ON those networks.)

Do you mean see in Explorer/Network Neighborhood? If so then it is likely
a NetBIOS issue where you may need a WINS server (multiple subnets generally
require WINS for NetBIOS resolution.)

Seeing the other networks through the VPN connection is critical because our
DNS server is on 192.168.6.0 network.

If you mean connected to, given a name or address then you likely have a
name resolution or perhaps a routing problem.

What happens when you ping or use tracert by NUMBER verses name?

On my home PC I can ping only the local network (192.168.1.0).
When I run a tracerout to the 192.168.6.0 network it goes out on my internet
connection and not through the VPN tunnel.
How do I fix this?

With a static route -- on the machine with a VPN, give a static route to the
other network that can be reached through the VPN -- specify the VPN as
the interface. Use the RRAS interface since it does not require a gateway
"address" for such dynamically connected interfaces (it's smart enough to
use
whatever is available on connect.)

Do I need to add static routes? If so, what info needs entered. I have all
the router numbers but I am just not sure what numbers go where.

Yes.

 

[Paul Edwards]

The VPN server is 192.168.1.102.
The DNS is 192.168.6.202.

Since I can't get to the 192.168.6.0 network (where the DNS server is) I
can't ping anthing via hostname. Which I understand.

The problem is that I can't even ping computers or servers on the
192.168.6.0 network using IP address.

When I connect to the VPN server from my home pc and tracert any
computer on the 192.168.1.0 network the tracert runs through the tunner.

BUT when I try a tracert to a computer on the 192.168.6.0 network the
tracert runs goes out to thee internet instead of the tunnel. Why?

Thanks

 

[Herb Martin]

When I connect to the VPN server from my home pc and tracert any

computer on the 192.168.1.0 network the tracert runs through the tunner.

BUT when I try a tracert to a computer on the 192.168.6.0 network the
tracert runs goes out to thee internet instead of the tunnel. Why?

Lack of static routes. On the VPN source, add this net as a static route.
And on the 192.168.1.0 add it too. Add it to any intermediate routers that
don't connect directly to any of these nets -- this means 192.168.6.0 may
need a route back to 192.168.1.x TOO!!!

Do you understand the Static Route concept?

Any router knows ONLY about what it's own NICs are connected to...
Any router can have a Default Gateway (router) for ALL other traffic...
BUT...
If you need to reach specific nets by using another (than the default)
router
you must add static routes to/from those locations.

(Technically you could use Dynamic routing instead of static but that is a
whole 'nuther can o' worms.)