Cisco VPN client on guest system failed to connect after upgrade to 2.1.0 ver.

[Vladimir Sidorenko]

Host: win2003 Guest: XP Network: NAT

CiscoVPN client(ver. 4.8.00.0440) installed on guest system.

After upgrade VBOX from ver. 2.0.6 to 2.1.0 client can't connect to server. Downgrading to 2.0.6 solved this problem.

[ingenium]

Same problem, but it only appeared after upgrading from 2.1.0 to 2.1.2. It worked fine for me in 2.1.0. I have Ubuntu 8.10 as the host and Windows XP SP3 as the guest. Cisco VPN client 5.0.00.0340. I get an error that the remote peer is no longer responding with both UDP and TCP.

[Sander van Leeuwen]

Retry with 2.1.4 and reopen if necessary please.

[ingenium]

still broke in 2.1.4 with both TCP and UDP connections

[vasily Levchenko]

Could you please attach log files here?

[ingenium]

Virtualbox 2.1.4 log

[ingenium]

Cisco VPN log

[ingenium]

Attached. Are there any other log files I should attach?

[vasily Levchenko]

Thank you for input. You've provided enough information.

[ingenium]

The issue is still present in 2.2.0

[djarosz]

NAT: Unsupported protocol 888e

Still not working in 2.2.2. I have attached my log from virtual box and from cisco client may be this helps.

[vasily Levchenko]

Replying to djarosz:

NAT: Unsupported protocol 888e

Still not working in 2.2.2. I have attached my log from virtual box and from cisco client may be this helps.

your VPN implementation require EAP which (according RFC3748 3.1.4) could be transported via IP as well, but NAT able to deal with protocols based on TCP/IP and UDP/IP, because of OS limitations. I'd recommend try it with bridged networking.

[djarosz]

Replying to Hachiman:

Replying to djarosz:

NAT: Unsupported protocol 888e

Still not working in 2.2.2. I have attached my log from virtual box and from cisco client may be this helps.

your VPN implementation require EAP which (according RFC3748 3.1.4) could be transported via IP as well, but NAT able to deal with protocols based on TCP/IP and UDP/IP, because of OS limitations. I'd recommend try it with bridged networking.

It works for bridged networking but this is not a sollution for me sicne a connect using WiFi interfaces and than bridged networking does not work at all.

VPN Client used to work perfectly with NAT prior to 2.1.0

[vasily Levchenko]

Replying to djarosz:

Replying to Hachiman:

Replying to djarosz:

NAT: Unsupported protocol 888e

Still not working in 2.2.2. I have attached my log from virtual box and from cisco client may be this helps.

your VPN implementation require EAP which (according RFC3748 3.1.4) could be transported via IP as well, but NAT able to deal with protocols based on TCP/IP and UDP/IP, because of OS limitations. I'd recommend try it with bridged networking.

It works for bridged networking but this is not a sollution for me sicne a connect using WiFi interfaces and than bridged networking does not work at all.

VPN Client used to work perfectly with NAT prior to 2.1.0

Hm .. sounds not good . Could you please attach to the ticket or send me in private mail to me [vasily [dot] levchenko [at] Sun [dot] COM] result of:

#VBoxManage modifyvm [your-vm-name] -nictrace1 on -nicktracefile1 c:/vpn.pcap
#VirtualBox startvm [your-vm-name] 
try to establish VPN connection, till vpn client aborts.
<Host-Q>

[ingenium]

The issue has disappeared as of 3.0.8. I'm able to connect to the VPN using NAT.

[djarosz]

The same for me. With VirtualBox 3.0.8 I can connect though Cisco VPN client using NAT

[Frank Mehnert]

Thanks for the feedback. Closing.