Currently I use VirtualBox for a while with a Win2000 guest, which has some business software and a VPN connection to work. It functions but has several major problems that I have given up on fixing and now merely tolerate/workaround.
The most serious problem is that the Win7 host gets confused (as far as I can tell) about which packets to route where. Often the Win7 host's network connections slow down horribly even though ping to my ISP's home page remains fine. When this happens, I see the vbox guest network icon going nuts while the guest is not actually using it. Or vice versa. Rarely the host's traffic (intended for the home ISP) is actually being routed through the guest's VPN (and uses work's ISP), which ticks off everyone including me and my boss.
However, between the VPN filtering stuff, vbox's nat/bridging implementations modifying packets, and Windows networking (in which I have little confidence), I'm not sure where the fault is. So I thought I'd start from scratch with VMWare Player, a Win7 guest, and a second NIC dedicated to the guest.
- NIC A -> (physical) home network, TCP/IP for the host
- NIC B -> (physical) home network, VPN (via udp?) for the guest
Is this advisable?
If so, can you give me some terms that I can use to search for more information?
My skill level is moderate, given that I'm a home user and not a network admin. I set up my home router and have a basic working knowledge of IP ranges, subnets, conflicts, protocols, ports, firewall rules, etc. - just enough knowledge to be dangerous. -_-'