re-initiate NAT on Network switch(Reopen issue)

[liamblack]

Could someone reopen the following issue or explain a fix? https://www.virtualbox.org/ticket/3847
I tried several of the commands but they don't work.
INCLUSIVE EDIT:
I'm on a Windows 7 host and I have tried both a Linux and Windows guest.
So basically if you switch wifi networks(or ethernet) the guest internet goes down with no way to bring it back up.
I tried setting both of the following commands inclusively and individually with no change to the Virtual Machine(including restarting both the host and guest).

VBoxManage setextradata "Windows" "VBoxInternal/Devices/pcnet/0/LUN#0/Config/UseHostResolver" 1
VBoxManage setextradata "Windows" "VBoxInternal/Devices/pcnet/0/LUN#0/Config/DNSProxy" 1

Also disabling and renabling NAT doesn't work either.

VBoxManage controlvm "GUESTNAME" nic1 null
VBoxManage controlvm "GUESTNAME" nic1 nat

Also the following also fail to renew the ip address linux I believe is( ifconfig eth0 down; ifconfig eth0 up;/etc/init.d/networking restart)

ipconfig /release
ipconfig /renew

Lastly I tried disabling/enabling the host network adapter but the guest OS still doesn't come back up.

[mpack]

Not unless you can expand on "don't work". We don't normally respond to that kind of non report.

[liamblack]

@mpack Although I appreciate your response, you must have simply not run into the issue otherwise I think you would agree that the following commands "don't work."
Change wifi networks(or ethernet networks) and the internet goes down with no way to bring it back up without a restart.

I tried setting both of the following commands with no change to the Virtual Machine(including restarting both the host and guest).

VBoxManage setextradata "Windows" "VBoxInternal/Devices/pcnet/0/LUN#0/Config/UseHostResolver" 1
VBoxManage setextradata "Windows" "VBoxInternal/Devices/pcnet/0/LUN#0/Config/DNSProxy" 1

Also disabling and renabling NAT doesn't work either.

VBoxManage controlvm "GUESTNAME" nic1 null
VBoxManage controlvm "GUESTNAME" nic1 nat

Also the following also fail to renew the ip address.

ipconfig /release
ipconfig /renew

The only thing I did not try was the pre release but technically it is older then the current VB 5.
Again the problem doesn't exist in VMWare and only exists when switching between wifi(or ethernet) networks.
A fix should be well publicized and clear otherwise the issue should still be open.

[scottgus1]

Liam, the last post in the linked ticket was four years ago. And there was a little static on the end of the ticket. If I were you and I felt the issue exists again, I would make a new ticket on the Bugtracker referring to the ticket you posted, post my logs and ask the developers what they think. Be specific about what doesn't work, as in error messages that occur if any, and exactly what is not operating properly. For example, when the issue pops up can you get to Google's webpage by entering "74.125.224.72" in the address bar (that's one of Google's IP addresses) but not "www.google.com"? Things like that.

One quick thought, I assume you tried "unplugging the cable" on the NAT NIC in the guest, disabling/enabling the host network adapter, disabling/enabling the guest NIC within the guest, etc.?

[liamblack]

Scott, All internet access is broken not just 'wget google.com'. Ip addresses don't work either.

"there was a little static on the end of the ticket" I'm not sure what you mean by this.

Again to reproduce bug boot VirtalBox while connected to Wifi network and then switch to a new wifi network.

Once you have switched wifi networks the internet goes down in the guest os.
To my knowledge I have tried "unplugging the cable" on the NAT NIC in the guest( ifconfig eth0 down; ifconfig eth0 up;/etc/init.d/networking restart), disabling/enabling the host network adapter(I tried this with in host of Windows), disabling/enabling the guest NIC within the guest(I also tried VBoxManage controlvm "GUESTNAME" nic1 null).

[scottgus1]

"there was a little static on the end of the ticket" meant that when one reads the last few posts on the ticket which came in four years ago, the developers decided that the poster's info did not have anything to do with the ticket. The ticket is really 5 years old, then.

Good you did some experiments with disabling & re-enabling NICs, too bad they didn't work. By "unplugging the cable" I am suggesting trying to go to the Virtualbox guest's toolbar, choose Devices, then Network Adapters, then the Advanced dropdown triangle, then uncheck "cable connected" for 10 seconds or so while the guest OS recognizes that the network is disconnected, then check "cable connected" again and see what the guest OS does.

If this last test doesn't work, then you'll need to make a new ticket on the bugtracker as I suggested above. Even if we did find that your issue occurred on our Wi-Fi-connected hosts, we would not know how to fix Virtualbox to make the issue disappear - only the devs can do that, and you'll have to tell them on the bugtracker to get them to look into it.

[loukingjr]

FWIW, on a OSX host and a Windows 7 guest, changing the WiFi network does indeed disconnect the guest however, after a few seconds the guest reconnects. VB 5.0.10.

Also an XP guest, Linux guest, etc.

[liamblack]

I'm on a Windows 7 host and I have tried both a Linux and Windows guest.

[loukingjr]

Ok. Tried with Windows 10 host and Windows 7 and Linux Mint 17.2 guests. Same results as my OSX host. No problem reconnecting switching WiFi networks.

[liamblack]

Is posting a video and logs a valid way to show the bug exists?
It appears no one else it reproducing the bug.

[liamblack]

Bump.

Is posting a video and logs a valid way to show the bug exists?
It appears no one else it reproducing the bug.

[mpack]

If you have a way to reproduce your problem then create a BugTracker ticket for it, with all relevant supporting data - which would include a log.

[snowboardguy711]

Was there any resolution to this request. I'm running into the same problem. Linux host version 4.4.5 kernel. Rhel 6.X guests. Laptop works fine. Switch to a network, then dns stops working. I did enable --natdnshostresolver1 on for the virtual machine. Any help would be appreciated.