The cable for Parallels NAT is connected, but...

F

Fritz

Bit poster
All of a sudden, I can't use Shared Networking. It was working fine until recently, but now I get the "no connectivity" message in WinXP network connections, and my OS X networking prefpane says, "The cable for Parallels NAT is connected, but your computer does not have an IP address and cannot connect to the Internet." I wouldn't be posting this if I didn't have an Internet connection, of course; here's a screenshot that shows my general network status.

Bridged networking works fine, but I'd rather use Shared if possible. Any ideas?

Basic stats:
WinXP SP2
Parallels Build 1970
MacBook Pro C2Duo
OS X 10.4.8
 
Fritz,

Please try restarting pvsnatd by issuing 'sudo killall -HUP pvsnatd' from OSX Terminal. Then renew IP address in XP via 'ipconfig /release' followed by 'ipconfig /renew'.
If the above doesn't help try 'sudo killall -9 pvsnatd' then 'sudo /Library/StartupItems/Parallels/pvsnatd' in OSX. And try renewing XP IP address again.
 
Same problem - but only with wireless

Okay- same problem. Performed the 'killall -HUP', pvsnatd restarted fine (new PID) and then did the release/renew cycle - nothin'. So, did the number-nine killall - again, got a new pvsnatd PID, and did the ipconfig release/renew in XP. Both times, XP chugged on trying to connect, and popped up a 'Limited or No connectivity' error. Rebooted Mac, problem persists.

Interesting thing - this is only a problem when using my wireless connection. I plugged in an ethernet cable, did *nothing* to restart the pvsnatd daemon, instead did only an ipconfig release/renew in XP, and voila - we were good. Is there some kind of bug in the NAT daemon that's causing it to misbehave only with the wireless connection?

Relevant bits:

Windows XP SP2 in VM, 512MB RAM allocated (out of 1GB RAM)
MacBook Core Duo
OS X 10.4.8, latest updates
Parallels build 1970

cheers,

--
Matt Rogers
 
You must log in or register to reply here.
Back
Top