Bridged Adapter issues on a Win10 VM

[RobertSRUSA]

Hello,

I have recently installed virtualbox on xbuntu 20.04 and successfully created a Win10 VM. I want the VM to use the same IP range as the linux host (192.168.1.x). Unfortunately, no matter which Bridged Adapter I choose in the Settings, I still do not get the correct IP:

Code: Select all

Bridged Adapter
    eno1 - 169.254.89.93
    vmnet1 - 192.168.39.130
    vmnet8 - 172.16.238.129

How do I configure the network so that the VM receives the same DHCP IP as the linux host?

-Robert

[scottgus1]

Please right-click the guest in the main Virtualbox window's guest list, choose "Show in Explorer/Finder/File Manager". In the window that opens, zip the guest's .vbox file, and post the zip file, using the forum's Upload Attachment tab.

Also, provide the text output of 'ip address' and 'vboxmanage list hostonlyifs' on the host PC.

[RobertSRUSA]

I have uploaded the file. Here's the output from the two commands:

Code: Select all

# ip address
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever

2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether a8:a1:59:29:15:8c brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.206/24 brd 192.168.1.255 scope global dynamic noprefixroute eno1
       valid_lft 603303sec preferred_lft 603303sec
    inet6 fe80::dbac:64a2:e7aa:6ad3/64 scope link noprefixroute
       valid_lft forever preferred_lft forever

3: vmnet1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000
    link/ether 00:50:56:c0:00:01 brd ff:ff:ff:ff:ff:ff
    inet 192.168.39.1/24 brd 192.168.39.255 scope global vmnet1
       valid_lft forever preferred_lft forever
    inet6 fe80::250:56ff:fec0:1/64 scope link
       valid_lft forever preferred_lft forever

4: vmnet8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000
    link/ether 00:50:56:c0:00:08 brd ff:ff:ff:ff:ff:ff
    inet 172.16.238.1/24 brd 172.16.238.255 scope global vmnet8
       valid_lft forever preferred_lft forever
    inet6 fe80::250:56ff:fec0:8/64 scope link
       valid_lft forever preferred_lft forever

Code: Select all

# vboxmanage list hostonlyifs
#

[scottgus1]

You've been doing a lot of experimentation:

<Network>
<Adapter slot="0" enabled="true" MACAddress="0800271795D3" promiscuousModePolicy="AllowAll" type="82540EM">
<DisabledModes>
<BridgedInterface name="eno1"/>
<NATNetwork name="NatNetwork"/>
</DisabledModes>
<InternalNetwork name="intnet"/>
</Adapter>
<Adapter slot="1" MACAddress="080027082144" promiscuousModePolicy="AllowNetwork" type="virtio">
<DisabledModes>
<InternalNetwork name="intnet"/>
<NATNetwork name="NatNetwork"/>
</DisabledModes>
<BridgedInterface name="eno1"/>
</Adapter>
<Adapter slot="2" MACAddress="080027294D6D" promiscuousModePolicy="AllowAll" type="Am79C970A">
<DisabledModes>
<InternalNetwork name="intnet"/>
<NATNetwork name="NatNetwork"/>
</DisabledModes>
<BridgedInterface name="vmnet8"/>
</Adapter>
<Adapter slot="3" MACAddress="08002740A278" promiscuousModePolicy="AllowAll">
<DisabledModes>
<InternalNetwork name="intnet"/>
<NATNetwork name="NatNetwork"/>
</DisabledModes>
<BridgedInterface name="vmnet1"/>
</Adapter>
</Network>

Based on you original IP addresses, compared to the 'ip address' command output, Bridging to vmnet 1 & 8, whatever they are, were working, or someone set static IPs so it looks like they were working.

However, it appears that eno1 is the correct physical Ethernet adapter, it is also the only UP adapter that can be used.

Guest adapter slot 1, the second tab, is Bridged to eno1, but uses the virtio adapter, and Windows 10 does not come with drivers for the virtio adapter. It is always best to stick with the hardware types the New Guest Wizard picked, and not to thrash when a problem develops.

The first Network tab is the only one that is enabled, use the first tab and leave the rest alone and disabled.

Set the network card type to the Windows 10 default 'Intel PRO 1000 MT Desktop' , set to Bridged and point at eno1, and start the guest. Set the guest OS to automatic IP address from DHCP. If you are in an office with an IT dept, check that your IT policies allow multiple IP addresses on the one switch port your PC is using. Try the guest, see what you get.

[RobertSRUSA]

Thank you for the detailed response! Right now, I am comparing Virtualbox against VMware workstation pro, and trying to decide which best suits my needs. I didn't realize I had so many network adapters!

I made the changes that you suggested with the network settings, but it's still not working. The Win10 VM is still not able to obtain an IP from the DHCP server when in Bridged mode (see attached image). I thought about the IT policy that you mentioned, but then realized that I have bridge mode working correctly on the Win10 VM running on vmware workstation. I attached a screenshot of the vmware network editor in case that could be causing conflicts with virtualbox.