Opened 15 years ago
Closed 13 years ago
#7235 closed defect (duplicate)
Crash when using Shrewsoft VPN client with SATA controller
Reported by: | David | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 3.2.6 |
Keywords: | shrewsoft sata vpn | Cc: | |
Guest type: | other | Host type: | other |
Description (last modified by )
guest: Windows XP 64 host: Ubuntu Server 64 9.10
Succesfully using Shrewsoft VPN client from within the guest until I switched from IDE to SATA controller on the guest. When attempting to connect to the VPN with the Shrewsoft client the guest appears to freeze along with display corruption, although I have also experienced BSOD.
Shrewsoft version: 2.1.5
Attachments (2)
Change History (5)
by , 15 years ago
comment:1 by , 14 years ago
comment:2 by , 14 years ago
I'm also having the same problem with Cisco AnyConnect VPN client.
HOST: Windows 7 64
Guest: Windows XP SP3 32
When using SATA Controller, the Guest Crashes and shows graphical distortion, also BSOD occurs if the window is minimized. Changing from SATA to IDE allows the VPN connection to occur correctly.
I will recreate and attach vbox.log file as well.
comment:3 by , 13 years ago
Description: | modified (diff) |
---|---|
Resolution: | → duplicate |
Status: | new → closed |
I think this problem is related to enabled Page fusion. Let's continue discussion in #7278.
I'm also having the same problem with the Cisco AnyConnect VPN client.
Host: Gentoo 64
Guest: Windows XP SP3 32
Using IDE/PATA for the drive connection it works fine, but if I move the system drive to a SATA connection then I get a freeze-up or crash as soon as VPN connects and tries to bring up the VPN interface. If I leave the system drive on IDE and connect another drive to SATA the guest keeps working fine, but whatever drives are on the SATA connection disappear. I then tried refreshing the drives from within Intel's Rapid Storage management console but it could not re-detect the drives.
This used to work fine with Cisco's older VPN Client version 5.0.04.0300. But AnyConnect seems totally different, using another VPN virtual network interface even.