Networking Issues

[jsimmonstx]

Running VB 5.2.22 r126460 on Linux Mint 19...

I've created a Lubuntu 18.04 VM, and a Windows 7 VM:

0) There are no Host Networks defined in Virtual Box.
1) For both VMs, I selected "Bridged Adapter".
2) Both machines are using the same host network adapter (enp2s0).
3) The Lubuntu VM can see the host machine, and all of the shares on the network.
4) The Windows VM cannot see the host machine or any network shares.
5) The Windows VM has worked in the past (as late as Saturday)

[socratis]

4) The Windows VM cannot see the host machine or any network shares.

It's not a matter of "seeing", it's a matter of pinging.

5) The Windows VM has worked in the past (as late as Saturday)

Then something changed in your guest, no?

I've included a sample output, with only the parameters that you should be focusing on:

> ipconfig /all
   Physical Address. . : 08-00-27-36-28-0C            <-- VBox NICs start with 08-00-27
   IPv4 Address. . . . : 192.168.100.103(Preferred)
   Default Gateway . . : 192.168.100.1
   DNS Servers . . . . : 1.1.1.1

Then, once you have the key values, try the following commands:

> ping <DefaultGateway>             <-- tests your connectivity
> ping <DNSserver>                  <-- tests your DNS server
> ping 1.1.1.1                      <-- tests outgoing connectivity
> ping download.virtualbox.org      <-- tests name resolution

If you can "ping <DefaultGateway>", if you can "ping <DNSserver>", if you can "ping 1.1.1.1", if you can "ping download.virtualbox.org", VirtualBox is working as it should. You should look elsewhere for your networking connectivity. Look in your host for firewalls, proxies, antivirus filters, web-cleaning applications, redirectors, etc.

[jsimmonstx]

The thing is, I haven't changed anything. I start the VM, use it, and shut it down. I did apply updates on Saturday, but there was nothing in the updates related to the network adapter. It was just your standard "Windows is crap, and here's our latest attempt to fix it" stuff. When I created the VM, I didn't do anything but select Bridged Adapter under Network in the machine settings.

Can't ping gateway (the gateway IP isn't even shown), or DNS servers.

The VB MAC address is 08-00-27..., so that's correct.

IPv4 address is not on the same subnet as the rest of my machines. IPConfig shows:

DHCP Enabled..................... : Yes
AutoConfiguration Enabled........ : Yes
Subnet Mask...................... : 255.255.0.0
Autoconfiguration IPv4 address... : 169.254.78.69 (preferred)
DNS Servers...................... : 192.168.1.2, 192.168.1.3

I don't have any idea where it got the IPv4 IP address. my network is 192.168.1.n.

(My use of "can't see" is a playful euphemism for "no workee".)

[socratis]

I need to see a complete VBox.log, from a complete VM run, where the problem occurs:

• Start the VM from cold-boot (not from a paused or saved state) / Observe problem / Shutdown the VM (force close it if you have to).
• With the VM completely shut down (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".
• Save only the first "VBox.log", ZIP it and attach it to your response. See the "Upload attachment" tab below the reply form.

I would also like to see the complete output from the following command in the guest:

• 
  ipconfig /all

[jsimmonstx]

Output for ipconfig /all

Code: Select all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : marsvm
   Primary Dns Suffix  . . . . . . . : 
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Desktop Adapter
   Physical Address. . . . . . . . . : 08-00-27-38-80-AA
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::90bc:7a73:d480:4e45%11(Preferred) 
   Autoconfiguration IPv4 Address. . : 169.254.78.69(Preferred) 
   Subnet Mask . . . . . . . . . . . : 255.255.0.0
   Default Gateway . . . . . . . . . : 
   DHCPv6 IAID . . . . . . . . . . . : 235405351
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-23-8B-4B-32-08-00-27-38-80-AA
   DNS Servers . . . . . . . . . . . : 192.168.1.2
                                       192.168.1.3
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{D8B84984-8F47-4194-9EC2-34C5782C0EDE}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

[jsimmonstx]

And the weirdness continues...

I came home from work today with a couple of things to try, and when I fired up the VM, everything was okay.

I'm not sure why Windows lost its mind, and I'm kinda afraid to shut the VM down now...

I am loathe to mark this as [SOLVED] because I didn't do anything to fix it.

[socratis]

@jsimmonstx
Does this still work? If it does, there's no point in marking it as [Solved], because as you said no "solution" was provided, it was a random act of a collection of bytes. I'll simply mark the thread as [WorksForMe]...