After I posted this, I refined my search of postings and came upon one that
was similar. Even though the originator was not using a Cisco VPN Client as
I am, the reply from Shenan Stanley was right on the mark:
==
Cisco VPN client?
Under the transport tab for your particular connection, choose to use UDP
instead of TCP 443.

--
- Shenan -
--
The information is provided "as is", it is suggested you research for
yourself before you take any advice - you are the one ultimately
responsible for your actions/problems/solutions. Know what you are
getting into before you jump in with both feet.
==

Thank you Shenan where ever you are! It worked. I will have my corporate
IT folks update their client install instructions to include this pearl of
wisdom. :-)


"BobD" wrote:

I have XP SP2 installed and the Firewall enabled. The Knowledge Base
describes a problem whose symptoms match mine exactly, except I'm not running
a pre-release version of SP2. I've tried adding Cisco VPN Client to the
Exceptions list, and even disabled the firewall for the VPN network
connection. Nothing works - I still can not connect. The only message
displayed is from the client, not from the Firewall, so at first I was
unaware the Firewall had anything to do with the connection problem. I
eventually found that if I turn off the XP Firewall, I can connect with no
trouble.

I don't understand why the Windows Firewall does not distinguish between
apps attempting to connect to the Internet from inside the system like other
firewalls do. The VPN Client is trying to connect to the remote end, and if
I have it added to exceptions and/or disable Firewall from the VPN network
connection, it should not be blocking a return connection from the remote end.

To make matters more confusing, if I drop the firewall, connect, then raise
the firewall again, I don't seem to lose the connection. I need to
experiment with this to see if it is a viable workaround.

Any assistance or suggestions will be greatly appreciated.

advTHANKSance!