SonicWall VPN Client - trouble seeing WAN, sees VPN subnet

Archived from groups: comp.dcom.vpn (More info?)

Hi.

I'm out of ideas on how to fix this and the IT guys can't seem to
figure it out either:

* VPN Client 8.0.0 Build 10
* Windows 2000 Pro SP4
* Multi-tier VPN configuration

I use my VPN client to talk to our local affiliate's subnet
xxx.xxx.225.0. My policy is set up for xxx.xxx.0.0 to ensure that
I can see the whole WAN. This has worked fine for two years.
Recently, however, traffic destined for the VPN WAN upstream from
the 225.0 subnet doesn't get anywhere. Rebooting the SonicWall
fixes this for a while, but then routing seems to disappear again.

The VPN configuration is multi-tiered in that not only do we have
VPN clients connecting to the affiliate firewall, but VPN is used
between the affiliate firewall and the HQ firewall. It's this
part of the equation that doesn't seem to be working well for me.
Problem is that we have two other telecommuters and their
configurations are working just fine. Routing only dies for my
client.

Is this a known issue? If so, how can it be fixed? Be as
technical as you like; I'll forward any answers to the IT folks
so they can have a go at it.

Many thanks,

trane
--
//------------------------------------------------------------
// Trane Francks trane@gol.com Tokyo, Japan
// Practice random kindness and senseless acts of beauty.