Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have three locations: A is a host with T1 internet connection, B and C are point-to-point with A. Each location also has their on default gateway.

A, B, C all have different subnets:

A: 10.30.7.x
B: 10.30.9.x
C: 192.168.2.x

There is an Ipsec VPN connected to 192.168.26.x by a Symantec Gateway Security 320 (subnet A). But I am unable to ping an address on the other side of the vpn from any computer on subnets B and C.

I need to know how to have one computer (WinXP) from B and one from C be able to utilize the VPN connection made on A.

Is is possible to split-tunnel my Symantec, or create routes through command prompt on the machines needing the VPN connection?

share|improve this question

The routers at sites B and C need to learn how to reach 192.168.26.x either by putting in a static route or having router A advertise it using a routing protocol.

share|improve this answer

Forgot my login info when I asked this question!!

Added each subnet to routing of Symantec, didn't fix the issue.

The routers at B and C are owned/managed by ISP, so I have called them asking to add static route, and they are "looking into the issue".

Other than not being able to ping this VPN from subnets B and C, having no connectivity/passing traffic issues. Thanks for your help, Tom

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.