CISCO VPN Client Not Connecting

[Tom]

Hi, XP Pro, cable modem, internet access, a CISCO VPN client will not
connect. What might be causing this problem? I remember in previous
version of cisco client I had to enter a port number into the windows
firewall.


Thanks in advance

 

[chuckcar]

Hi, XP Pro, cable modem, internet access, a CISCO VPN client will not
connect. What might be causing this problem? I remember in previous
version of cisco client I had to enter a port number into the windows
firewall.

Disable the windows firewall entirely and see if it works. No point in
fiddling with a program if you don't know if it's the problem.

 

[wisdomkiller & pain]

Disable the windows firewall entirely and see if it works. No point in
fiddling with a program if you don't know if it's the problem.

Cable modem and no firewall. Guess how long will it take to become a zombie?

 

[Desk Rabbit]

Disable the windows firewall entirely and see if it works. No point in
fiddling with a program if you don't know if it's the problem.

Dangerous advice at best.

 

[Desk Rabbit]

Hi, XP Pro, cable modem, internet access, a CISCO VPN client will not
connect. What might be causing this problem? I remember in previous
version of cisco client I had to enter a port number into the windows
firewall.

Contact support at the host end of the VPN tunnel and ask for advice.

 

[§ñühwØ£f]

Hi, XP Pro, cable modem, internet access, a CISCO VPN client will not
connect. What might be causing this problem? I remember in previous
version of cisco client I had to enter a port number into the windows
firewall.


Thanks in advance

Cant you set it up in yer cable modem?
192.168.1.1 and look for somthing like "port forwarding"...might be a drop
down menu with a big lits of things you can allow...prolly named Cisco VPN?

 

[chuckcar]

Cable modem and no firewall. Guess how long will it take to become a
zombie?

Just to check obviously. Then reenable it back to normal. Or better yet
get a *real* firewall program.

 

[Pennywise]

Disable the windows firewall entirely and see if it works. No point in
fiddling with a program if you don't know if it's the problem.

You would finally screw this person, it might take a full minute, but
you would get what you've been working at all this time.

 

[Tom]

Contact support at the host end of the VPN tunnel and ask for advice.

Did that but they were no help.

 

[§ñühwØ£f]

Did that but they were no help.

Lemme get this straight...you contacted CISCO and they *couldnt* help you?

 

[Desk Rabbit]

Lemme get this straight...you contacted CISCO and they *couldnt* help you?

It is reasonable to assume that the end point he is connecting to who
provided the connections details and/or the client software would
provide support for their connection.

 

[§ñühwØ£f]

It is reasonable to assume that the end point he is connecting to who
provided the connections details and/or the client software would
provide support for their connection.

I guess Tom fixed his problem since he never poasted again
I would check the cisco site since they know more about networking than
most. But thats just me.

http://www.commondreams.org/view/2008/11/16-6
No bailout for GM!

 

[grwilli]

Did you get this working?

I was going to ask what was new about your setup. Didn't read through the
whole chain - but did it ever work and now it's broke? Fill me in.

Another thing - I moved to Comcast recently and mine broke as a result.
There are a couple ways to configure a Cisco VPN Client and head-end (router,
vpn concentrator, pix, asa) to compensate for folks like Comcast.

In a nutshell, using the TCP/10000 (default port) is the answer, but this
ONLY works if your head-end support folks allow and configure it. To your
cable modem (and say Comcast) this VPN traffic now appears as a straight-up
TCP flow (like www, ftp) - no IPSec stuff, no IKE/ISAKMP stuff, no ESP
protocol translation and no negotiation. In other words, unless someone is
specifically blocking that TCP port (10000), then it works.

Oh, and is applies here, as far as I know, this is a Cisco only feature -
Cisco VPN client to Cisco head-end. All head-ends (with current code) that
support a 4.0+ Cisco VPN client support this feature. As a help to pitch
this to the head-end folks - that with this, only one port is needed through
a filter/policy (ACL) to support the VPN clients - simple.

Hell for that matter - try it out. Modify the connection entry, Transport
tab, Checkbox for Enable Transparent Tunneling, and the radio-button for
IPSec over TCP - guess leave the port value at 10000. If it doesn't work -
then you know where to go from there.

Hope that helps.