#14090 closed defect (fixed)

NATnetwork stops working => Fixed in SVN

Reported by:	Reiner Brodbeck	Owned by:
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 (3)

follow-up: 2 comment:1 by Valery Ushakov, 10 years ago

Summary:	NATnetwork stops working → 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.

in reply to: 1 comment:2 by Reiner Brodbeck, 10 years ago

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 by Frank Mehnert, 10 years ago

Resolution:	→ fixed
Status:	new → closed

Fix is part of VBox 4.3.28.

Note: See TracTickets for help on using tickets.

Download in other formats: