Page 1 of 1

[SOLVED] Wired Network does not connect on Ubuntu 10.10

Posted: 19. Apr 2011, 10:57
by Suleyman
Hi,

I have installed VB 4.0.4 on a XP host and using Ubuntu 10.10 as guest. When I use the network as NAT everything works well however I have to be in the same network as the host OS. Therefore I tried Bridged Network with all combinations of adapter types but each time the guest OS (which is Ubuntu 10.10) says "Wired Network -Disconnected" and it never connects. In the network settings of VirtualBox, I used the mac address of host OS then wired network got connected in guest OS however it cannot use the internet connection because the connection to the server gets reset and in the mean time I cannot use internet on the host OS either. If I disconnect the wired network in the guest OS then the internet on the host OS works well. I have checked many forums and web sites however I could not find the solution. Anybody has any idea?

As a summary, when bridged network is used, the guest OS does not connect to the wired network. All adapter types were tried. (NAT works well.)

Btw I have guest additions 4.0.4.

Thanks in advance,

/Süleyman

Re: W?red Network does not connect on Ubuntu 10.10

Posted: 19. Apr 2011, 11:22
by vbox4me2
Suleyman wrote:I used the mac address of host OS then wired network got connected in guest OS
MAC addresses can only be used by one OS, if a linux Guest gets a new MAC addresses you need to reset the lan interface inside the Guest.

Re: W?red Network does not connect on Ubuntu 10.10

Posted: 19. Apr 2011, 11:25
by Suleyman
vbox4me2 wrote:
Suleyman wrote:I used the mac address of host OS then wired network got connected in guest OS
MAC addresses can only be used by one OS, if a linux Guest gets a new MAC addresses you need to reset the lan interface inside the Guest.
Yes I realized that the same mac address can be used by only one OS. However still it is no solution.

Re: Wired Network does not connect on Ubuntu 10.10

Posted: 19. Apr 2011, 11:41
by Suleyman
Yes! Finally I fixed it by configuring the network settings manually, such as ip address, dns address, subnet mask and so on... So I guess the problem was between the guest OS and DHCP server, the guest OS was not able to get ip address automatically.