no able to use other then bridge net with win 11 as guest...

[p060477]

win 10 home as host
win 11 pro as guest
if you do not choose the net bridged but the other options seems that my network interface has been disappeared in win 11 guest:
and i'm really do not able to have internet and navigate in my win 11 guest
only with net bridged i'm able to navigate
when I change to nat the adapter disappear and there is no internet.
is it a virtualbox bug?

[scottgus1]

when I change to nat the adapter disappear and there is no internet.

Did you make a static IP address inside the VM's OS for its network adapter? If so, it is quite likely that the static IP address is not compatible with NAT's IP address range.

[p060477]

no...if you see the pics is clear that changin from bridged to nat any adapter is showing...
"only with net bridged i'm able to navigate
when I change to nat the adapter disappear and there is no internet."
if you see pics you see that i'm not really able to make a static ip for my vm's guest...cause i do not see any adapter...
see pics attached

[scottgus1]

OK, I see it now. The adapter completely disappears.

That is unprecedented in Virtualbox usage. Normally, changing from Bridged to NAT is merely like taking a computer's network cable out of your wall jack and sticking it into a neighbor's wall jack. The original adapter remains in the VM.

To have the adapter disappear completely, something unusual has to be done.

How exactly are you switching from Bridged to NAT?

[p060477]

...simply in the vm machine settings about net......
...do you know the vb manager gui...??...
there you can choose vm settings...about for ex screen...audio...usb....shared folder....
so strange that an expert user like you ask me this...

[mpack]

We know what is obvious to us. The goal was to find out what YOU know.

[scottgus1]

We know what is obvious to us.

Amen to that! @p060477, you keep a civil tone to your messages or we lock this and walk.

...simply in the vm machine settings about net......

There's two ways to do this in the main Virtualbox window's Network Settings. One way can cause the problem you face. The other does not cause it if done in the usual way.

So I reiterate, and expecting a properly respectful tone in your response:

How exactly are you switching from Bridged to NAT?

[p060477]

simply changing the net settings in the vm's win 11 guest
i attach the config working, the bridged, if i change to NAT comes the issue
the adapter disappeared

[scottgus1]

Thanks. Let's dig a little deeper:

Set the VM to Bridged.

Start the VM from full normal shutdown, not save-state. Log into the desktop.
Run these commands in the VM OS's command prompt:
ping 8.8.8.8
ipconfig /all

Then shut down the VM from within the VM's OS. 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 Attachments tab. (Configure your host OS to show all extensions so you can find the "vbox.log", not "vbox.log.1", etc.)

Also Zip the VM's .vbox file (not the .vbox-prev file), and post the zip file, using the forum's Attachments tab. (Configure your host OS to show all extensions if the folder that opens does not show a .vbox file.)

Repeat the entire process above and post the results and log & .vbox file with the VM set to NAT.

[p060477]

hi Scott
maybe is important i attach here the net config pic about i'm talking
this config really works fine with my win xp pro guest
but makes the issue described,of adapter disappearing, with my win 11 guest
pls take a look at this pic and confirm if i should follow yr last instructions or if there is something i have also to verify and test

i repeat this works with win xp pro guest
and make adapter disappearing with win 11 guest

thxs for yr attention
cheers

[scottgus1]

Thanks for the picture. Simply changing the "Attached To" dropdown from Bridged to NAT or NAT Network does not cause the problem you're having.

We'll still need the requested data to get a better idea of what is happening.

[p060477]

Hi Scott
here are the first 2 ones with Bridged setted

and this is the cmd line:

Bridged:

Microsoft Windows [Versione 10.0.22000.318]
(c) Microsoft Corporation. Tutti i diritti riservati.

C:\Windows\system32>ping 8.8.8.8

Esecuzione di Ping 8.8.8.8 con 32 byte di dati:
Risposta da 8.8.8.8: byte=32 durata=17ms TTL=116
Risposta da 8.8.8.8: byte=32 durata=13ms TTL=116
Risposta da 8.8.8.8: byte=32 durata=12ms TTL=116
Risposta da 8.8.8.8: byte=32 durata=13ms TTL=116

Statistiche Ping per 8.8.8.8:
Pacchetti: Trasmessi = 4, Ricevuti = 4,
Persi = 0 (0% persi),
Tempo approssimativo percorsi andata/ritorno in millisecondi:
Minimo = 12ms, Massimo = 17ms, Medio = 13ms

C:\Windows\system32>ipconfig /all

Configurazione IP di Windows

Nome host . . . . . . . . . . . . . . : Lu
Suffisso DNS primario . . . . . . . . :
Tipo nodo . . . . . . . . . . . . . . : Ibrido
Routing IP abilitato. . . . . . . . . : No
Proxy WINS abilitato . . . . . . . . : No

