ip conflict after upgrade to 5.02 if bridged network

Discussions about using Windows guests in VirtualBox.
Post Reply
Br1
Posts: 6
Joined: 26. Aug 2015, 10:56

ip conflict after upgrade to 5.02 if bridged network

Post by Br1 »

Hi All,
I upgraded from virtualbox 4.3.30 to 5.02 including extention pack.
I'm on laptop toshiba with Windows 7 and hosted machines XP and Windows 7

After this upgrade all my vms with "bridged network" give error "IP CONFLICT"

Please note it happens in each case:
- With wireless or linked network,
- it happens also if I set a statical IP address!!
- even if I'm the only pc in my network !

Please help.

Thank you
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Mostly XP

Re: ip conflict after upgrade to 5.02 if bridged network

Post by mpack »

Make sure all of your VMs have unique MAC addresses and machine names, and that none of them match the host.
Br1
Posts: 6
Joined: 26. Aug 2015, 10:56

Re: ip conflict after upgrade to 5.02 if bridged network

Post by Br1 »

Hi,
I've changed MAC address and computer name of every VM but without success!

Thanks

Bruno
Br1
Posts: 6
Joined: 26. Aug 2015, 10:56

Re: ip conflict after upgrade to 5.02 if bridged network

Post by Br1 »

Please note it happens only with wireless adapter!
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Mostly XP

Re: ip conflict after upgrade to 5.02 if bridged network

Post by mpack »

Well then, please expand on what give error "IP CONFLICT" means. I.e. the context, like who is issuing this error message. A screenshot might be useful too.

While you're doing that, a VM log might be useful too: with the VM fully shut down, right click it in GUI. Select "Show Log" and save "VBox.log" (ONLY) to a zip file. Attach the zip here.
Br1
Posts: 6
Joined: 26. Aug 2015, 10:56

Re: ip conflict after upgrade to 5.02 if bridged network

Post by Br1 »

Hi,
I attach a zip with screenshot of error and mv log.

Please note that the mac address reported in screenshot inside vm that generates ip conflict , it's the same of my real wireless network .

This is output of "ipconfig /all" from my phisycal laptop:


Configurazione IP di Windows

Nome host . . . . . . . . . . . . . . : Bruno-PC
Suffisso DNS primario . . . . . . . . :
Tipo nodo . . . . . . . . . . . . . . : Ibrido
Routing IP abilitato. . . . . . . . . : No
Proxy WINS abilitato . . . . . . . . : No
Elenco di ricerca suffissi DNS. . . . : lan

Scheda LAN wireless Connessione rete wireless 2:

Stato supporto. . . . . . . . . . . . : Supporto disconnesso
Suffisso DNS specifico per connessione:
Descrizione . . . . . . . . . . . . . : Microsoft Virtual WiFi Miniport Adapter #2
Indirizzo fisico. . . . . . . . . . . : 24-FD-52-16-B3-65
DHCP abilitato. . . . . . . . . . . . : S
Configurazione automatica abilitata : S

Scheda LAN wireless Connessione rete wireless:

Suffisso DNS specifico per connessione: lan
Descrizione . . . . . . . . . . . . . : Realtek RTL8723AE Wireless LAN 802.11n PCI-E NIC
Indirizzo fisico. . . . . . . . . . . : 24-FD-52-16-B3-65
DHCP abilitato. . . . . . . . . . . . : S
Configurazione automatica abilitata : S
Indirizzo IPv6 locale rispetto al collegamento . : fe80::3484:1efa:d4a7:b04c%55(Preferenziale)
Indirizzo IPv4. . . . . . . . . . . . : 192.168.1.186(Preferenziale)
Subnet mask . . . . . . . . . . . . . : 255.255.255.0
Lease ottenuto. . . . . . . . . . . . : gioved 3 settembre 2015 11:15:33
Scadenza lease . . . . . . . . . . . : venerd 4 settembre 2015 11:15:33
Gateway predefinito . . . . . . . . . : 192.168.1.254
Server DHCP . . . . . . . . . . . . . : 192.168.1.254
IAID DHCPv6 . . . . . . . . . . . : 237305170
DUID Client DHCPv6. . . . . . . . : 00-01-00-01-19-19-58-97-7C-05-07-83-DA-75
Server DNS . . . . . . . . . . . . . : 192.168.1.254
NetBIOS su TCP/IP . . . . . . . . . . : Attivato

Scheda Ethernet Connessione alla rete locale (LAN)* 15:

