After SSL VPN connected, there are no routes to private LAN

[sj3vans]

My PAN SE just helped setup our SSL-VPN.  The first two users had no problems, but the next two did.  I observered both first hand.  Once the SSL VPN client is connected, I was not able to ping internal IP addresses.  I checked the routes on the PC ("route print") and there was no route to our internal network.  Doing an "ipconfig" showed no default-gateway for the VPN interface (0.0.0.0) unlike my PC which works and has the default-gateway matching the IP address I had received from the PAN's VPN pool.  I added a route to our LAN subnet on the PC and connectivity started working ("route add 10.170.249.0 mask 255.255.255.0 10.170.248.5").  I was then able to access all internal devices fine.  I realize I'm leaving out a lot of configuration details but wanted to check to see if anyone else had seen this in case there is an easy fix before opening a case or digging too much deeper.  Thanks!

[migration]

Hi,

I have not seen this problem. I just did a quick check with our support guys, and they suggest you contact them so that they may help you troubleshoot the problem.

Cheers,

-TK

[todd.felker@tmmc.com]

We are experiencing this too at random times.  Was there any fix or suggestions to this?