Second host-only network stuck on 169.254.x.y

Discussions related to using VirtualBox on Windows hosts.

Second host-only network stuck on 169.254.x.y

Postby Ken Hagan » 31. Oct 2012, 13:00

In 4.2.2 (and now also in 4.2.4), if I create a second host-only adapter and try to set the IP address to 192.168.x.y then VirtualBox ignores me. When I reboot the machine, there is a two-minute delay and I find that the adapter has been given an APIPA address that I cannot change. Equally, if I select the adapter in Windows' Control Panel (the host is Server 2008 R2) and try to change IPv4 settings there, I can type in the values but the adapter remains resolutely stuck on the 169.254.x.y. address.

(I believe APIPA is not recommended for multi-homed hosts, so there's some irony in this bug only kicking in for the second adapter. :D )

This all worked in every version up to 4.2.0 (which I have stuck with for now).
Ken Hagan
 
Posts: 40
Joined: 1. Oct 2009, 17:42
Location: UK
Primary OS: Debian other
VBox Version: PUEL
Guest OSses: Windows (various)

Re: Second host-only network stuck on 169.254.x.y

Postby Perryg » 31. Oct 2012, 14:32

These kinds of problems that are reproducible should be reported to bugtracker. If you have not signed on to Bugtracker before you will need to select a new Nickname to be able to report issues.
It would also help if you can post the ticket number here so other can see the progress, add information, or see the final results.
Perryg
Site Moderator
 
Posts: 25964
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX - Other

Re: Second host-only network stuck on 169.254.x.y

Postby Ken Hagan » 31. Oct 2012, 21:47

Ken Hagan
 
Posts: 40
Joined: 1. Oct 2009, 17:42
Location: UK
Primary OS: Debian other
VBox Version: PUEL
Guest OSses: Windows (various)


Return to VirtualBox on Windows Hosts

Who is online

Users browsing this forum: Nielas Aran and 54 guests