From: Scott Vermillion (scott_ccie_list.com@it-ag.com)
Date: Wed Sep 19 2007 - 23:07:21 ART
Hi Mohammed,
Could possibly be a NAT-T issue. NAT-T uses UDP port 4500 bi-directionally.
Any chance that port is blocked by your corporate firewall? Haven't dealt
w/ the Cisco VPN client in over a year, so I don't remember all the details,
but I do remember NAT-T issues needing to be addressed...
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Mohammad Saeed
Sent: Wednesday, September 19, 2007 7:40 PM
To: Cisco certification
Subject: Interesting VPN Access Issue
Hello Every body,
I have Ciisoc VPN Cleint insttaled on my laptop windowsXP. Now if I
use this VPN Client from myhome Internet connection to establish VPN
Tunnel to the destination which is a PIX firewall from home, it gets
connected, and I can reach ping/telnet any device on remote side
network.
But when I take my system to my office, hook my laptop to office
network, VPN Cleints gets authenticated and tunnel is established, VPN
Adapter gets the same IP that its gets when I establish tunnel from
home, but I can't ping/telnet to any deivces on the remotre network
that I used to ping/telnet when I am connecting from my home network.
If I say ping, it just times out, traceroute doesn't even show first
hop which shall be the other end of the tunnel and telnet times out.
What can be the reason????
If routing on remote end or firewall on the laptop would be issue,
then how VPN Tunnel is established on the first step?
I will appreciate if any one can hint....
Regards,
Mohammad Zahed Saeed
This archive was generated by hypermail 2.1.4 : Sat Oct 06 2007 - 12:01:14 ART