Stato supporto. . . . . . . . . . . . : Supporto disconnesso
Suffisso DNS specifico per connessione:
Descrizione . . . . . . . . . . . . . : Check Point Virtual Network Adapter For SSL Network Extender #2
Indirizzo fisico. . . . . . . . . . . : 54-9F-7C-9A-CD-19
DHCP abilitato. . . . . . . . . . . . : S
Configurazione automatica abilitata : S

Scheda Ethernet Connessione alla rete locale (LAN) 5:

Stato supporto. . . . . . . . . . . . : Supporto disconnesso
Suffisso DNS specifico per connessione:
Descrizione . . . . . . . . . . . . . : TAP-Windows Adapter V9
Indirizzo fisico. . . . . . . . . . . : 00-FF-A8-B2-C2-64
DHCP abilitato. . . . . . . . . . . . : S
Configurazione automatica abilitata : S

Scheda Ethernet Connessione alla rete locale (LAN)* 14:

Stato supporto. . . . . . . . . . . . : Supporto disconnesso
Suffisso DNS specifico per connessione:
Descrizione . . . . . . . . . . . . . : Check Point Virtual Network Adapter For SSL Network Extender
Indirizzo fisico. . . . . . . . . . . : 54-44-C5-5E-78-17
DHCP abilitato. . . . . . . . . . . . : S
Configurazione automatica abilitata : S

Scheda Ethernet Connessione alla rete locale (LAN) 2:

Stato supporto. . . . . . . . . . . . : Supporto disconnesso
Suffisso DNS specifico per connessione:
Descrizione . . . . . . . . . . . . . : StoneGate IPsec VPN Virtual Adapter
Indirizzo fisico. . . . . . . . . . . : 02-00-00-00-01-00
DHCP abilitato. . . . . . . . . . . . : S
Configurazione automatica abilitata : S

Scheda Ethernet Connessione alla rete locale (LAN):

Stato supporto. . . . . . . . . . . . : Supporto disconnesso
Suffisso DNS specifico per connessione: lan
Descrizione . . . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Indirizzo fisico. . . . . . . . . . . : 7C-05-07-83-DA-75
DHCP abilitato. . . . . . . . . . . . : S
Configurazione automatica abilitata : S

Scheda Ethernet VirtualBox Host-Only Network:

Suffisso DNS specifico per connessione:
Descrizione . . . . . . . . . . . . . : VirtualBox Host-Only Ethernet Adapter
Indirizzo fisico. . . . . . . . . . . : 0A-00-27-00-00-00
DHCP abilitato. . . . . . . . . . . . : No
Configurazione automatica abilitata : S
Indirizzo IPv6 locale rispetto al collegamento . : fe80::31bd:b0cd:b3:b2fd%40(Preferenziale)
Indirizzo IPv4. . . . . . . . . . . . : 192.168.56.1(Preferenziale)
Subnet mask . . . . . . . . . . . . . : 255.255.255.0
Gateway predefinito . . . . . . . . . :
IAID DHCPv6 . . . . . . . . . . . : 738852903
DUID Client DHCPv6. . . . . . . . : 00-01-00-01-19-19-58-97-7C-05-07-83-DA-75
Server DNS . . . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS su TCP/IP . . . . . . . . . . : Attivato

Scheda Ethernet VirtualBox Host-Only Network #2:

Suffisso DNS specifico per connessione:
Descrizione . . . . . . . . . . . . . : VirtualBox Host-Only Ethernet Adapter #2
Indirizzo fisico. . . . . . . . . . . : 0A-00-27-00-00-00
DHCP abilitato. . . . . . . . . . . . : No
Configurazione automatica abilitata : S
Indirizzo IPv6 locale rispetto al collegamento . : fe80::3c2c:9d26:321:6337%43(Preferenziale)
Indirizzo IPv4. . . . . . . . . . . . : 192.168.57.1(Preferenziale)
Subnet mask . . . . . . . . . . . . . : 255.255.255.0
Gateway predefinito . . . . . . . . . :
IAID DHCPv6 . . . . . . . . . . . : 1628045351
DUID Client DHCPv6. . . . . . . . : 00-01-00-01-19-19-58-97-7C-05-07-83-DA-75
Server DNS . . . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS su TCP/IP . . . . . . . . . . : Attivato

Scheda Tunnel isatap.{20101511-4976-424C-B8E0-8B924692CDE9}:

