NAT Network crash.

Discussions related to using VirtualBox on Windows hosts.
Post Reply
Mattias
Posts: 6
Joined: 5. Apr 2015, 23:25

NAT Network crash.

Post by Mattias »

Hi, hope anyone can help! We having this error few months now.

Nat Network crash every 2 or 7 days. It's like this. We running game server on VBox 5, Host Windows 7 and guest Win Server 2003 and one of our software is for connection players to the server (Launcher - only for login to game using credentials, on server site is Gate software.). It's start like this. First this gate software crash and then stop letting players login and our launcher says is CLOSED. I'm restarting gate software manually by close it and start it again. It works few hours and then crash completely and NAT Network crash too. When we have 20+ people connected in one time NAT crashes every up to 7 days but when we having 40+ people connected in one time it crashes every 2 days. I think is because so many TCP connections in one time doing it. Please have a look on attached file, error.png.

So i wonder if we can fix it somehow. If someone know what i can do to prevent this crash of NAT Network or other thinks i can do it will be grate. Many thanks in advance.

Regards Maciej
Attachments
NAT Network error on host.
NAT Network error on host.
error.PNG (17.33 KiB) Viewed 887 times
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Mostly XP

Re: NAT Network crash.

Post by mpack »

There is no such thing as "VBox 5". When talking about crashes, please give the software version precisely.
Mattias
Posts: 6
Joined: 5. Apr 2015, 23:25

Re: NAT Network crash.

Post by Mattias »

Hi, ok

I'm using VirtualBox 5.0.4. Host is Windows 7 64 bit ultimate and guest is Windows server 2003 32 bit enterprise edition.
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Mostly XP

Re: NAT Network crash.

Post by mpack »

Well, the current release is v5.0.8 - perhaps you should test with that and report back. If you still get the crash then the best thing would be to raise a BugTracker ticket.
Post Reply