Opened 14 years ago
Last modified 9 years ago
#8239 closed defect
Virtualbox on multiple computers breaks name resolution — at Initial Version
| Reported by: | B Lloyd | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 4.0.2 |
| Keywords: | Cc: | ||
| Guest type: | other | Host type: | Windows |
Description
When installing virtualbox on multiple computers, a name lookup from a command such as "ping HISCOMPUTER" will start to fail on an ad-hoc (home) style network.
The problem is that when doing a name lookup, the computer broadcasts a search for the name. When it recieves a response from the other computer, the response includes all addresses for the machine. 192.168.56.1 is used by VirtualBox for the Host Network only adapter. Both computers will thus have an address of 192.168.56.1. A hop to your own address will always be the cheapest, so the name resolves to the 192.168.56.1. Thus the computers stop talking.
This is a problem with how networking works, but is exacerbated by the virtual networking component. The only solution I can see is to not use the same address for the two disconnected networks. Changing the address pool in one of them does fix the problem. However, Virtualbox in a fresh install shouldn't break existing networking.
This affects 2.X, 3.X, and 4.X clients. You don't even need to have a guest running to experience this.
