VPN over NAT - Vbox 2.0.2 -Vista x64 host, Windows XP guest
Posted: 13. Oct 2008, 21:38
I am using VirtualBox 2.0.2 with Vista x64 as the host and Windows XP x86 as the guest.
I want to be able to connecting using Windows VPN from the guest into my office. Using NAT networking the VPN connection never completes. I tried creating a network interface and using bridging. While this works in that the VPN connects, it causes my network on the host to become unstable with the connection dropping every ten minutes or so.
Is there a way to configure my network settings and/or firewall to allow Windows VPN to function correctly in the guest while using NAT networking? I believe Windows VPN uses PPTP which is TCP port 1723. It also uses the GRE protocol (47).
I have a similar WinXP guest running in Virtual PC 2007. It works seamlessly without having to manually setup bridging or having to modify my firewall configuration. Also, whatever VPC is doing does not cause any instability in my network connection. How is the approach that Virtual PC uses different than what VirtualBox does?
I much prefer VirtualBox over Virtual PC for the features and the ability to use the same virtualization software under both of my development environments (Vista and Solaris), but the bridging requirement is turning out to be a showstopper.
I want to be able to connecting using Windows VPN from the guest into my office. Using NAT networking the VPN connection never completes. I tried creating a network interface and using bridging. While this works in that the VPN connects, it causes my network on the host to become unstable with the connection dropping every ten minutes or so.
Is there a way to configure my network settings and/or firewall to allow Windows VPN to function correctly in the guest while using NAT networking? I believe Windows VPN uses PPTP which is TCP port 1723. It also uses the GRE protocol (47).
I have a similar WinXP guest running in Virtual PC 2007. It works seamlessly without having to manually setup bridging or having to modify my firewall configuration. Also, whatever VPC is doing does not cause any instability in my network connection. How is the approach that Virtual PC uses different than what VirtualBox does?
I much prefer VirtualBox over Virtual PC for the features and the ability to use the same virtualization software under both of my development environments (Vista and Solaris), but the bridging requirement is turning out to be a showstopper.