VirtualBox

Ticket #8577 (closed defect: invalid)

Opened 3 years ago

Last modified 3 years ago

Network stops working XP (guest) on MacOSX (host)

Reported by: OxOOCOFFEE Owned by:
Priority: major Component: network/NAT
Version: VirtualBox 4.0.4 Keywords:
Cc: Guest type: Windows
Host type: Mac OS X

Description

This is a clean install of vbox 4.0.4 on MacOSX (fresh installed). After some time working I am trying to check my source in with svn from Windows XP SP3 with all updates and guest tools installed. Networking works just fine on host (MacOSX). So guest restart only fixes this problem for some time. I am configured with NAT to airport (eth1). One thing perhaps it might be that I think of it is that sometimes switch between Access Points without shutting down guest and it has problem after host reconnect to new AP? I am attaching my log.

Attachments

VBox.log Download (74.4 KB) - added by OxOOCOFFEE 3 years ago.

Change History

Changed 3 years ago by OxOOCOFFEE

comment:1 Changed 3 years ago by OxOOCOFFEE

I have more updates. It is definitly a problem with switching AP. Here is what I tested

  1. Connected to office AP
  2. Started XP guest (in NAT mode connected to AirPort eth1)
  3. Ping www.google.com from host and guest (it all works)
  4. Closed lid (sleep) while guest ir running and waited couple of minutes
  5. Logged back to Mac with the same AP (host and guest still can ping)
  6. Closed lid (sleep) and turned of AP. Waited couple of minutes.
  7. Connected AP gave few sec to boot and logged back to mac. Guest and Host still can ping.
  8. Closed lid (sleep) turned off AP and started a different portable AP miniWIFI from different vendor.
  9. Logged back to Mac while original AP is down and auto connected to miniWIFI.
  10. Host can ping and Guest CAN NOT ping.
  11. Closed lid and turned off miniWIFI and started original AP. Waited few min
  12. Logged back to Mac and auto connected to initial AP. Can ping from guest and host.

This was all done without shutting down guest XP.

comment:2 Changed 3 years ago by Hachiman

Does

# ipconfig /release
# ipconfig /renew

solve issue for you?

comment:3 Changed 3 years ago by OxOOCOFFEE

Here is little more info. Doing ipconfig /release followed with /renew does the trick. I wish VB guest tools network could detect this and do it automatically.. if all posible.

comment:4 Changed 3 years ago by Hachiman

  • Status changed from new to closed
  • Resolution set to invalid

Thanks for feedback. The most of operating systems do this automatically, in order to resolve networking problems. So it isn't really required to handle this case on NAT side.

comment:5 follow-up: ↓ 6 Changed 3 years ago by OxOOCOFFEE

So if this is not NAT problem on host side, would this be possible to detect and automatically do on guest side? Guest tools/network driver? Just wondering. I think quite few people move around between AP as I do and "loosing connection is little confusing". I understand that release renew works but it would be much better if this could be done automatically if all possible? Is there a technical reason thatvthis can't be done? Is it up to OS to handle this? Or possible to do in driver? Should this be moved as "enhancement" to guest tools / networking instead of just closing it? Thank you

comment:6 in reply to: ↑ 5 Changed 3 years ago by Hachiman

Replying to OxOOCOFFEE:

So if this is not NAT problem on host side, would this be possible to detect and automatically do on guest side?

Usually guests do it with out additional interaction with user, unfortunately win XP is not one of them.

Guest tools/network driver? Just wondering. I think quite few people move around between AP as I do and "loosing connection is little confusing". I understand that release renew works but it would be much better if this could be done automatically if all possible? Is there a technical reason thatvthis can't be done?

It is possible but increases host dependendent part for nothing, because the most of the guest will do release/renew automatically. Even after reacting on host side on adapter change, we need enforce guest to update dhcp operation. Modifying guest side for this isn't an option, because whole idea of NAT is avoiding host/guest modifications as much as possible.

Is it up to OS to handle this? Or possible to do in driver? Should this be moved as "enhancement" to guest tools / networking instead of just closing it?

It possible of course, but I thing it won't be done, because of reasons mentioned above.

Thank you

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use