[SOLVED] Not seeing network in bridged adapter

Discussions related to using VirtualBox on Linux hosts.
Post Reply
GpaBob
Posts: 10
Joined: 16. Mar 2021, 21:41

[SOLVED] Not seeing network in bridged adapter

Post by GpaBob »

I’m running Linux Mint 21.04 fully updated. I’m trying to run Windows 10 in VirtualBox. I have VBox installed in my host machine, Windows 10 installed in VBox, and Windows 10 updated. Let me add that I am very new at using VirtualBOX or any virtual machines. My Windows 10 has internet connection (obviously, since I can update it). When I select the network in Windows 10 file manager, I can see my printer, my Roku, etc., but not my NAS. My NAS is a Raspberry PI 4 and I can connect to it with a physical Windows 10 system. I can’t connect to the printer in VBox as Windows can’t seem to find it. I am using bridged adapter for a network adapter. It is the only network adapter in settings.
Can anyone help me with this issue? I will be glad to upload any more info you may need.
Thanks.
Last edited by GpaBob on 23. Apr 2023, 20:06, edited 1 time in total.
scottgus1
Site Moderator
Posts: 20965
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: Not seeing network in bridged adapter

Post by scottgus1 »

1. Start the VM from full normal shutdown, not save-state. Run until you see the problem happen, then shut down the VM from within the VM's OS if possible. If not possible, close the Virtualbox window for the VM with the Power Off option set.

Right-click the VM in the main Virtualbox window's VM list, choose Show in Explorer/Finder/File Manager. In the "Logs" subfolder, zip the VM's "vbox.log", and post the zip file, using the forum's Upload Attachment tab. (Configure your host OS to show all extensions so you can find the "vbox.log", not "vbox.log.1", etc.)

2. Right-click the VM in the main Virtualbox window's VM list, choose Show in Explorer/Finder/File Manager. Zip the VM's .vbox file (not the .vbox-prev file), and post the zip file, using the forum's Upload Attachment tab. (Configure your host OS to show all extensions if the folder that opens does not show a .vbox file.)

3. In the Linux host OS, open a Terminal and run ifconfig or ip address. Post the command output.

4. In the Windows VM OS, open a Command Prompt and run ipconfig /all. Post the command output.

5. In both host and VM OS's, ping 8.8.8.8. Post the command outputs. Label which is which.

6. In both host and VM OS's, ping your NAS via its IP address and its network name if it has one. Post the command outputs. Label which is which.
GpaBob
Posts: 10
Joined: 16. Mar 2021, 21:41

Re: Not seeing network in bridged adapter

Post by GpaBob »

I have attached the logs folder and the win10.vbox file. I can't figure out how to copy and paste the Win 10 ipconfig /all or the ping commands. Here are the results from LM21:
Linux mint:
bob@Desktop:~$ ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=114 time=57.5 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=114 time=248 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=114 time=364 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=114 time=73.6 ms
64 bytes from 8.8.8.8: icmp_seq=5 ttl=114 time=1100 ms
64 bytes from 8.8.8.8: icmp_seq=6 ttl=114 time=522 ms
^C
--- 8.8.8.8 ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5025ms
rtt min/avg/max/mdev = 57.546/394.247/1100.360/354.357 ms, pipe 2

