Opened 8 years ago
Closed 8 years ago
#15852 closed defect (duplicate)
VM crashes immediately in NAT mode when host Cisco AnyConnect VPN is connected
Reported by: | DKroot | Owned by: | |
---|---|---|---|
Component: | network/NAT | Version: | VirtualBox 5.1.4 |
Keywords: | Cc: | ||
Guest type: | other | Host type: | Mac OS X |
Description
I'm running Windows 10 guest in OS X El Capitan host. If I try to use host VPN connection via NAT in VM, VM crashed almost immediately when the host Cisco AnyConnect VPN is connected.
Test case:
- Launch VM and login
- Connect Cisco AnyConnect VPN on the host
- I can see network tray icon in Windows 10 showing disconnection for a couple of seconds
- VM crashes
This is a critical issue for me because I can't pass USB device and use guest VPN either in Bridged mode: a separate issue. So, I can't use VirtualBox whatsoever for work because of these two issues.
Attachments (1)
Change History (9)
by , 8 years ago
follow-up: 3 comment:2 by , 8 years ago
@frank To clarify, do you want me to get Windows dump from the guest?
comment:3 by , 8 years ago
Host type: | other → Mac OS X |
---|
Replying to DKroot:
@frank To clarify, do you want me to get Windows dump from the guest?
No, the core dump of the VirtualBox on the host.
I'll also try to provide a test build with additional logging around relevant parts in the next day or two.
comment:4 by , 8 years ago
What is the contents of /etc/resolv.conf
when you connect to the VPN and the VM crashes? Feel free to mask the actual addresses/names.
comment:6 by , 8 years ago
I was having the same issue with an OSX host & windows 10 guest. The solution provided in #15948 worked for me. When connecting to the VPN the /etc/resolv.conf contained more than 6 search entries. When I edited it down to 6 everything worked fine.
Any ideas which version of VirtualBox this fix may get rolled into? Until then you'll have to edit your resolv.conf each time you connect to the VPN.
comment:7 by , 8 years ago
It will be in the next dot-dot releases. Meanwhile you can use a recent test build.
Log immediately after crash