Why is this happening with my Cisco VPN?

Question

Level 1

12 points

Why is this happening with my Cisco VPN?

I'm having a weird problem. I use Cisco VPN to connect to my work server from home, with an RSA SecurID.

I can connect using my MacBook Pro without an issue--which connects wirelessly to my AEBS network. The laptop is assigned an IP via DHCP (if it matters).

I cannot connect with my Mac Pro at all--which is connected to the AEBS with an Ethernet cable. The Mac Pro has a fixed IP assigned through the AEBS, outside of the DHCP range. Once in a blue moon, the VPN will connect.

This is a log of the connection attempt:

Cisco Systems VPN Client Version 4.9.01 (0080)
Copyright (C) 1998-2006 Cisco Systems, Inc. All Rights Reserved.
Client Type(s): Mac OS X
Running on: Darwin 9.5.0 Darwin Kernel Version 9.5.0: Wed Sep 3 11:29:43 PDT 2008; root:xnu-1228.7.58~1/RELEASE_I386 i386

30 11:51:18.993 11/14/2008 Sev=Info/4 CM/0x43100002
Begin connection process

31 11:51:18.993 11/14/2008 Sev=Warning/2 CVPND/0x83400011
Error -28 sending packet. Dst Addr: 0xC0A801FF, Src Addr: 0xC0A80164 (DRVIFACE:1158).

32 11:51:18.993 11/14/2008 Sev=Warning/2 CVPND/0x83400011
Error -28 sending packet. Dst Addr: 0xC0A8A2FF, Src Addr: 0xC0A8A201 (DRVIFACE:1158).

33 11:51:18.993 11/14/2008 Sev=Warning/2 CVPND/0x83400011
Error -28 sending packet. Dst Addr: 0xC0A80DFF, Src Addr: 0xC0A80D01 (DRVIFACE:1158).

34 11:51:18.994 11/14/2008 Sev=Info/4 CM/0x43100004
Establish secure connection using Ethernet

35 11:51:18.994 11/14/2008 Sev=Info/4 CM/0x43100024
Attempt connection with server "pvc.partners.org"

36 11:51:18.994 11/14/2008 Sev=Warning/2 CVPND/0x83400011
Error -16 sending packet. Dst Addr: 0xAADFA8BE, Src Addr: 0x00000000 (DRVIFACE:2384).

37 11:51:18.994 11/14/2008 Sev=Info/4 CM/0x4310002E
Unable to reset TCP connection

38 11:51:18.994 11/14/2008 Sev=Info/4 CVPND/0x43400019
Privilege Separation: binding to port: (500).

39 11:51:18.994 11/14/2008 Sev=Info/4 CVPND/0x43400019
Privilege Separation: binding to port: (4500).

40 11:51:18.994 11/14/2008 Sev=Info/6 IKE/0x4300003B
Attempting to establish a connection with 170.223.168.190.

41 11:51:18.994 11/14/2008 Sev=Warning/2 CVPND/0x83400011
Error -16 sending packet. Dst Addr: 0xAADFA8BE, Src Addr: 0x00000000 (DRVIFACE:1281).

42 11:51:19.094 11/14/2008 Sev=Warning/2 CVPND/0x83400011
Error -16 sending packet. Dst Addr: 0xAADFA8BE, Src Addr: 0x00000000 (DRVIFACE:1281).

43 11:51:19.195 11/14/2008 Sev=Warning/2 CVPND/0x83400011
Error -16 sending packet. Dst Addr: 0xAADFA8BE, Src Addr: 0x00000000 (DRVIFACE:1281).

44 11:51:19.295 11/14/2008 Sev=Warning/2 CVPND/0x83400011
Error -16 sending packet. Dst Addr: 0xAADFA8BE, Src Addr: 0x00000000 (DRVIFACE:1281).

45 11:51:19.395 11/14/2008 Sev=Warning/2 CVPND/0x83400011
Error -16 sending packet. Dst Addr: 0xAADFA8BE, Src Addr: 0x00000000 (DRVIFACE:1281).

46 11:51:19.495 11/14/2008 Sev=Warning/2 CVPND/0x83400011
Error -16 sending packet. Dst Addr: 0xAADFA8BE, Src Addr: 0x00000000 (DRVIFACE:1281).

47 11:51:19.495 11/14/2008 Sev=Info/4 IKE/0x43000075
Unable to acquire local IP address after 5 attempts (over 5 seconds), probably due to network socket failure.

