virtualbox.org

Hello dear community,
I would be grateful for help.
I have Windows 11 on host machine and Windows 11 on guest VM.
In the VM Network settings Adapter 1 Attached to NAT Internet connection is not always stable when enabled NAT.
In my work I use cloud services such as Google Drive via Air Explorer application.
I can't upload large files to cloud services, I get an error message:
"Error: Cannot write data to transport connection: The remote host forcibly terminated the existing connection."

When Adapter 1 Attached to Briged adapter Internet connection is fully stable.
I have no any error messages.

But I need to use NAT.

Please help with connection stability using NAT
Thanks

What version of Virtualbox are you using?

I have a problem that might be related. Loading a specific website will stop in the middle. For example if I load an image (URL ends with .png), it will show up to third or half, then stop. The progress indicator spins, but it never finishes. Tried different browsers (FF, IE, old version of FF). Or sometimes it won't load at all, just spinning.
Other websites work fine.
That specific website works fine from other hosts including the VM host.
I updated the Guest Additions, rebooted the guest VM, no improvement.

Guest OS is Windows Server 2012R2 64 bit
virtualbox 6.1.38 (no extenstion pack)
Host OS : Windows 10 Pro 21H2 64 bit

This worked before and recently I updated VB from 6.1.36 to 6.1.38, so I wonder if this is some kind of regression?

xerces8foo wrote: Other websites work fine.

Then it sounds like a problem with that website, or a problem with some server on the route.

What happens when you use the host browser?

mpack wrote: What happens when you use the host browser?

I already wrote: That specific website works fine from other hosts including the VM host.

The website is not public.

xerces8foo wrote:This worked before and recently I updated VB from 6.1.36 to 6.1.38

xerces8foo, if you revert to 6.1.36 and the network activity returns to normal function, then upgrade back to 6.1.38 and the problem returns, then there is a Virtualbox problem. We would need a 6.1.36 log with the working service, and a 6.1.38 log with the failure.

CyanCetus wrote:Internet connection is not always stable when enabled NAT. ... Attached to Briged adapter Internet connection is fully stable.

CyanCetus, we would also need two logs, one with NAT and failing, the other with Bridged working.

For both parties, please provide each log in this fashion:

* Change the network or Virtualbox version as needed. If you change versions, please reboot the host.

* Start the VM from full normal shutdown, not save-state. Run until you see the problem happen, then shut down the VM from within the VM's OS if possible. If not possible, close the Virtualbox window for the VM with the Power Off option set.

* Right-click the VM in the main Virtualbox window's VM list, choose Show Log. Save the far left tab's log, zip it, and post the zip file, using the forum's Upload Attachment tab.

CyanCetus wrote:cloud services such as Google Drive via Air Explorer application

"Air Explorer" is a 3rd-party app, according to my web-search. What happens when you use basic good ol' Windows File Explorer? Can you upload successfully on NAT then?

scottgus1 wrote: * Change the network or Virtualbox version as needed. If you change versions, please reboot the host.

Because of some other things I encountered this comment on the forum:
VirtualBox upgrades do NOT require a reboot. (in bold and red color)

So why you suggest a reboot? Just in case?

I did tests with VB 6.1.36 and 6.1.38 and did not find anything conclusive.

The problematic website is pretty flaky, no matter from where it is accessed.

It works best on the host.
In VM, it works in IE, although with many hiccups, sometimes nothing loads, then it works fine for a while.
Firefox in VM seems to be even worse, but it also starts working every now and then.

The host uses a VPN, over which the website is located.

So basically it is many factors and hard to point at the root cause.

Anyway, it seems VB version has no effect on the problem, so this case is closed.

xerces8foo, Thanks for trying the tests!

xerces8foo wrote:Because of some other things I encountered this comment on the forum:
VirtualBox upgrades do NOT require a reboot. (in bold and red color)

So why you suggest a reboot

It sets a clear playing field for testing purposes, ensuring that nothing has been left running that's not supposed to be.
Also, a reboot is recommended when downgrading.