Occasionally Losing networking in Windows XP

I'm running Parallels 1970 and Windows XP, I've got Bridged Ethernet; Default Adapter as my choice.

I switch between an ethernet cable network connection, sometimes to a wireless connection, then to a different ethernet cable network connection on a different subnet. This'll all work fine and DHCP will get a new IP every time and then every 5th time or so it won't. And when it stops working, no amount of fiddling can fix it. I can manually set all the Windows networking IP addresses and gateways to no avail. Quitting and restarting Parallels and WinXP doesn't help matters, can't ping the gateway, can't get out to anywhere. (The Mac OSX is always fine, and is happily chatting away to the internet...)

The only solution is to restart the entire Mac. After doing this, everything will come right up in WinXP. So... the problem must be somewhere on the Mac, having to do with the TCP/IP for Parallels... But where? How?

Is there some Parallels networking app or daemon on the Mac that is running even where Parallels isn't, which I need to restart or something?

 

Hi there,

I might have a similar problem here. Yesterday I had clicked on "My Network Connections" in Parallels on my XP Pro VM. All three of my other computers showed up initially, but then they disappeared and I still don't have access to them. I have re-booted XP, closed it down, re-installed the Network Connection. I have the default Bridged Ethernet. I also totally exited from my Intel Core Duo iMac, shut it and all the other three computers off and then restarted everything. Restarted Parallels and still no network connections. I can access the internet and e-mail just fine on any computer, the VM or iMac. However, when the connections disappeared I lost the internet as well which is why everything was then shut down and restarted. Proper procedure was followed. I use LAN connections on this home network.

In addition to all this I can no longer connect my iMac on Tiger 10.4.8 to any computer.

Does anyone have ideas as to what has happened and how I can resolve it? This is puzzling but also a nuisance as I need to access files occasionally on one of the other computers. One computer is running XP Home and the other has Windows Millennium. All had been happily linked until this sudden disappearance. By the way I'm using Parallels Desktop for Mac, 1970. I haven't upgraded to 3150 yet as I was waiting for it to be the final release. Would it help to try RC2?

Thanks in advance.

Lynn

 

this seems to be a similar issue i'm having but not identical.

i have no networking available when switching between wifi access points.

example, at home wifi AP, parallels winxp pro VM is installed, configured properly with full bridged networking (with default settings) working and the ability to use IE to access my hospital's radiology imaging (it has to be IE) over the internet. when i close & sleep the macbook, go to work and open, the mac os wifi connects as usual to the hospital AP, but the parallels win xp refuses to connect via the bridge connection and there is no network/internet access from within parallels win xp. nothing i have done within the windows networking configs have resolved the IP address, running network setup wizard, rebooting the winxp VM, even manually setting the IP, DNS & subnet. when i go home and run parallels win xp VM at home again, it connects just fine as it did originally.

it seems to just refuse to get an IP address assigned via the bridge connection to the network/internet unless it is on the network it was setup in.

i hope i made this clear, but please feel free to ask more details if i i did not.

admittedly, i haven't just shut down the macbook, booted at the hospital and then started parallels to see if this corrects the issue, but that is a huge pain as i never shut down the macbook, i just put it to sleep. i am going to shut down the macbook before i go to work next to see if i can connect and that resolves the issue, but if i could figure out how to keep from having to do that, i would be grateful.

*******
macbook 2.0ghz, 2.0gb ram, mac os x 10.4.8
parallels 3150, win xp pro 512mb ram, with default settings otherwise.

 

gkrodg00, your issue does indeed sound similar.

For anyone else reading this thread and thinking they can help pinpoint the issue, here's a little more information:

I was connected to 172.xx.xx.xx with ethernet. Then I connected to 192.xx.xx.xx via airport. Finally I connected to the same 192.xx.xx.xx via ethernet. At this point, I can't ping the gateway from XP, 192.xx.xx.1. But I _can_ ping the mac's IP address from XP. Since at this location I have access to both the wireless and cabled connection, I switched the mac networking to the airport 192. I could then ping the gateway, and get out to the internet, and all's fine (the Mac got a new IP on the 192 net). But when I try to go back to the cable connection (which is typically more reliable) I can again no longer ping the gateway (yet another new IP for the Mac). XP _can_ it appears talk to the DHCP server in either case. All the IP settings look fine on XP, but there's no getting to the gateway. Quitting and restarting parallels doesn't help, but rebooting the whole Mac does.

Note the symptoms are the same with Solaris as well. I can renew the DHCP successfully, but can't get to the gateway with the ethernet, but can get to the gateway with airport.

 

Can you not use Shared Networking?

 

that would be my solution too.. you'll not need to change the ip of the XP vm then.

 

I don't think I can use shared networking because I make connections to the IP of my XP Parallels instance via Remote Desktop, or I ssh into my Solaris install, both sometimes from machines external to my Mac. Correct me if I'm wrong about how shared networking works.

 

ok.. so in bridged mode, did you say that when you have this issue with networking not working, your machine does still get an address form the dhcp server ?

Could be an ARP issue... try clearing windows ARP cache with

arp -d *

 

That's right.

OK, I'll try that next time it happens. (I can't reproduce the problem at will... switching the Mac back and forth between airport and ethernet after a Mac reboot creates no problems for XP.)

I can't help feeling that the problem is on the Mac side, because both Solaris and XP experience the problem the same way. But we'll see if clearing the ARP cache helps.

 

Clearing the ARP cache didn't help my similar problem:

http://forums.parallels.com/thread8938.html

I get an IP, but I can't do anything with the network.

Steve

 

Cleared the ARP cache, no luck. still can't ping gateway, or ping another machine on the LAN. I can ping the Mac and myself (Parallels XP) and the Parallels Solaris IP. (Solaris does the same: can ping XP, the Mac, itself, but not the gateway or another machine on the LAN)

Alright, gotta go shutdown solaris, shutdown XP, and reboot the Mac to get networking back...

(Of course all this time the Mac is just fine, and can ping the outside world, gateway, etc.)

 

I have the same problem (under RC3).

Windows ARP is not the problem. Rebooting Windows or even exiting and re-starting Parallels does not work. Only rebooting the Mac will fix it. The Issue appears to be something that Parallels does to the virtual adapters it creates for OS X.

Does anyone know if the problem is still there in 3170 (RC3)?

 

I've had this problem for quite a while now and it is still present in RC3

 

Same Problem...Parallels Can't Connect to Network

For some reason, under RC3, I am now having a similar networking problem. On the Mac side, my network works fine. On Windows, under Parallels, the Windows VM can't even get an IP address.

This just started happening for me.

I rebooted the Mac, rebooted the VM, nothing works as far as networking on the Windows side under Parallels.

I took all the Parallels defaults for network setup, so whatever the defaults are, they worked fine for me from the time Parallels came out until now.

Any suggestions would be appreciated.

 

I've used every public beta of Parallels Desktop for Mac since before the first release. And every single release has had this same issue. Don't hold your breath.