Windows Guest on Macbook Pro 2018 has no network

Discussions related to using VirtualBox on Mac OS X hosts.
Post Reply
macandroid
Posts: 27
Joined: 10. Nov 2018, 14:04

Windows Guest on Macbook Pro 2018 has no network

Post by macandroid »

Hi, I am new to this forum.

I have been using VB for years, on both macOS (High Sierra 13) and Linux (Ubuntu 16.04) hosts with Windows 7, 10 and Ubuntu 18.04 guests.
Last week I bought a new Macbook Pro 2018 with 16GB RAM and 500GB SSD of which I migrated all data, using the builtin 'Migration assstant', including the virtual machine images and VB settings, from my old 2011 MBP with 8GB RAM and 500GB SSD.
For safety I completely uninstalled VB and purged its settings and kept only the VMs, and reinstalled in again (VB 5.2.20).

But when using the same VDI of Windows 7 on my new MBP I cannot make network connections. Windows refuses to connect to the network. Message is 'network cable broken' which is not the case as the macOS host has normal network and internet connection.
The VM is set to NAT, using en0 (wireless).
When starting the Windows 10 VM, the same issue appeared.
But the Ubuntu 18.04 VM however *does* connect with the network and internet ('apt update' in the VM did work), and I could SSH into it from the macOS terminal.
And the network settings are the same on the Ubuntu VM and both Windows VMs.
I recovered the Win 7 VMware image from a backup disk (which is copied from a Linux host and runs flawlessly on my old MBP as well) but to no avail.

EDIT: When setting network to NAT, it does work normally, but that makes access to the VM (e.g. RDP or SMB) impossible, but 'Bridged does not work,

Does anyone have an idea what the problem is ?

ifconfig on host

Code: Select all

klaaspc:1 klaas$ ifconfig
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
	options=1203<RXCSUM,TXCSUM,TXSTATUS,SW_TIMESTAMP>
	inet 127.0.0.1 netmask 0xff000000 
	inet6 ::1 prefixlen 128 
	inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 
	nd6 options=201<PERFORMNUD,DAD>
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
XHC20: flags=0<> mtu 0
XHC1: flags=0<> mtu 0
XHC0: flags=0<> mtu 0
VHC128: flags=0<> mtu 0
en5: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	ether ac:de:48:00:11:22 
	inet6 fe80::aede:48ff:fe00:1122%en5 prefixlen 64 scopeid 0x8 
	nd6 options=201<PERFORMNUD,DAD>
	media: autoselect (100baseTX <full-duplex>)
	status: active
ap1: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
	ether f2:18:98:58:d2:cd 
	media: autoselect
	status: inactive
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	ether f0:18:98:58:d2:cd 
	inet6 fe80::82b:d987:4332:7827%en0 prefixlen 64 secured scopeid 0xa 
	inet 192.168.0.187 netmask 0xffffff00 broadcast 192.168.0.255
	nd6 options=201<PERFORMNUD,DAD>
	media: autoselect
	status: active
p2p0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 2304
	ether 02:18:98:58:d2:cd 
	media: autoselect
	status: inactive
awdl0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1484
	ether aa:21:51:33:a5:fd 
	inet6 fe80::a821:51ff:fe33:a5fd%awdl0 prefixlen 64 scopeid 0xc 
	nd6 options=201<PERFORMNUD,DAD>
	media: autoselect
	status: active
en1: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
	options=60<TSO4,TSO6>
	ether 36:00:50:02:8b:01 
	media: autoselect <full-duplex>
	status: inactive
en2: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
	options=60<TSO4,TSO6>
	ether 36:00:50:02:8b:00 
	media: autoselect <full-duplex>
	status: inactive
en3: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
	options=60<TSO4,TSO6>
	ether 36:00:50:02:8b:05 
	media: autoselect <full-duplex>
	status: inactive
en4: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
	options=60<TSO4,TSO6>
	ether 36:00:50:02:8b:04 
	media: autoselect <full-duplex>
	status: inactive