bob@Desktop:~$ ifconfig
eno1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.86.36 netmask 255.255.255.0 broadcast 192.168.86.255
inet6 fd61:a716:c401:6b73:2daa:f020:ee5a:1170 prefixlen 64 scopeid 0x0<global>
inet6 fe80::4733:e1db:b1f5:e989 prefixlen 64 scopeid 0x20<link>
ether 94:de:80:7b:41:0a txqueuelen 1000 (Ethernet)
RX packets 14469023 bytes 14476731480 (14.4 GB)
RX errors 0 dropped 136 overruns 0 frame 0
TX packets 7333906 bytes 6909406730 (6.9 GB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 20 memory 0xf7c00000-f7c20000

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 203165 bytes 48814827 (48.8 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 203165 bytes 48814827 (48.8 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

surfshark_ipv6: flags=195<UP,BROADCAST,RUNNING,NOARP> mtu 1500
inet6 fdbe:2bde:b490:9e47:: prefixlen 64 scopeid 0x0<global>
inet6 fe80::6047:4db2:275f:430f prefixlen 64 scopeid 0x20<link>
ether 62:90:79:1f:f7:cd txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 5630 bytes 529220 (529.2 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

surfshark_wg: flags=209<UP,POINTOPOINT,RUNNING,NOARP> mtu 1280
inet 10.14.0.2 netmask 255.255.0.0 destination 10.14.0.2
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 1000 (UNSPEC)
RX packets 4044938 bytes 4806921916 (4.8 GB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 2127130 bytes 305013500 (305.0 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

vboxnet0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.56.1 netmask 255.255.255.0 broadcast 192.168.56.255
inet6 fe80::800:27ff:fe00:0 prefixlen 64 scopeid 0x20<link>
ether 0a:00:27:00:00:00 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 571 bytes 87918 (87.9 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

Here are the results from pinging my NAS in LM21:
bob@Desktop:~$ ping 192.168.86.34
PING 192.168.86.34 (192.168.86.34) 56(84) bytes of data.
64 bytes from 192.168.86.34: icmp_seq=1 ttl=64 time=0.264 ms
64 bytes from 192.168.86.34: icmp_seq=2 ttl=64 time=0.198 ms
64 bytes from 192.168.86.34: icmp_seq=3 ttl=64 time=0.246 ms
64 bytes from 192.168.86.34: icmp_seq=4 ttl=64 time=0.247 ms
64 bytes from 192.168.86.34: icmp_seq=5 ttl=64 time=0.207 ms
64 bytes from 192.168.86.34: icmp_seq=6 ttl=64 time=0.209 ms
^C
--- 192.168.86.34 ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5123ms
rtt min/avg/max/mdev = 0.198/0.228/0.264/0.024 ms

If you can tell me how to copy and paste the Win 10 I will be happy to do it. I haven't used Windows for about 8 years or so (just after win10 came out).
Thank you for your help.
Bob
Attachments
Win 10.vbox.zip
(1.96 KiB) Downloaded 6 times
Logs.zip
(132.46 KiB) Downloaded 3 times
scottgus1
Site Moderator
Posts: 20965
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: Not seeing network in bridged adapter

Post by scottgus1 »

GpaBob wrote:how to copy and paste the Win 10
A screenshot from the host OS, cropped to show the command and output, would do as well. Please post the screenshots with Upload Attachment, too.
GpaBob
Posts: 10
Joined: 16. Mar 2021, 21:41

Re: Not seeing network in bridged adapter

Post by GpaBob »

I have a .png photo of each of the results in Win 10 but the files are in the 250-300 Kb size and too big to be accepted.
GpaBob
Posts: 10
Joined: 16. Mar 2021, 21:41

Re: Not seeing network in bridged adapter

Post by GpaBob »

Here is a second try:

Microsoft Windows [Version 10.0.19045.2846]
(c) Microsoft Corporation. All rights reserved.

C:\Windows\system32>ping 8.8.8.8

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=661ms TTL=55
Reply from 8.8.8.8: bytes=32 time=262ms TTL=55
Reply from 8.8.8.8: bytes=32 time=1013ms TTL=55
Reply from 8.8.8.8: bytes=32 time=1074ms TTL=55

Ping statistics for 8.8.8.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 262ms, Maximum = 1074ms, Average = 752ms

C:\Windows\system32>ipconfig

Windows IP Configuration


Ethernet adapter Ethernet:

Connection-specific DNS Suffix . : lan
IPv6 Address. . . . . . . . . . . : fd61:a716:c401:6b73:e544:5974:44ad:27f7
Temporary IPv6 Address. . . . . . : fd61:a716:c401:6b73:30ab:ec04:f06a:5b65
Link-local IPv6 Address . . . . . : fe80::dc09:4847:d59:afa9%4
IPv4 Address. . . . . . . . . . . : 192.168.86.163
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.86.1

Hope this helps.
Bob
scottgus1
Site Moderator
Posts: 20965
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: Not seeing network in bridged adapter

Post by scottgus1 »

That's good, yes. It appears your VM has a correct IP address in the LAN's range, and the VM can ping the internet. Can the VM ping the host and access a shared folder on the host OS? Can the VM ping the NAS or the printer?

FWIW, if ping to the web works, then the Virtualbox Bridged network looks to be working, which is borne out by the VM OS being able to see the printer and the Roku, and it can get updates, which would all be impossible if the network wasn't working. Often there is some other configuration error(s) in the various services beyond what Virtualbox has control of (like maybe SMB1 only on the Raspberry Pi and Windows 10 only has SMB2 or greater, etc).
GpaBob
Posts: 10
Joined: 16. Mar 2021, 21:41

Re: Not seeing network in bridged adapter

Post by GpaBob »

<Can the VM ping the host and access a shared folder on the host OS? Can the VM ping the NAS or the printer?>
Yes, in all three cases. Here are the results:

Microsoft Windows [Version 10.0.19045.2846]
(c) Microsoft Corporation. All rights reserved.

C:\Windows\system32>ping 192.168.86.36 {EDIT} NAS

Pinging 192.168.86.36 with 32 bytes of data:
Reply from 192.168.86.36: bytes=32 time<1ms TTL=64
Reply from 192.168.86.36: bytes=32 time<1ms TTL=64
Reply from 192.168.86.36: bytes=32 time<1ms TTL=64
Reply from 192.168.86.36: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.86.36:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Windows\system32>ping 192.168.86.34
 Edit:  Host

Pinging 192.168.86.34 with 32 bytes of data:
Reply from 192.168.86.34: bytes=32 time<1ms TTL=64
Reply from 192.168.86.34: bytes=32 time<1ms TTL=64
Reply from 192.168.86.34: bytes=32 time<1ms TTL=64
Reply from 192.168.86.34: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.86.34:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Windows\system32>ping 192.168.86.38
 Edit:  Printer

Pinging 192.168.86.38 with 32 bytes of data:
Reply from 192.168.86.38: bytes=32 time=120ms TTL=64
Reply from 192.168.86.38: bytes=32 time=8ms TTL=64
Reply from 192.168.86.38: bytes=32 time=7ms TTL=64
Reply from 192.168.86.38: bytes=32 time=70ms TTL=64

Ping statistics for 192.168.86.38:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 7ms, Maximum = 120ms, Average = 51ms

C:\Windows\system32>

I think I have not pushed a right button in my config file and that is where I am lost. I had a working VBox a few days ago and it could see the network okay, then did something stupid and screwed it up. So I deleted everything and started over and now can't see the network. I haven't changed anything SMB or otherwise since. 
 
scottgus1
Site Moderator
Posts: 20965
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: Not seeing network in bridged adapter

Post by scottgus1 »

Bridged doesn't have any special configuration settings in Virtualbox, like port forwarding etc. There's nothing to get in the way of the traffic. See Virtualbox Networks: In Pictures: Bridged Adapter.

The ability of the VM to ping the NAS shows that the network is working and that the VM can see the NAS. I think there's something not working inside the VM's OS, or the NAS has a block against the VM's OS in its OS, or something like that.

Try making a new 10 VM with a fresh test OS install, Bridged. See if that VM can access the NAS.
GpaBob
Posts: 10
Joined: 16. Mar 2021, 21:41

Re: Not seeing network in bridged adapter

Post by GpaBob »

I tried a completely new install in VBox and the new one is the same as the old one. Can't see my NAS.
GpaBob
Posts: 10
Joined: 16. Mar 2021, 21:41

Re: Not seeing network in bridged adapter

Post by GpaBob »

I have fixed it. My NAS is a SMB 1.0/CIFS device. The answer was found on this website: https://www.stellarinfo.co.in/blog/how- ... indows-10/ . Specifically, for me, it was Fix2. I enabled the SMB 1.0/cifs and I now see my network. Your previous response is what made me look in that direction. I didn't do this on the orginal machine that did work as I would have remembered it so I can't explain that part. Thanks for your help.
scottgus1
Site Moderator
Posts: 20965
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: [SOLVED] Not seeing network in bridged adapter

Post by scottgus1 »

Great! Glad you kept up the hunt and found a solution! Keep in mind that SMB1 was Wannacry's vector, and turning it back on in Windows will allow Wannacry back in again if it comes to pay a visit.

I don't know if it's possible, but try to see if SMB2 can be run on your NAS.
GpaBob
Posts: 10
Joined: 16. Mar 2021, 21:41

Re: [SOLVED] Not seeing network in bridged adapter

Post by GpaBob »

l Will check it out. THANKS!
Post Reply