Ticket #7480 (closed defect: obsolete)

Opened 8 years ago

Last modified 3 years ago

Bridged network driver causing connectivity delay on host

Reported by: vb-fan Owned by:
Priority: major Component: network
Version: VirtualBox 3.2.8 Keywords: Host's NIC delayed start
Cc: Guest type: Windows
Host type: Windows

Description (last modified by frank) (diff)

VB bridged network driver causes connectivity delay on host, i.e after host OS restarting one has to wait 3-5 minutes (without doing anything, just waiting) till his Host's NIC gets connected. (might see forum discussion at

Change History

comment:1 follow-up: ↓ 2 Changed 8 years ago by misha

Please also specify host os windows version you are running.

comment:2 in reply to: ↑ 1 Changed 8 years ago by vb-fan

Replying to misha:

Please also specify host os windows version you are running.

MS Windows Server 2008 R2 Standard (Version 6.1.7600), my NIC is Atheros AR8121/AR8113/AR8114 PCI-E Ethernet Controller(NDIS6.20), current driver provider is Atheros Communicatons, version I have also Kerio VPN Client (64-bit) installed, earlier (before installing VirtualBox) on the host I also tried VMware workstation and later server versions (for testing, uninstalled now). Thank you.

comment:3 Changed 8 years ago by vb-fan

Important note! There is a suspicion that the problem is mainly with the hideous quality Atheros NIC and/or its drivers! At work where I have similar Atheros L1 gigabit ethernet NIC (and Virtualbox installed) today my PC just hang tightly several times (total freeze with ctrl+alt+del not working, no keyboard/mouse reaction) when a client just connected to a shared folder! And only after I replaced the NIC (with a d-link DFE-520TX) all problems gone away!

comment:4 Changed 3 years ago by frank

  • Status changed from new to closed
  • Resolution set to obsolete
  • Description modified (diff)
Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use