Parallels build 5600 and DHCP problems

Softfailur

Bit poster
Hi all,

After upgrading to the newest build I have encountered weird problem with DHCP. It tries to get 192.168.1.1 address which is already assigned to other machine.
This behavior occurs only when using bridged networking. After choosing 'shared networking' the problem disappears and I can use network connection under Win XP. Although I would really prefer going with "Bridged Connection" as I've done until now. I haven't changed anything in my Windows configuration and reinstalled Parallels Tools right after upgrade to build 5600 was finished.
Anyone has any idea what can be done to overcome this? Any help will be appreciated.
 
Same here. Still broken. Same exact behavior as fortuna. I almost wonder if the Parralells rep even linked the right package? Why would you re-release it with the same rev?
 
Hugh W wrote: yes but why do you need it?

My reason for wishing to use a program feature is my choice. Bridged networking is broken in the new Build. The fact that you use a different method is irrelevant. Anyone who had bothered to read and comprehend the earlier would know this.
 
Yes, it's all gone very quiet, hasn't it. With luck, after the first quick fix attempt failed they're now beavering away on a solid solution but it would be nice to know.
 
Yet another update to Parallels Desktop that targets to fix this problem. It took us longer this time as we wanted to confirm it with several select beta-testers first. We are still unsure that it fixes 100% of cases, so please report any difference in wireless network behavior that you may notice compared to build 5582/5584.

We are looking forward to your feedback.
 
Last edited:
please report any difference in wireless network behavior that you may notice compared to build 5582/5584

A quick first impression - it works! Bridged networking is back & has been working for at least three minutes as I write. One quirk. The VM & Host get DHCP leases (different ones!) automatically but the DHCP client log shows both IP addresses as having the VM's hostname.
 
but the DHCP client log shows both IP addresses as having the VM's hostname.

Oops! Scratch this comment. Late night haste & mis-configuration on my part. All working fine at default Bridged network settings now. Many thanks to Tim & Parallels team.
 
Because I need to get an IP from my windows server!

yes I understand that
but what application needs the IP?

If you define your exact need then the developers can emulate your system and find a fix

An Intel Mac is in fact a unix box with the Mac OS as the primary shell

Remember Win Xp too began as a WinNT front end

the data you want may well be on your machine already if only you can find the hook
for example there is a hidden Apache server running on your machine

For me I find the Mac OS mail and freebie nntp systems adequate for my personal use adn I have no time to be a gamer

what is your user profile?

Hugh W
 
yes I understand that
but what application needs the IP?

If you define your exact need then the developers can emulate your system and find a fix

An Intel Mac is in fact a unix box with the Mac OS as the primary shell

Remember Win Xp too began as a WinNT front end

the data you want may well be on your machine already if only you can find the hook
for example there is a hidden Apache server running on your machine

For me I find the Mac OS mail and freebie nntp systems adequate for my personal use adn I have no time to be a gamer

what is your user profile?

Hugh W

OK, I apreciate your concern/comments but they have nothing to do with the problem.

Why or if I need an IP from my server is not the issue. I have apps that require this, period.

What XP is or where it came from I well know (having started with Tandy radio Shack TRS80, comming to DOS, Windows 1, 3x, 95, 98, 2000, XP and stopping there because it got junk (see Vista)!
What the Mac is or isn't I know as well.


What you need or what fits you is good for you, but not necessarily for others and certainly not in this case.
 
Back
Top