48 11:51:19.495 11/14/2008 Sev=Warning/2 IKE/0xC300009A
Failed to set up connection data

49 11:51:19.495 11/14/2008 Sev=Info/4 CM/0x4310001C
Unable to contact server "pvc.partners.org"

50 11:51:19.495 11/14/2008 Sev=Info/5 CM/0x43100025
Initializing CVPNDrv

51 11:51:19.495 11/14/2008 Sev=Info/4 CVPND/0x4340001F
Privilege Separation: restoring MTU on primary interface.

52 11:51:19.495 11/14/2008 Sev=Info/4 IKE/0x43000001
IKE received signal to terminate VPN connection

53 11:51:19.496 11/14/2008 Sev=Info/4 IPSEC/0x43700008
IPSec driver successfully started

54 11:51:19.496 11/14/2008 Sev=Info/4 IPSEC/0x43700014
Deleted all keys

55 11:51:19.496 11/14/2008 Sev=Info/4 IPSEC/0x43700014
Deleted all keys

56 11:51:19.496 11/14/2008 Sev=Info/4 IPSEC/0x43700014
Deleted all keys

57 11:51:19.496 11/14/2008 Sev=Info/4 IPSEC/0x43700014
Deleted all keys

58 11:51:19.496 11/14/2008 Sev=Info/4 IPSEC/0x4370000A
IPSec driver successfully stopped

Does anyone have any idea what is going on, or how i can fix this? I have tried, after reading this board, selecting the "Enable default host at" box on the AEBS and assigning it to the Mac Pro (it is usually assigned to the IP address given my Vonage box).

Thanks,
Frank

Mac Pro, MacBook Pro, Mac OS X (10.5)

Posted on Nov 14, 2008 8:53 AM

Reply

Answer 1

orangekay

Level 5

4,085 points

Nov 14, 2008 8:58 AM in response to fcarrano

fcarrano wrote:
(it is usually assigned to the IP address given my Vonage box).

What does that mean?

Reply

Answer 2

fcarrano Author

Level 1

12 points

Nov 15, 2008 2:27 PM in response to orangekay

it means that my Vonage was built into my old router. I have the AEBS and my old router connected to each other, with the old router's DHCP turned off...so it's functioning simply as the Vonage box and a switch. I had, way back when, had problems with the vonage quality getting spotty, and had read that this would help. so I put the Vonage's IP address into the "Enable default host at" box. In retrospect, now that I know that "Enable default host" is just a synonym for a DMZ, Im not sure that makes sense.

Nonetheless, I turned the "enable default host at" off, and the problem persists. When I assign the Mac Pro IP to the "enable default host at", the problem persists.

Thanks for any help,
Frank

Reply

Answer 3

Nov 15, 2008 2:37 PM in response to fcarrano

First, in the Cisco VPN client on your MacPro, make sure the NAT-T setting is enabled. Try to connect. What happens?

Try setting up the Mac Pro for DHCP and if it has an airport card, also try with wireless. What happens?

What about with your current static ethernet setup: what happens if you ping the IP of the VPN server.

Reply

Answer 4

fcarrano Author

Level 1

12 points

Nov 18, 2008 9:34 PM in response to Community User

Okay, so here's what happened. I deleted the static IP assignment for the Mac Pro in the AEBS settings. I also changed the Mac Pro's network settings from manual to DHCP. When I restarted, it continued to assign the IP address I had manually chosen (192.168.1.100, with a DHCP range set from .120 to .140).

And now it seems to connect to my VPN just fine. Can anyone explain to me why this would happen?

In addition, I had opened some ports assigned to VPN access, routing them to my 192.168.1.100 Mac Pro. I deleted this assignation as well....just in case this might have had something to do with it (although I had turned this port forwarding off prior to turning off manual IP assignment, and it wouldn't connect).

Frank

Reply

Answer 5

Nov 19, 2008 1:01 PM in response to fcarrano

It was the ports being opened that fixed the issue.

Reply

Answer 6

fcarrano Author

Level 1

12 points

Nov 19, 2008 10:11 PM in response to Community User

It actually wasn't working when I had the ports being forwarded (I was forwarding UDP 62515,4500,500, and TCP 10000 to my Mac Pro's IP address). When I unchecked those ports, it worked again.

I'm baffled.

Reply