Opened 7 years ago
Closed 15 months ago
#16789 closed defect (obsolete)
VM dropped from network because of DHCP problems
| Reported by: | boxer01 | Owned by: | |
|---|---|---|---|
| Component: | network/NAT | Version: | VirtualBox 5.1.22 |
| Keywords: | DHCP NAT | Cc: | |
| Guest type: | Windows | Host type: | Windows |
Description
I have a VM in the NAT mode. It happened only once last month, but suddenly guest network lost its internet connection. So the card and network was here, but it has this standard 169 IP address and because of this no access to internet. Only the shutdown and start of the guest helped here. As one can see from the log, it looks like VM suddenly got some problems with DHCP in my local network, where my router is a DHCP server, and lost his 10.x.x.x address. Therefore, it got an 169.x.x.x address. Both guest and host are latest Windows 10.
Attachments (1)
Change History (6)
by , 7 years ago
comment:1 by , 7 years ago
It's usually better and faster, if problems like this one (configuration, question) get first addressed in the forums (https://forums.virtualbox.org/). More than 95% of the issues are resolved over there, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of.
So, if you can, please open a new thread in the VirtualBox on Windows Hosts section.
comment:2 by , 7 years ago
You must excuse me, because I wasn‘t clear enough in my description. It isn‘t a configuration problem, it’s definitely happens only one time and this VM works correctly before and since then. I would like to be clear: I use Vbox since version 2.1 and I never had any problems with NAT. Probably some other things didn’t work quite well or were not properly configured, but not the network or NAT.
This host in particular is over 4 years old and went all the way from delivered Windows 7 x64 over Windows 8.1 to the latest Windows 10 now, with clear new install every time. And the VM itself went the same way. And as I already told, I never had such a behaviour. So I just wanted to inform the developers about it and posted the log. Maybe it isn’t something in the Vbox code, the problem could be somewhere else on the network. But I couldn’t see anything suspicious, so I simply filed the bug on the tracker.
comment:3 by , 7 years ago
That's why I said in my comment, that a one-off shouldn't be necessarily characterized as a bug. For example a similar thread was solved in the forums by simply re-installing VirtualBox.
comment:4 by , 15 months ago
This ticket could be closed because this issue hasn't come up for a long time.
comment:5 by , 15 months ago
| Resolution: | → obsolete |
|---|---|
| Status: | new → closed |
Log file