virtualbox.org

Hi everyone.

I was trying to find a solution for my problem in Google, though, the Google didn't help me.

The problem is that in my Windows 10 Guest Os in the System settings "Network status is not connected" is shown in the windows. And Edge doesn't open pages. Also, my Office apps (Word, Excel, etc.) could not connect to internet (i think because of that reason) and apply my license, so I can only read documents, but not to create.

Nevertheless, google chrome or firefox is connecting to internet and showing pages successefully.

P.S. I don't like IE, and of course, I don't like Edge. But if that has been the only reason... But I think (and I'm sure) that this is also the reason of my Office Apps cannot connect to internet and apply my license.

P.P.S. In the adapter settings --> Status shown that "IPv4 Connectivity - Not connected".

You're the second person reporting that, and I honestly don't know why that's happening to your guest. Did you select the appropriate type of network (Home, Work, Public) when asked? Can you change it?

Interesting.

In the firewall settings I see that "Private networks" - NOT CONNECTED, and "Guest or public networks" is Connected.

Interesting, is that really that nobody except me (and someone more person) has this problem?

I thought that my hint was enough, but your should change your network from Public to Work, instructions all over the internet. And please post the output of the command (run in the guest):

• ipconfig /all

Moving to "Windows Guests" from "Linux Hosts".

Here is the output of the command "ipconfig /all"

Code: Select all

C:\Users\peter>ipconfig /all

Windows IP Configuration

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

Ethernet adapter Ethernet:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Desktop Adapter
   Physical Address. . . . . . . . . : 08-00-27-B2-FD-AB
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 10.0.2.15(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : 11 июня 2018 г. 20:48:50
   Lease Expires . . . . . . . . . . : 12 июня 2018 г. 20:48:50
   Default Gateway . . . . . . . . . : 10.0.2.2
   DHCP Server . . . . . . . . . . . : 10.0.2.2
   DNS Servers . . . . . . . . . . . : 8.8.8.8
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{0BE41E3F-4198-4423-B8AF-A9B2710BB998}:

   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

Your configuration looks right for NAT. What you need to do now is to make the network Public from Private. This is NOT a VirtualBox issue, but here are some links (I searched for "windows public or private network command line", there may be more):

• https://www.top-password.com/blog/chang ... indows-10/
• https://serverfault.com/questions/63908 ... er-2012-r2
• https://www.tenforums.com/tutorials/681 ... -10-a.html
• ...