VirtualBox

Ticket #14090 (closed defect: fixed)

Opened 3 years ago

Last modified 3 years ago

NATnetwork stops working => Fixed in SVN

Reported by: ReinerB Owned by:
Priority: major Component: network/NAT
Version: VirtualBox 4.3.26 Keywords:
Cc: Guest type: all
Host type: Windows

Description

I use a Win7 SP1 host. I have a total of 7 VMs configured into two different NATnetworks. It seems that, if after stopping a VM there is no VM left in one of the NATnetworks, both NATnetworks stop working, i.e. a ping to the router (usually address x.x.x.1) does no longer work.

After stopping all VMs and restarting them all works fine again.

This configuration worked without any problem in VBox 4.3.22. I did not use 4.3.24 because of the DNS problem.

Change History

comment:1 follow-up: ↓ 2 Changed 3 years ago by vushakov

  • Summary changed from NATnetwork stops working to NATnetwork stops working => Fixed in SVN

Thanks for re-filing this properly. This should have been fixed. Please, give a try to a recent testbuild.

comment:2 in reply to: ↑ 1 Changed 3 years ago by ReinerB

Replying to vushakov:

Thanks for re-filing this properly. This should have been fixed. Please, give a try to a recent testbuild.

Problem is fixed in test build 4.3.27 r99897 (on Win7 host). Thanks for fixing this so fast.

comment:3 Changed 3 years ago by frank

  • Status changed from new to closed
  • Resolution set to fixed

Fix is part of VBox 4.3.28.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use