Scheda Ethernet Ethernet:

Suffisso DNS specifico per connessione:
Descrizione . . . . . . . . . . . . . : Intel(R) PRO/1000 MT Desktop Adapter
Indirizzo fisico. . . . . . . . . . . : 08-00-27-xxxxxxx
DHCP abilitato. . . . . . . . . . . . : Sì
Configurazione automatica abilitata : Sì
Indirizzo IPv6 locale rispetto al collegamento . : fe80:b46b:e9b1:2b2b%11(Preferenziale)
Indirizzo IPv4. . . . . . . . . . . . : 192.168.2.x(Preferenziale)
Subnet mask . . . . . . . . . . . . . : 255.255.255.0
Lease ottenuto. . . . . . . . . . . . : domenica 25 giugno 2023 21:20:01
Scadenza lease . . . . . . . . . . . : martedì 27 giugno 2023 21:20:05
Gateway predefinito . . . . . . . . . : 192.168.2.1
Server DHCP . . . . . . . . . . . . . : 192.168.2.1
IAID DHCPv6 . . . . . . . . . . . : 101187623
DUID Client DHCPv6. . . . . . . . : 00-01-00-01-2A-59-xxxxxxxxxxxx
Server DNS . . . . . . . . . . . . . : 192.168.2.1
NetBIOS su TCP/IP . . . . . . . . . . : Attivato

C:\Windows\system32>


thxs again for yr attention
cheers

[p060477]

and here are the last 2 ones with NAT Network setted

and here the cmd line:

NAT network:

Microsoft Windows [Versione 10.0.22000.318]
(c) Microsoft Corporation. Tutti i diritti riservati.

C:\Windows\system32>ping 8.8.8.8

Esecuzione di Ping 8.8.8.8 con 32 byte di dati:
PING: trasmissione non riuscita. Errore generale.
PING: trasmissione non riuscita. Errore generale.
PING: trasmissione non riuscita. Errore generale.
PING: trasmissione non riuscita. Errore generale.

Statistiche Ping per 8.8.8.8:
Pacchetti: Trasmessi = 4, Ricevuti = 0,
Persi = 4 (100% persi),

C:\Windows\system32>ipconfig /all

Configurazione IP di Windows

Nome host . . . . . . . . . . . . . . : Lu
Suffisso DNS primario . . . . . . . . :
Tipo nodo . . . . . . . . . . . . . . : Ibrido
Routing IP abilitato. . . . . . . . . : No
Proxy WINS abilitato . . . . . . . . : No

C:\Windows\system32>

thxs again
cheers

[scottgus1]

Thanks for the information. The .vbox files do in fact show that the VM on NAT Network does not have a network adapter in it:

<Network>
<Adapter slot="0" enabled="true" MACAddress="08002772F84D" type="82540EM">
<DisabledModes>
<NAT localhost-reachable="true"/>
<InternalNetwork name="intnet"/>
<NATNetwork name="NatNetwork"/>
</DisabledModes>
<BridgedInterface name="Realtek PCIe GBE Family Controller"/>
</Adapter>
</Network>

<Network>
<Adapter slot="0" enabled="true" MACAddress="08002772F84D" promiscuousModePolicy="AllowAll"> <note no "type"
<DisabledModes>
<NAT localhost-reachable="true"/>
<BridgedInterface name="Realtek PCIe GBE Family Controller"/>
<InternalNetwork name="intnet"/>
</DisabledModes>
<NATNetwork name="NatNetwork"/>
</Adapter>
</Network>

Why this is happening is a very big puzzle, though. I tried my 7.0.8 host, switching the VM's network between Bridged and NAT Network, and the network adapter remained for both settings. "Type" was visible in both .vbox file contents.

Even bigger a puzzle is that Virtualbox does not have a way for the VM adapter to be enabled but for there to not have an adapter type. There are 6 adapter types in the "Adapter Type" dropdown, and none of them remove the "type" data from the .vbox file.

There is something else going on here that has not been revealed yet. (NB I see mention of "Greenvbox" in the file paths and non-default install path; is a 3rd-party VM controller involved?)

One thing I do see is that the first screenshot of your Windows 11 VM's Network settings for Bridged is from your Windows 10 host in Italian, if I read correctly. The second VM network settings screenshot for NAT Network is from an XP VM on a Vista or 7 host in English. So the shown data is not consistent.

Please remake those screenshots again, this time both of them from the failing W11 VM on the W10 host. Crop to show only the VM settings window, not the whole host screen, so the text will be readable. Show the Advanced data as you've done in the first screenshots, so we can see the Adapter Type setting as you switch from Bridged to NAT Network and back.

[p060477]

Hi Scott, thanks so much for yr attention
here are the 2 screenshoots you ask

thxs again
cheers