We are testing PD4 on a couple of MacBook Pros. Everything seems great except for Bridge Network via Ethernet. The Mac side gets and IP but the Windows XP side get a self-assigned IP. If I downgrade back to PD3, the Bridge Network via Ethernet works fine. Any ideas?.. we would definately like to make PD4 work and it "critical" that Bridge network via ethernet work before upgrading entire company. We are a pretty big company 30,000+ employees with a mixture of mac and pc on our network. Just a background on our network. we do implement port security meaning that no more than one IP address be distributed out from on Port. However, PD3 worked find with that.
This is definitely not possible for the Virtual Machine to get an IP in the Bridged Networking mode if this is really so. But may be there was another option on the switch? I mean "no more then one MAC-address for the port". In this case may be you had used some special build of the Parallels Desktop 3.0, which does special handling for this issue. We did made several of such builds for special requests. Actually, Parallels Desktop 4.0 has some options to allow this without special build, but they are not exposed to the GUI. I will post them to the topic tomorrow.
we have both the late model 2008 MBP with Black keyboard (MBP-BK) and the earlier MPB with Grey Keyboard (MBP-GK). I have just downgrade a MBP-BK to PD3 and upgraded a MBP-GK to PD4 keep in mind used the same virtual image on both machines. the MBP-BK with PD3 has the same issue connecting via Bridge Connection over Ethernet. The MBP-GB upgraded to PD4 has no issues what so ever. So the constant denominator now is the MacBook Pro (black keyboard). Is there a hardware change that might be doing this?
Hi, No, actually hardware change should not be important. Are you using some cable connection or an AirPort to bridge to? In case of AirPort, it may be that GK and BK are connected to the different WiFi Access Points. In that case, for PD40 may help the "Sends the host's MAC address to the DHCP Server". The option is available in the VM Configuration "Network Adapter" when VM Network adapter is bridged to the AirPort and the "Show advanced settings" option is on. In the case of cable-connection, it may be different switches configuration.. Could you please try to swap the sockets to which BK and GK are connected? I mean pull out the cable from the BK and connect it to the GK (and connect the end that was connected to the GK, to the BK) and after this either reboot the VMs or type in the windows cmd.exe two commands ipconfig /release ipconfig /renew ( the ipconfig /release command is important) -- There could be one more issue: the VMs may have the same MAC-address. In this case, they simply conflicts with each other and fix for this is quite simple: MAC address shoud be regenerated: Could you please attach the config files for the VMs? -- Also, there is an option for the VM to use the same MAC address as Host Mac does. Please turn off the PD40 VM and edit the pvs-file for the PD40 VM configuration (I mean config.pvs) to turn on the ForceHostMacAddress option. So, the network adapter configuration in the VM should looks like <NetworkAdapter> ... <ForceHostMacAddress>1</ForceHostMacAddress> </NetworkAdapter> If after turning on the PD40 VM, the VM will still not get the IP, please try also enable the DHCPUseHostMac option (while ForceHostMacAddress is still on) in the same configuration. PS: but most likely it is just a MAC-address conflict between the PD40 VM and PD30 VM, so first step should be regenerating MAC-address for the Parallels Desktop 4.0 VM
hmm.. this issue may stem futher in than just Parallels. Seems liek there may have been a change to our network scope. I say that because both BK and GK laptops will work if on a network with Port security turned off.. meaning more than one IP is "dished" out on a single port.. I will have to get back to you. Though this doesn't have any affect on WiFi
