VIEW SOLUTION IN MY NEWER POST
*********************************************
Hi everybody...
I installed VirtualBox in Ubuntu (Gutsy i386) using the official repos (v1.5.0, OSE version) and then installed Windows XP Pro SP2 as guest OS.
After finishing installation, i can't get any network activity in guest machine (web, ftp, dns resolution), even when I have enabled a virtual network adapter using NAT and it's recognized in Win right (assigns an IP in the 10.0.2.x range).
I have tried using the repos from virtualbox.org (version 1.5.2, non-OSE) but the problem persists, and also probed a linux liveCD guest and the problem persists...
I can't use bridged networks because it's a corporate, and is filtered by MAC.
Have two network adapters in the host, wired and wireless (this is using ndiswrapper), but the problem happens when connected in both ways. I have removed the ndiswrapper driver and tried with only the eth0 if, but still nothing.
Anyone has some idea about it?
Thanks.
gfa
*********************************************
VIEW SOLUTION IN MY NEWER POST
SOLVED!! No network in Virtualbox guests (win & linux)
SOLVED!! No network in Virtualbox guests (win & linux)
Last edited by gfalinux on 13. Mar 2008, 09:03, edited 1 time in total.
We have got exactly the same problem here in my school. Some people - about 10 - are using virtualbox on Windows hosts (XP, Vista) with Linux guests and networking using NAT stopped working all of a sudden.
There is no way to reactivate it, though sometimes playing around with adapters (NAT, Host Interface, deactivating it, selecting NAT again, and so on) seemed to revive it.
Never had those problems until today. I am using Linux as host and now my XP guest doesn't see to be able to get any connections to LAN, not speaking of Internet at all.
This seems to be an error that has been reported a few times and, sad but true, has not been attracting interest at all.
There is no way to reactivate it, though sometimes playing around with adapters (NAT, Host Interface, deactivating it, selecting NAT again, and so on) seemed to revive it.
Never had those problems until today. I am using Linux as host and now my XP guest doesn't see to be able to get any connections to LAN, not speaking of Internet at all.
This seems to be an error that has been reported a few times and, sad but true, has not been attracting interest at all.
NAT,Network bridging
I have exactly the same problems.Whatever I do,it just doesn't go.I use XP Corporate SP2 as guest.Considering that VMware ,Win4LinPro and Parallels all have Network bridging automatically installed,the developers can't be serious in thinking,command line stuff will do forever.Isn't it about time they get their fingers out and add it to the installation as other Companies do?
Whichever of the 3 afore mentioned I install,everything is well.There is only one letdown with VirtualBox,NAT,Network bridging,it is crap.
Firewalls can and must not be an excuse,as the products from the competition can be run with a firewall in the host and in the guest without any detrimental effects.If this cannot be done likewise in VirtualBox,you must warn your users,that VirtualBox cannot be used with a firewall running in the host.Even without a Firewall your examples in the manual still don't do the trick to get Nat or bridging going with XP Corporate SP2
Whichever of the 3 afore mentioned I install,everything is well.There is only one letdown with VirtualBox,NAT,Network bridging,it is crap.
Firewalls can and must not be an excuse,as the products from the competition can be run with a firewall in the host and in the guest without any detrimental effects.If this cannot be done likewise in VirtualBox,you must warn your users,that VirtualBox cannot be used with a firewall running in the host.Even without a Firewall your examples in the manual still don't do the trick to get Nat or bridging going with XP Corporate SP2
IF IT'S FREE IT'S ME
Re: NAT,Network bridging
A good default rule of a firewall is to block anything it doesn't know. And if the competition has a good default firewall setup (I suppose it) they all will have the same problems if you don't tell the firewall what's going on with your networking.tiberian wrote:Firewalls can and must not be an excuse,as the products from the competition can be run with a firewall in the host and in the guest without any detrimental effects.
Or you do it like Microsoft: automatically open the firewall as needed.
SOLVED!!!
In my case, the solution was "easy"...
I realized that browsing throw static IP addresses in guest was OK.
My problem, I think it is caused because I use a local DNS cache with dnsmasq, so:
- Inside the guest operating system, I setup the network connection manually for the DNS servers.
Thanks to everyone for your help...
I realized that browsing throw static IP addresses in guest was OK.
My problem, I think it is caused because I use a local DNS cache with dnsmasq, so:
- Inside the guest operating system, I setup the network connection manually for the DNS servers.
Thanks to everyone for your help...
-
Quasaur
- Posts: 10
- Joined: 1. Oct 2007, 16:49
- Primary OS: MS Windows 7
- VBox Version: OSE other
- Guest OSses: XP
- Location: Charlotte, NC
- Contact:
Re: SOLVED!! No network in Virtualbox guests (win & linu
what did you set the guest's DNS servers to?
Re: SOLVED!! No network in Virtualbox guests (win & linu
To my ISP provided DNS:Quasaur wrote:what did you set the guest's DNS servers to?
200.23.242.193
200.23.242.201
But after upgrading to Hardy and VB 1.6.2 I haven't to set any additional DNS information. Only have to occasionally clic Repair connection in the XP network connection.