🚀 go-pugleaf

I have to disagree with Fadi's post.

"Fadi" <fadi@harake.com> wrote in message
news:64307795.0111020717.6c8b7ed4@posting.google.com...
> Its NAT! are you using a "Firewall" does your wireless "gateway" takes
> one "real" IP address and the clients use a reserved address?

 I'm quite sure you can run a VPN session using the nortel extranet client
(connecting to a contivity box at the corporate end) through a session using
NAT. I connect to a corporate VPN all the time and used to connect through a
Linksys using NAT all the time and never had any trouble. I use the Nortel
client to get to a contivity box as well. If you asked me I'd guess there is
something going on your corporate VPN authentication - maybe you sessions
are expiring for some reason. I'm not a VPN expert, but isnt there some IP
encapsulation going on anyway with IPsec or L2tp that would make NAT pretty
much irrelevant?

>
> dzerzhin@yahoo.com (Alex) wrote in message
news:<ab6bb229.0110301543.25dd0ca0@posting.google.com>...
> > I'm using UofChicago's wireless LAN to get on the Internet, which
> > works great.  But once i try to go from their LAN to corporate VPN
> > (using Nortel Extranet client),

 Maybe UofC's network doesn't like something your PC is sending/receiving to
keep the session alive - I've had trouble with VPNs in the past where
networks wouldn't necessarily allow all the ports the VPN required. If those
ports are being dropped for some reason that would explain your sessions
timing out - the packedts on ports needed to keep the tunnel alive aren't
being received at the host or client, and the tunnel eventually dies. Any
VPN experts wanna tell me I'm full of it (I'd appreciate it, since I'm sort
of technical novice with VPN anyway).

Regards,
Rob