Page 1 of 1

Bridged network not working

Posted: 6. Nov 2014, 21:14
by Javia1492
Hello,

I am using a Dell Latitude E6520 laptop and running VirtualBox 4.2.12 r84980 with a windows guest (Win7 Professional 64-bit SP1). I am trying to use bridged network adapter (Intel(R) 82579LM Gigabit Network Connection), but I am unable to access the network through the guest. I can access the network through the host.

I have tried other modes, such as NAT and internal network (used for file transferring), and while using NAT i am able to get access to the network, I cannot access the guest through the host from the network. I.e, i can ping the host using the guest, but not vice-versa. Using internal network, i can ping bidirectionally, but i cannot access the network using the guest (but this is by design).

I need to be able to access the guest from the host through the network while enabling the guest to access the network because i am using it for development and need it to communicate directly to my device.

Device manager shows no errors, but the network adapter is listed as Intel Pro/1000 MT Desktop Adapter.

Results from ipconfig /all for Guest:

Windows IP Configuration

Host Name . . . . . . . . . . . . : Design-PC
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-AA-3D-7A
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::8b6:228a:6991:d217%11(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.210.23(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 235405351
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1B-E0-A0-DA-08-00-27-AA-3D-7A

DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{0CAC6F17-EB9F-4264-96F2-0458905404FB}:

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

Tunnel adapter Local Area Connection* 9:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes


Results from ipconfig /all on Host:
Windows IP Configuration

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

Wireless LAN adapter Wireless Network Connection 2:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Virtual WiFi Miniport Adapter
Physical Address. . . . . . . . . : 68-94-23-13-4A-25
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wireless Network Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : DW1501 Wireless-N WLAN Half-Mini Card
Physical Address. . . . . . . . . : 68-94-23-13-4A-25
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) 82579LM Gigabit Network Connecti
on
Physical Address. . . . . . . . . : D4-BE-D9-44-A3-08
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::acf4:72bc:7f20:8dd9%11(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.100.97(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.100.109
DHCPv6 IAID . . . . . . . . . . . : 248823513
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-17-FE-43-09-D4-BE-D9-44-A3-08

DNS Servers . . . . . . . . . . . : 172.22.68.19
172.22.78.19
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter VirtualBox Host-Only Network:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VirtualBox Host-Only Ethernet Adapter
Physical Address. . . . . . . . . : 08-00-27-00-5C-34
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::1c44:b21e:71be:7d5e%27(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.56.1(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 554172455
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-17-FE-43-09-D4-BE-D9-44-A3-08

DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter VMware Network Adapter VMnet1:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet
1
Physical Address. . . . . . . . . : 00-50-56-C0-00-01
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::202e:f5c9:c0b:a8a0%35(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.27.1(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 939544662
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-17-FE-43-09-D4-BE-D9-44-A3-08

DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter VMware Network Adapter VMnet8:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet
8
Physical Address. . . . . . . . . : 00-50-56-C0-00-08
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::cd25:51e2:9f8d:d9b2%37(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.121.1(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 973099094
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-17-FE-43-09-D4-BE-D9-44-A3-08

DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Reusable ISATAP Interface {F3905D79-EF92-4672-A817-4EC59B818E69}:


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

Tunnel adapter isatap.{FA7B07DF-D5A6-4115-97CE-DA097FD55AEE}:

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

Tunnel adapter isatap.{034149B4-B6CC-49BC-B8D8-FB81BD522C13}:

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

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{0CD976AE-A0E9-42CA-A2A2-32168AAA7243}:

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

Tunnel adapter isatap.{25C8F06A-7F9E-41DE-A3DF-4A7B428265D5}:

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

Tunnel adapter isatap.{4A0449D7-FBE0-4DC5-8B9E-8CF741CDE11E}:

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

Tunnel adapter isatap.{044A9C0C-79A6-4C50-96E6-B8D29D10091D}:

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

Any help would be much appreciated as i really need to get this connection working.
Thank you in advance.

Re: Bridged network not working

Posted: 6. Nov 2014, 21:48
by Perryg
From the hosts terminal/command window type VBoxManage showvminfo <VM Name> --details and post here. Replace <VM Name> with the actual name of the VM. Use " " if the name has a space in it.

Note if the host is Windows you need to be in the directory that has VBoxManage.exe for the command to work.

Re: Bridged network not working

Posted: 6. Nov 2014, 22:08
by Javia1492
Perryg wrote:From the hosts terminal/command window type VBoxManage showvminfo <VM Name> --details and post here. Replace <VM Name> with the actual name of the VM. Use " " if the name has a space in it.

Note if the host is Windows you need to be in the directory that has VBoxManage.exe for the command to work.
I was unable to run that command because the location of the virtualbox installation is different than where the virtual machines are being stored. The host is Windows and I set the directory for the virtual box installation path where VBoxManage.exe is located, but it cannot find the VMs. I think it is because the folder with the Virtual Machine information is in a different location, C:\User\<Name>\VirtualBox VM as opposed to the virtualbox installation being in C:\Program Files\Oracle\VirtualBox.

Re: Bridged network not working

Posted: 6. Nov 2014, 23:54
by Javia1492
Ok so i managed to get the command to work.

Here is the result of VBoxmanage showvminfo <VMName> --details for the host Windows OS:
C:\Users\JBadmin\VirtualBox VMs>VBoxManage showvminfo "WEC7 DEV1" --details
Name: WEC7 DEV1
Groups: /
Guest OS: Windows 7 (64 bit)
UUID: b5aa3635-5c41-4c07-9a3e-56c7dd2dcd7b
Config file: C:\Users\JBadmin\VirtualBox VMs\WEC7 DEV1\WEC7 DEV1.vbox
Snapshot folder: C:\Users\JBadmin\VirtualBox VMs\WEC7 DEV1\Snapshots
Log folder: C:\Users\JBadmin\VirtualBox VMs\WEC7 DEV1\Logs
Hardware UUID: b5aa3635-5c41-4c07-9a3e-56c7dd2dcd7b
Memory size: 2048MB
Page Fusion: off
VRAM size: 18MB
CPU exec cap: 100%
HPET: off
Chipset: piix3
Firmware: BIOS
Number of CPUs: 1
Synthetic Cpu: off
CPUID overrides: None
Boot menu mode: message and menu
Boot Device (1): Floppy
Boot Device (2): DVD
Boot Device (3): HardDisk
Boot Device (4): Not Assigned
ACPI: on
IOAPIC: on
PAE: off
Time offset: 0ms
RTC: local time
Hardw. virt.ext: on
Hardw. virt.ext exclusive: off
Nested Paging: on
Large Pages: on
VT-x VPID: on
State: powered off (since 2014-11-06T21:52:53.000000000)
Monitor count: 1
3D Acceleration: off
2D Video Acceleration: off
Teleporter Enabled: off
Teleporter Port: 0
Teleporter Address:
Teleporter Password:
Tracing Enabled: off
Allow Tracing to Access VM: off
Tracing Configuration:
Autostart Enabled: off
Autostart Delay: 0
Storage Controller Name (0): IDE
Storage Controller Type (0): PIIX4
Storage Controller Instance Number (0): 0
Storage Controller Max Port Count (0): 2
Storage Controller Port Count (0): 2
Storage Controller Bootable (0): on
Storage Controller Name (1): SATA
Storage Controller Type (1): IntelAhci
Storage Controller Instance Number (1): 0
Storage Controller Max Port Count (1): 30
Storage Controller Port Count (1): 1
Storage Controller Bootable (1): on
IDE (1, 0): C:\Program Files\Oracle\VirtualBox\VBoxGuestAdditions.iso (UUID: e4b
7db0c-2d54-48c2-bd95-580bf4aa19e3)
SATA (0, 0): C:\Users\JBadmin\VirtualBox VMs\WEC7 DEV1\WEC7 DEV1.vdi (UUID: b517
14c3-a40f-414a-a5d0-7d5b685b5d02)
NIC 1: MAC: 080027679F2C, Attachment: Bridged Interface 'Intel(R) 8257
9LM Gigabit Network Connection', Cable connected: on, Trace: off (file: none), T
ype: 82540EM, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: allow-al
l, Bandwidth group: none
NIC 2: disabled
NIC 3: disabled
NIC 4: disabled
NIC 5: disabled
NIC 6: disabled
NIC 7: disabled
NIC 8: disabled
Pointing Device: USB Tablet
Keyboard Device: PS/2 Keyboard
UART 1: disabled
UART 2: disabled
LPT 1: disabled
LPT 2: disabled
Audio: enabled (Driver: DSOUND, Controller: HDA)
Clipboard Mode: Bidirectional
Drag'n'drop Mode: Bidirectional
VRDE: disabled
USB: enabled
EHCI: enabled

USB Device Filters:

<none>

Available remote USB devices:

<none>

Currently Attached USB Devices:

<none>

Bandwidth groups: <none>

Shared folders:

Name: 'C_DRIVE', Host path: 'C:\' (machine mapping), writable

VRDE Connection: not active
Clients so far: 0

Guest:

Configured memory balloon size: 0 MB

Re: Bridged network not working

Posted: 7. Nov 2014, 00:16
by Perryg
Ok This is going to be tricky to fix because you have multiple host adapters with competing Virtualizers.

First thing to find out is if this host is part of a corporate LAN. If so then it may be you are not getting an address from the dhcp server due to restrictions.
Next if this is not on a Corp LAN I would disable the host-only adapter on the host side to make sure that it is not causing your issue.
Finally if that does not help you will need to remove the competing drivers to see if they are causing the issue.

Re: Bridged network not working

Posted: 7. Nov 2014, 16:13
by Javia1492
Perryg wrote:Ok This is going to be tricky to fix because you have multiple host adapters with competing Virtualizers.

First thing to find out is if this host is part of a corporate LAN. If so then it may be you are not getting an address from the dhcp server due to restrictions.
Next if this is not on a Corp LAN I would disable the host-only adapter on the host side to make sure that it is not causing your issue.
Finally if that does not help you will need to remove the competing drivers to see if they are causing the issue.
The host is on a corporate LAN and this LAN is only for test machines so the security is minimal so i do not think it is restricting anything from the dhcp server. To prove this, i took my personal laptop and connected it to the network via ethernet and was successfully able to obtain access to the network, HOWEVER, i had to manually specify the ip address, default gateway, and preferred/alternate dns server. I will try this on the VM and hopefully it will work.

If it does not work, i will try removing the competing drivers.

Re: Bridged network not working

Posted: 7. Nov 2014, 16:23
by Javia1492
It worked with my fix posted above, but thank you for the insight to guide me to this. Saved me from further headaches!