Cisco VPN

[pinti59]

I cannot seem to connect to my corporate network via the Cisco VPN. is there something I need to do?

[SomeJoe7777 ACE - Geek]

The U-Verse router (the 2Wire residential gateway, or RG) supports Cisco VPN only in transport mode, not in tunnel mode.  You will need to speak to your IT department about how to operate with the Cisco VPN client in transport mode.

[pinti59]

The Client is set to enable transport tunneling and to use IPSEC over TCP on port 10000, but I still can't get in. I know the VPN works because I can get in using other computers using a different ISP.

[SomeJoe7777 ACE - Geek]

If it is tunneling through TCP it should work correctly.

If you still can't get it to work after checking all settings and verifying them with your IT department, you can also try assigning your computer as the DMZPlus device.  Do this in the 2Wire's configuration pages under Settings -> Firewall -> Applications, Pinholes, and DMZ.

[pinti59]

how can I access the 2wire configuration page?

[SomeJoe7777 ACE - Geek]

Usually at http://192.168.1.254

To change the configuration, the 2Wire will ask for a password.  The default password is on a white sticker on the side/bottom of the 2Wire router.

[ScottMac]

---

pinti59 wrote:

I cannot seem to connect to my corporate network via the Cisco VPN. is there something I need to do?

---

What version are you using? I am (at this moment, on this post) using Cisco VPN client 5.0.03.0530 in UDP through an unmodified, no-extra-holes-in-the-fireall, old-style 3800 RG. I am connected wirelessly laptop to AP to RG using 802.11n and a reported speed of 130Mbps.

It is an exclusive VPN, no split tunneling is permitted on our system.

It's connecting to a Cisco VPN concentrator at the company end.

I have never had any issues (nearly two years) via VPN, UDP or TCP.

You may want to verify that your company's firewall is permitting you in, since you are now originating from a new address (U-verse versus whatever you had before).

Good Luck

[pinti59]

I am actually the IT Manager and I am trying to troubleshoot this with a someone who live in Florida. I know the firewall is allowing in all vpn clients. I have tried this from multiple locations with different computers. It extremely frustrating because I know that all is working on my end. 

[ScottMac]

---

pinti59 wrote:

I am actually the IT Manager and I am trying to troubleshoot this with a someone who live in Florida. I know the firewall is allowing in all vpn clients. I have tried this from multiple locations with different computers. It extremely frustrating because I know that all is working on my end. 

---

The other "usual" issue is MTU or MSS ... if the user has cascaded devices, tunnels, etc then the actual content size may need to be reduced, ala DSL and using 1492 byte MTU to accommodate the added header info / packet / frame expansion (remembering that encrypted stuff generally does not frag).

AT&T is not blocking anything, and the RG works fine for client VPN apps, at least Cisco's (and a co-worker is using Sonicwall-to-Sonicwall VPN into our facility, all day, every day for over a year now through a U-verse RG ...Sonicwall is behind the RG, RG in DMZ+ mode).

Do you have access to the logs? Both sides?

[RJSinMO]

I connect to several different sites with Cisco VPN's, both the Cisco classic client and also the Cisco AnyConnect http version, with no problems.  These are VPN's operated by my various clients, so their configurations vary, but again, no problems.  I would really doubt the problem is with UVerse. 

[2geeks]

I had a difficult time getting my Cisco VPN to work. I followed all the recommendations and still had problems.

It turns out that Windows 7 had classified my ATT uverse wireless connection as an insecure "Internet network" so the Windows 7 firewall was blocking my VPN connection.

Once I opened the Network and Sharing Center in WIndows 7 and changed my network type to "Home network" my VPN worked.

[Taylarie]

I would like to thank everyone for taking the time to post your comments and opinions related to this topic. This topic has been thoroughly discussed and will now be closed.