bridge0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	options=63<RXCSUM,TXCSUM,TSO4,TSO6>
	ether 36:00:50:02:8b:01 
	Configuration:
		id 0:0:0:0:0:0 priority 0 hellotime 0 fwddelay 0
		maxage 0 holdcnt 0 proto stp maxaddr 100 timeout 1200
		root id 0:0:0:0:0:0 priority 0 ifcost 0 port 0
		ipfilter disabled flags 0x2
	member: en1 flags=3<LEARNING,DISCOVER>
	        ifmaxaddr 0 port 13 priority 0 path cost 0
	member: en2 flags=3<LEARNING,DISCOVER>
	        ifmaxaddr 0 port 14 priority 0 path cost 0
	member: en3 flags=3<LEARNING,DISCOVER>
	        ifmaxaddr 0 port 15 priority 0 path cost 0
	member: en4 flags=3<LEARNING,DISCOVER>
	        ifmaxaddr 0 port 16 priority 0 path cost 0
	nd6 options=201<PERFORMNUD,DAD>
	media: <unknown type>
	status: inactive
utun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 2000
	inet6 fe80::9f6c:965a:e5c8:b24e%utun0 prefixlen 64 scopeid 0x12 
	nd6 options=201<PERFORMNUD,DAD>
klaaspc:1 klaas$ 

ipconfig on the Windows guest for this network:

Code: Select all

Ethernet adapter Local Area Connection 4:

   Connection-specific DNS Suffix  . : home
   IPv4 Address. . . . . . . . . . . : 192.168.0.199
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.0.254
The network settings for the VM (which are the same as for Linux VM which works)
The network settings for the VM (which are the same as for Linux VM which works)
Screen Shot 2018-11-10 at 13.22.08.png (77.02 KiB) Viewed 3190 times
EDIT: Added zipped log files.
The &quot;Network and Sharing Center&quot; screen in the Windows VM
The "Network and Sharing Center" screen in the Windows VM
Screen Shot 2018-11-10 at 13.24.21.png (63.79 KiB) Viewed 3190 times
Attachments
vboxlog.zip
(110.28 KiB) Downloaded 16 times
macandroid
Posts: 27
Joined: 10. Nov 2018, 14:04

Addition: Windows Guest on Macbook Pro 2018 has no network

Post by macandroid »

I tried three different Windows VMs, two Win10 and one Win7, none of them connected in Bridged, but all of them in NAT mode.
And tried two Linux VMs, one Ubuntu 18.04 and one Centos 7 and all worked flawlessly in Bridged mode and I could SSH into both VMs.
So it is a combination of Windows and VB on the MBP 2018.

I tried even another wifi hotspot, but to no avail.

I need the Windows VM to be accessible as a web server and for SMB sharing, which requires Bridged mode.
MichaelJBaldwin
Posts: 1
Joined: 21. Nov 2018, 19:05

Re: Windows Guest on Macbook Pro 2018 has no network

Post by MichaelJBaldwin »

I see a similar problem:
1. Wireless bridged networking on High Sierra host worked fine for Windows 7 64-bit client.
2. Upgraded to new MacBook last week, and wireless bridged networking on Mojave host cannot be used by Windows 7 clients. Upgraded to VirtualBox 5.2.22 of course.
3. Installed a bridged wired ethernet adaptor on my new MacBook and that works fine.
4. NAT doesn't work with wireless either.

Problem appears localized to wireless. Does the new version 6 address this?
andyp73
Volunteer
Posts: 1631
Joined: 25. May 2010, 23:48
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Assorted Linux, Windows Server 2012, DOS, Windows 10, BIOS/UEFI emulation

Re: Windows Guest on Macbook Pro 2018 has no network

Post by andyp73 »

MichaelJBaldwin wrote:Problem appears localized to wireless. Does the new version 6 address this?
Bridged networking isn't part of the wireless networking standard. Some wireless adapter drivers in combination with the right access point will work whereas others don't. I can use VirtualBox bridged to a wireless adapter on my Windows laptop but not from my 2017 iMac.

-Andy.
My crystal ball is currently broken. If you want assistance you are going to have to give me all of the necessary information.
Please don't ask me to do your homework for you, I have more than enough of my own things to do.
Post Reply