I have an XP SP2 VM that has no network problems when I have Airport switched on on the OSX side. When I switch Airport off, and plug in a wired Ethernet connection, OSX can still access the net and everything is normal. But the XP machine is different. Here's what it does: Retrieves a valid IP, DNS, and gateway addresses Can ping the OSX IP Cannot ping the router Cannot ping anything else, either I need to used a wired Ethernet to access a VPN so I have to get this working. I'm pretty sure it was working under a previous build of Parallels. Can anyone help me diagnose this issue, or provide a solution?! Thanks, D
Looks like I needed to turn "Shared Networking" on, as detailed in this other thread. I've no idea why that works, but it does! Hurrah!
You found a networking bug in Parallels Desktop This is the same networking bug that several of the users I assist have found. It's an intermittent problem, so I haven't been able to figure out the exact trigger for it so I haven't filed a bug report. Basically, if Parallels is running when you switch from AirPort <-> Ethernet, there is a chance that this bug will get triggered. Once it does, the only recourse I have found is to reboot Mac OS X. Somehow, the network driver that Parallels uses to get "direct" access to the network gets confused and won't reset itself. You can avoid the problem by using "Shared networking" or always saving your virtual machine and quitting Parallels before changing your network connection. In our case, we need the virtual machine to have direct network access, so it's a matter of suspending the virtual machines whenever the user needs to change network connections. Steve
