How to open port forwarding on virtualbox(part 2)?

Discussions related to using VirtualBox on Linux hosts.
Post Reply
hien82
Posts: 6
Joined: 8. Apr 2016, 14:38

How to open port forwarding on virtualbox(part 2)?

Post by hien82 »

I do like you said, choice bridge adapter, but so what is this; http://imgur.com/a/mo0qj , what is this problem? are you help me wrong? And one more thing: in linksys router page, "to IP address" it have 192.168.1.(...). But I also try "host only adapter" and terminal have this IP: 192.168.59.101, so , can anybody tell me what is my problem.
hien82
Posts: 6
Joined: 8. Apr 2016, 14:38

Re: How to open port forwarding on virtualbox(part 2)?

Post by hien82 »

need help fast, please.
socratis
Site Moderator
Posts: 27329
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: How to open port forwarding on virtualbox(part 2)?

Post by socratis »

  1. You should not have started a new thread. It is definitely a continuation of the previous one.
  2. Again, you uploaded your image on a 3rd party site. Next time, personally, I will ignore it.
hien82 wrote:are you help me wrong?
No, I'm not. You have a different problem. Your problem now is that you're getting the "VERR_INTNET_FLT_IF_NOT_FOUND". I do not have Windows myself, but from a quick search that I did, I found that there is a "workaround":
superuser.com wrote:I had exactly the same problem as you, tried everything, but the solution is really easy:

1. Open network center
2. Change adapter settings
3. Right click your Virtualbox host-only adapter and select Properties
4. Enable "Virtualbox NDIS6 Bridget Networking Driver" (if it's disabled - if it's not, see next)

If the checkbox in step 4 was disabled, VB should work just fine now (no reboot needed). Otherwise repeat steps 3-4 for every network adapter you have (Ethernet, WiFi...) and always uncheck the NDIS6 checkbox -> apply -> check it again -> apply.

Hope this helps - worked for me on 2 different machines (it seems that this is caused by last Windows 10 update - thanks Microsoft for wasting another 4 hours of my life).
I'm not sure if it is going to work or not. But several users have reported success with that.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Post Reply