Opened 16 years ago
Closed 16 years ago
#2433 closed defect (fixed)
VirtualBox crashes randomly when using port forwarding -> retry with 2.1.4
Reported by: | Luke Franklin | Owned by: | |
---|---|---|---|
Component: | network/NAT | Version: | VirtualBox 2.0.2 |
Keywords: | Port Forwarding, Crashes, SME Server | Cc: | |
Guest type: | Linux | Host type: | Windows |
Description
I have SME server 7.3 configured as a guest on VirtualBox with a Vista host, I have setup port forwarding with NAT as follows:
Port 3873(TCP) from Vista to port 80 on SME server. Port 2222(TCP) from Vista to port 22 on SME server.
When I first started SME server after setting up the port forwarding everything seemed fine, the ports were being forwarded as intended until...the entire VirtualBox application crashed, nothing worked, none of the other guests, the VirtualBox main application window won't open or close (if it's already open), the whole VirtualBox application is unresponsive but is consuming lot's of CPU. I tried closing it through the task manager, this only closes the windows but one instance of VirtualBox won't close and when I try to reopen the VirtualBox application it doesn't let me, I have to log out or restart Vista to get things working again!
I have tried it several times, SME server will work fine for maybe half an hour then crashes randomly, it doesn't matter what I'm doing.
This only started when I set port forwarding and it must have something to do with it.
My Vista computer connects to the router through wireless LAN then to the internet, could it be a problem with it dropping out? I didn't notice it drop out at the time and it doesn't drop very often at all.
Attachments (1)
Change History (5)
by , 16 years ago
Attachment: | SME Server 7.3-2008-10-15-21-20-28.log added |
---|
comment:1 by , 16 years ago
Component: | network → network/NAT |
---|
comment:3 by , 16 years ago
Summary: | VirtualBox crashes randomly when using port forwarding → VirtualBox crashes randomly when using port forwarding -> retry with 2.1.4 |
---|
comment:4 by , 16 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
No response so I suppose this bug is fixed in 2.1.4. Closing.
VirtualBox Log