Page 1 of 1
Bridged network - unable connect host network
Posted: 2. Oct 2015, 13:48
by Lorenzo Soncini
Good morning,
I have installed Virtual Box 5.0.4 on Windows Server 2012 R2 Foundation.
I use a bridged network because I need to connect to the guest machine (Windows 10 Enterprise) using remote desktop.
The problem is:
From the guest machine I connect to all other computer on the network (ping other server, router,...) but I'm unable to contact the HOST machine (Windows Server 2012 R2 Foundation) where VirtualBox is installed.
There is a solution?
Thanks
Lorenzo soncini
Re: Bridged network - unable connect host network
Posted: 3. Oct 2015, 10:22
by ecate
I have a similar problem from version 5 onwards , before I was using version 4 of Windows 7 and everything worked well. Now I use Windows 10 pro as host and linux as a guest , but I also tried the version 5 of Windows 7 and should not be , if I use the NAT network I have no problems , but if I use the bridged takes a strange thing , I can ping the ' host router yourself for example goolge but if I try an ssh ftp etc. the guest fails to connect . I tried acnhe the latest version 5.0.6 r103037 and the problem persists , does anyone have any idea?
Re: Bridged network - unable connect host network
Posted: 3. Oct 2015, 10:47
by Lorenzo Soncini
Actually I have added a second NIC to the virtual machine attached to the "Host-only network" for connect to the GUEST to server HOST
LSo
Re: Bridged network - unable connect host network
Posted: 3. Oct 2015, 10:56
by ecate
But I can , for example, from the guest to open the page of google , I can only if we are in NAT , but not in Bridged if sending a ping to goole works .
Re: Bridged network - unable connect host network
Posted: 3. Oct 2015, 17:10
by Don12345
Having same type of problem, discussed in this thread:
posting.php?mode=reply&f=6&t=70052
Today, w/ VBox 5.0.6, can't see a second PCI / E NIC.
Re: Bridged network - unable connect host network
Posted: 3. Oct 2015, 18:36
by eddiegi686
Lorenzo, why do you need a second NIC on the guest? Usually one NIC is sufficient, e.g. I am using bridged networking on a Windows 10 x64 host with a CentOS 6.7 32 bit guest. I am able to access services on the guest, e.g. Web Server, Mediawiki pages. I am also able to ping the host from the guest and the guest from the host.
Previously I myself used two NICs to achieve this setup, however it was more complicated than it needed to be and caused me confusion, e.g. when the MAC address on the host changed I was unsure which virtual NIC was attached to which host NIC.
If you are seeing problems even with Virtualbox 5.0.6 then I suggest you post your guest's log file so that someone can help you.
Also do you have any firewalls running that might be blocking traffic? Try disabling them in that case.
Re: Bridged network - unable connect host network
Posted: 3. Oct 2015, 21:10
by ecate
eddiegi686 wrote:Lorenzo, why do you need a second NIC on the guest? Usually one NIC is sufficient, e.g. I am using bridged networking on a Windows 10 x64 host with a CentOS 6.7 32 bit guest. I am able to access services on the guest, e.g. Web Server, Mediawiki pages. I am also able to ping the host from the guest and the guest from the host.
Previously I myself used two NICs to achieve this setup, however it was more complicated than it needed to be and caused me confusion, e.g. when the MAC address on the host changed I was unsure which virtual NIC was attached to which host NIC.
If you are seeing problems even with Virtualbox 5.0.6 then I suggest you post your guest's log file so that someone can help you.
Also do you have any firewalls running that might be blocking traffic? Try disabling them in that case.
Thanks , I went crazy for days and I had the solution under the nose , the problem was the firewall avg I had not thought of .