VirtualBox

Opened 9 years ago

Last modified 9 years ago

#13947 new defect

bridged networking broken for Windows 8.1 guest

Reported by: nbi Owned by:
Component: network Version: VirtualBox 4.3.24
Keywords: Windows 8.1 guest bridged network Cc: pete.in.IL@…
Guest type: Windows Host type: Linux

Description

The windows 8.1 guest diagnostics don't see a problem with the bridged connection, but web browsers are unable to connect to any URL. If the adapter (Intel Pro 1000 desktop) is set to NAT in the Linux host then the connection is ok (browsers are able to connect). This problem also existed for version 4.3.18. Windows 7 guests do not have this problem.

Attachments (1)

VBoxSVC.log (1.9 KB ) - added by nbi 9 years ago.

Download all attachments as: .zip

Change History (5)

by nbi, 9 years ago

Attachment: VBoxSVC.log added

comment:1 by Frank Mehnert, 9 years ago

This is most likely not a VirtualBox bug. When you do bridged networking, did your guest receive an IP? Check this with

/sbin/ifconfig -a

comment:2 by nbi, 9 years ago

I assign (no DHCP) the IP in the guest since I want the guest to be a member of my local network. As I said the Win 8.1 diagnostics think all is good (with the assigned IP) and this works flawlessly under Win 7.

BTW, it doesn't even make sense to discuss DHCP with "bridged" networking. How would the DHCP server answering the guest's IP request know what addresses on the local network are already taken?

Answering my question I guess the local network's DHCP server would assign the guest IP. But that doesn't apply to me because all addresses are static IPs.

Last edited 9 years ago by nbi (previous) (diff)

comment:3 by Frank Mehnert, 9 years ago

Your understanding of DHCP with bridged networking is apparently not correct. The guest would get a DHCP lease from the same DHCP server as your host. So if your host is able to get an IP from the DHCP server, your guest will be able as well. With bridged networking, both host and guest are attached to the same network. Of course, if your host has a static IP then you need to set up a static IP to your guest as well.

I still think it's a configuration issue of your guest.

comment:4 by nbi, 9 years ago

Lets not jump to conclusions about what I know. I'm perfectly aware of what bridged networking is. That I haven't used DHCP in aeons is beside the point. Perhaps you need to forward this ticket to someone who understands guest configuration especially with regards to Win 8.1. As I have already explained (more than once) this setup works flawlessly with a Win 7 guest. So the onus is on you folks to clarify what the configuration differences are for a Win 8.1 guest. Nothing in the VirtualBox documentation indicates that a Win 8.1 guest needs any different and/or additional configuration steps from any other guest OS type that has functional bridged networking for a static guest IP.

If there are specific debugging/logging actions you'd like me to perform I'm all for it. But just telling me you think it's a guest configuration issue in light of evidence to the contrary is not helpful. Either point me to the documentation that shows me something new with regards to Win 8.1 or give me a troubleshooting recipe for zeroing in on the problem. Thank you.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use