| 1 | | 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. |
| | 1 | 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. |
| | 2 | |
| | 3 | 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. |
