Opened 13 years ago
Last modified 9 years ago
#8512 closed defect
Host-Only Network Problems After Upgrade — at Initial Version
| Reported by: | galesteven | Owned by: | |
|---|---|---|---|
| Component: | network/hostif | Version: | VirtualBox 4.0.4 |
| Keywords: | Cc: | ||
| Guest type: | other | Host type: | Windows |
Description
Host: Windows-7 64-bit Guest: Oracle Linux
I configured 2 network interfaces to my guest: NAT and Host-Only using VirtualBox 4.0. The Host-Only has a static IP for both the Host (192.168.56.1) and the Guest (192.168.56.101).
It worked like a charm.
Then I Upgraded from VB 4.0 to 4.0.4.
My network set-up before upgrading had a Host-Only adapter with IP=192.168.56.1 and Mask=255.255.255.0. After upgrading this changed to IP=169.254.208.136 and Mask=255.255.0.0.
I tried to change the Host-Only settings back the pre-upgrade values via File->Preferences->Network. It appears to work. It popped-up the security warning which I ok'ed. But it didn't REALLY change the IP config. The Windows "ipconfig" command displays the wrong IP and Mask. Pinging my guest also fails with "Destination host unreachable"
Then I started VirtualBox running "as Administrator" and tried to change the Host-Only IP configuration via File->Preferences->Network. This time it also appeared to work, but the Windows "ipconfig" command displays the wrong IP and Mask. Pinging my guest also fails with "Destination host unreachable".
So I do not believe that this is a Windows Security problem.
Each time restart Virtual Box and check the IP settings in File->Preferences->Network, I see that the Host-Only configuration reverted back to the wrong IP and Mask!
