Opened 10 years ago
Closed 9 years ago
#12790 closed defect (fixed)
Crash at startup: VERR_INTNET_FLT_IF_NOT_FOUND
Reported by: | papin | Owned by: | |
---|---|---|---|
Component: | network | Version: | VirtualBox 4.3.8 |
Keywords: | Cc: | ||
Guest type: | Windows | Host type: | Windows |
Description
See my first post (Ticket #12787: "upg 4.3.6 -> 4.3.8 modifies VM settings") for the full story.
Host: XP Pro SP3
Guest: XP Pro SP3
Current version: 4.3.6-91406
Guest's network settings:
- Adapter 1:
- enabled
- Attached to: "NAT"
- Adapter type: "PCnet-FAST III (Am79C973)"
- Promiscuous mode: disabled (greyed out)
- Adapter 2:
- enabled
- Attached to: "Bridged Adapter"
- Name: "Intel(R) Wifi Wireless Link 4965AGN"
- Adapter type: "PCnet-FAST III (Am79C973)"
- Promiscuous mode: "Deny"
What's happening?
Upon first start of the VM right after undergoing the upgrade, the VM cannot start because VirtualBox complains about the network settings. See attachment "NAT error.png".
Steps to reproduce
- Install 4.3.8-92456 over current version (no uninstall)
- Update .vbox-extpack (menu File/Preferences)
- Start the VM
Attachments (1)
Change History (3)
by , 10 years ago
Attachment: | NAT error.png added |
---|
comment:1 by , 10 years ago
Component: | network/NAT → network |
---|
comment:2 by , 9 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Please reopen if still relevant. In that case please attach the VBox.log file as well as the output of
VBoxManage list bridgedifs
Note:
See TracTickets
for help on using tickets.
The problem is with the bridged adapter, not the NAT adapter.