virtualbox.org

Well from what I have read Win7 is doing something and even MS says that it should not be used in production environments yet, but it should still work. I suspect as you that the XP feature may be causing it. The only way to test this is to disable or uninstall the xp feature and see if it clears things up. Anyway I will keep my ears open and let you know what I find out. I do know that if you are using 64 bit with a hyper-visor enabled OS you don't want to use two VT aware OSs together. It can not only corrupt the drive of one but can make both the host and the guest unusable forcing a totally reinstall of everything.

Issue is solved.
It was in front of my eyes all the time. Well, that's how it usually happens.

The bad boy was not Windows 7 or Virtual PC but Shrew VPN clinet.
I've ended up removing its driver from the Networking properties, and it worked like a charm right away.

Reinstalled the client, and it still works. Have not rebooted the PC yet, though. But even if it breaks again, I know where to look now.

For the laughs, the same is described here:


http://www.virtualbox.de/ticket/3752

I wish I saw it early

Update:
rebooted the host PC after reinstalling the VPN client, and no problem so far. VM and Shrew VPN - both work.

TDog wrote:Issue is solved.
It was in front of my eyes all the time. Well, that's how it usually happens.

The bad boy was not Windows 7 or Virtual PC but Shrew VPN clinet.
I've ended up removing its driver from the Networking properties, and it worked like a charm right away.

Well done, that did it for me to. Unchecked Shrewsoft Lightweight Filter from my NIC and everything works fine Have been pulling my hair about this one as it works on the WiFi NIC.