Stato supporto. . . . . . . . . . . . : Supporto disconnesso
Suffisso DNS specifico per connessione:
Descrizione . . . . . . . . . . . . . : Microsoft ISATAP Adapter
Indirizzo fisico. . . . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP abilitato. . . . . . . . . . . . : No
Configurazione automatica abilitata : S

Scheda Tunnel isatap.{A9820D85-0600-44E3-95A1-45462DD5E8BF}:

Stato supporto. . . . . . . . . . . . : Supporto disconnesso
Suffisso DNS specifico per connessione:
Descrizione . . . . . . . . . . . . . : Microsoft ISATAP Adapter #3
Indirizzo fisico. . . . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP abilitato. . . . . . . . . . . . : No
Configurazione automatica abilitata : S

Scheda Tunnel isatap.{A8B2C264-DB4F-4EF6-A335-2377DD109D65}:

Stato supporto. . . . . . . . . . . . : Supporto disconnesso
Suffisso DNS specifico per connessione:
Descrizione . . . . . . . . . . . . . : Microsoft ISATAP Adapter #5
Indirizzo fisico. . . . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP abilitato. . . . . . . . . . . . : No
Configurazione automatica abilitata : S

Scheda Tunnel isatap.lan:

Stato supporto. . . . . . . . . . . . : Supporto disconnesso
Suffisso DNS specifico per connessione: lan
Descrizione . . . . . . . . . . . . . : Microsoft ISATAP Adapter #6
Indirizzo fisico. . . . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP abilitato. . . . . . . . . . . . : No
Configurazione automatica abilitata : S

Scheda Tunnel isatap.{14ED46FB-A49E-4EA2-8BE7-E619DA14E28A}:

Stato supporto. . . . . . . . . . . . : Supporto disconnesso
Suffisso DNS specifico per connessione:
Descrizione . . . . . . . . . . . . . : Microsoft ISATAP Adapter #8
Indirizzo fisico. . . . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP abilitato. . . . . . . . . . . . : No
Configurazione automatica abilitata : S

Scheda Tunnel isatap.{AC7CB3C8-4027-442F-B345-87BC23C4B84D}:

Stato supporto. . . . . . . . . . . . : Supporto disconnesso
Suffisso DNS specifico per connessione:
Descrizione . . . . . . . . . . . . . : Microsoft ISATAP Adapter #10
Indirizzo fisico. . . . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP abilitato. . . . . . . . . . . . : No
Configurazione automatica abilitata : S

Scheda Tunnel isatap.{F9B3626E-5F41-4307-AD8F-3060F735027E}:

Stato supporto. . . . . . . . . . . . : Supporto disconnesso
Suffisso DNS specifico per connessione:
Descrizione . . . . . . . . . . . . . : Microsoft ISATAP Adapter #11
Indirizzo fisico. . . . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP abilitato. . . . . . . . . . . . : No
Configurazione automatica abilitata : S

Scheda Tunnel isatap.{B245D763-A7EF-4C7D-AEA1-490D25AB1587}:

Stato supporto. . . . . . . . . . . . : Supporto disconnesso
Suffisso DNS specifico per connessione:
Descrizione . . . . . . . . . . . . . : Microsoft ISATAP Adapter #13
Indirizzo fisico. . . . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP abilitato. . . . . . . . . . . . : No
Configurazione automatica abilitata : S


Thanks a lot!

Bruno
Attachments
vm_error.zip
(96.71 KiB) Downloaded 6 times
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Mostly XP

Re: ip conflict after upgrade to 5.02 if bridged network

Post by mpack »

Hmm. To me that seems like an excessive number of networking options. So, I'll leave you to people who know more about networking than I do.
Br1
Posts: 6
Joined: 26. Aug 2015, 10:56

Re: ip conflict after upgrade to 5.02 if bridged network

Post by Br1 »

Hi,
I unistalled virtualbox 5.02 and reinstalled 4.3.30 and now everything works fine again!

PLEASE check for the bug in 5.0.x

Thank you!!

Bruno
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Mostly XP

Re: ip conflict after upgrade to 5.02 if bridged network

Post by mpack »

If you have a fragile platform then practically anything you do to poke it might make some things work and other things break. So, I'm not convinced that I've seen a demonstration of a VirtualBox bug. However, by all means raise a BugTracker ticket for this.
Br1
Posts: 6
Joined: 26. Aug 2015, 10:56

Re: ip conflict after upgrade to 5.02 if bridged network

Post by Br1 »

I opened ticket #14541

Really Thanks your efforts!

Regards
Bruno
Post Reply