Opened 16 years ago
Closed 16 years ago
#4697 closed defect (worksforme)
After upgrade to 3.0.4 bridged networking no longer can connect
Reported by: | Dovber Shapiro | Owned by: | |
---|---|---|---|
Component: | network | Version: | VirtualBox 3.0.4 |
Keywords: | bridged networking | Cc: | |
Guest type: | Windows | Host type: | Linux |
Description
Host: Jaunty 2.6.28-13-generic #45-Ubuntu SMP Tue Jun 30 22:12:12 UTC 2009 x86_64 GNU/Linux Guest: winxp Bridged networking with a static IP using PCnet-FAST III bridged to eth0 I had this setup working for a while on older versions of VirtualBox, but since I upgraded to 3.0.4 the network is broken. everything looks normal in windows but I cannot ping anywhere or connect to anything. I tried changing to Intel NIC drivers, but it did not help
Attachments (1)
Change History (5)
by , 16 years ago
Attachment: | BH1799-2009-08-05-18-04-25.log added |
---|
comment:2 by , 16 years ago
Replying to frank:
Which was the previous VBox version you tested?
I was working on 2.2.4 and 3.0.2. I upgraded to 3.0.4 yesterday and then the networking stopeed working
comment:3 by , 16 years ago
Replying to dovshap:
Host: Jaunty 2.6.28-13-generic #45-Ubuntu SMP Tue Jun 30 22:12:12 UTC 2009 x86_64 GNU/Linux Guest: winxp Bridged networking with a static IP using PCnet-FAST III bridged to eth0 I had this setup working for a while on older versions of VirtualBox, but since I upgraded to 3.0.4 the network is broken. everything looks normal in windows but I cannot ping anywhere or connect to anything. I tried changing to Intel NIC drivers, but it did not help
Close this ticket. The issue was with the network in my office. The network team put in a setting to only allow one mac address per switch port which was why I could not connect with a bridged network
comment:4 by , 16 years ago
Resolution: | → worksforme |
---|---|
Status: | new → closed |
Thank you for the feedback!
vbox.log