VirtualBox

Opened 15 years ago

Closed 15 years ago

#4122 closed defect (fixed)

Networking doesn't work at all on Windows 7 RC1 x64 Host.

Reported by: Znuff Owned by:
Component: network Version: VirtualBox 2.2.2
Keywords: networking, bridged driver, windows 7, x64, rc1 Cc:
Guest type: other Host type: Windows

Description

The Internal Networking doesn't work at all.

NAT doesn't work at all.

Bridging doesn't work at all.

Also, the "VirtualBox Bridged Networking Driver" causes the system to lose network conectivity completely. The adapter(s) that have that driver enabled are reported in Win7 just as being "Enabled". There's no DHCP request and no activity at all. (See Screenshot1).

Disabling the "VirtualBox Bridged Networking Driver" makes the networking on the host system work again.

Attachments (1)

QShot_0119.jpg (87.5 KB ) - added by Znuff 15 years ago.
Screenshot1

Download all attachments as: .zip

Change History (3)

by Znuff, 15 years ago

Attachment: QShot_0119.jpg added

Screenshot1

comment:1 by Andy, 15 years ago

I also have problem with networking at a Windows 7 RC x64 host running VirtualBox 2.2.4.

My problem is that DHCP often doesn't work - especially on bridged interfaces. Sometimes I get the IP/mask and gateway, but no DNS - other times I get nothing.

I believe it also sometimes doesn't work with NAT-et interface, but it seems more stable than bridged.

comment:2 by Frank Mehnert, 15 years ago

Resolution: fixed
Status: newclosed

Please reopen or better if these problems persist with VBox 3.0.8 or better open separate tickets. At least NAT should work in every case, as well as internal network. I have to ask this: Did you really understand how the internal network works?

Apart from this, VBox 3.0.8 fixed a bug in the PCNet device emulation which could be related as well.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use