Can't connect with bridged ethernet in 5160

R

rickgassko

Bit poster
Installed 5160 yesterday; now I can only connect in shared networking. Neither airport nor ethernet get a connection. I've tried restarting the VM OS and reinstalling Parallels Tools, but no luck. Anyone else having problems with connectivity? Any solutions?
 
No problem here. When you open the network connection window in Windows (local connection), what do you see on the Support tab? Have you tried clicking Repair?

Steve
 
The only issue that I now see with this build and networking is that after resuming Windows XP from suspension that the network adapter doesn't automatically renew a DHCP address like it appeared to in the previous build. All the old IP address information is still from my last connection...thus it doesn't work. I have to run the repair for a quick release/renew.
 
ernstcs said:
The only issue that I now see with this build and networking is that after resuming Windows XP from suspension that the network adapter doesn't automatically renew a DHCP address like it appeared to in the previous build. All the old IP address information is still from my last connection...thus it doesn't work. I have to run the repair for a quick release/renew.
Click to expand...

I do have this same problem, now that you mention it. Moving from home to work with my MBP, I still have my 192.168.0.x address from home even after I connect to the network at work.

Steve
 
Thanks for the responses. I tried Repairing the connection (no good; it said it couldn't repair it). If I restart both the Macbook Pro and the VM, it will connect with bridged ethernet, but if it gets interrupted, the MBP goes to sleep, or I switch to a different network, it loses it and can't get it back (again, unless I switch to shared Networking). I'm DHCP at home and at work. I did manually select the adapter within parallels, but Default, Ethernet, and Aiport don't get me a connection. Pretty annoying since it used to work seamlessly before installing 5160. Is there a downside to always running in "Shared" mode?
 
The downfall of Shared mode is that you cannot have the Windows show up on the network as a seperate computer (although you can access it by configuring ipfw and natd).

I like Bridged because we have a firewall at our office that is pretty comprehensive, and I really don't figure like seeting up the natd and ipfw on each and every Windows box to support the RDC and scanning, and whatever other things we get going.
 
You must log in or register to reply here.
Back
Top