Will a fixed IP address get you going? I use my MacBook Pro at home and at work. The network at home and at work are essentially the same from the MacBook's perspective. At both places the network is wireless and the connections should happen automatically using DHCP, as they do on the MAC OS X side but not with Parallels. Parallels DHCP only works at one location, not the other, for me. I haven't been able to figure out why the difference. But rather than hassle around trying things out, I just configured Windows XP under Parallels to use a FIXED IP address rather than a Dynamic address, and everything works just fine. This DHCP anomoly "problem" I've had has been around since the release of Parallels. I was hoping the beta would allow DHCP to work at both locations but it didn't. If you don't know how to configure a fixed IP address, this can get you started. I may miss a step or two but it should serve as a cookbook to set up a fixed IP address. (There are other ways, this is just one way, and I apologize if it isn't the most elegant). In Windows XP - Click on START and select CONTROL PANEL -Double click on NETWORK CONNECTIONS -Click on PROPERTIES -Scroll down and select INTERNET PROTOCOL (TCP/IP) connection, click on PROPERTIES -Change from "automatically" to "Use the follwing address:" Now here is where you need help from your network administrator, and if that is you, you need the knowledge to select an unused IP address that works on your network. If you are the network administrator on your home network here is one approach to pick an IP address: Under the BLUE APPLE (upper left corner of your screen) select LOCATION / NETWORK PREFERENCES..... Select your AIRPORT connection (or built in ethernet if you are hardwired) Click on CONFIGURE Click on TCP/IP You should be able to see your Mac's IP address, mask and router address. Write these down. 99.9% of the time your mask will be 255.255.255.0 On my home network my IP address is 10.6.18.10, yours could start with a 10. or 12 .or 192. or whatever. Change the LAST number to something you are pretty darn sure isn't being used by another device on your netowrk. In my case I'll select 10.6.18.70 and use that for my Parallels virtual machine IP address. So go back into Parallels and enter your new IP address. Enter the same mask as the mask your Mac is using. Enter the same router address as the router you Mac is using. So be sure the ONLY address you differ on for Windows/Parallels is the IP address and that only varies on the rightmost number. You also need a DNS server address so Windows can figure out the IP address when you use names instead of numbers to get to the internet. If you don't know you DNS server address (and there usually isn't any reason to know this address) here is one way to find out the DNS server your Mac is using to resolve names into addresses. Launch NETWORK UTILITY which you will find in your UTILITIES folder inside your APPLICATIONS folder. Click on the Lookup tab at the top Enter an address to look up, like "www.apple.com". Make sure you are looking for ANY/ALL INFORMATION by selecting this choice in the "Select the information to lookup:" box. At the end of the result window you will see a "Query time" followed by the SERVER address. This is your DNS server. Use this same address for the DNS server entry in Windows. Then close these properties window and wait a while for Windows to redo the network stuff. On my machine I have to wait a couple of minutes for Windows to change the network connection and get everything settled down. Back in Windows, looking at your network connection for "Parallels Network Adapter" it should change from limited connection to "connected" You should now be able to connect to the internet. However, if you move to another network, you have to repeat this process to have a unique IP address, and have the correct router address on the second network. I'm sure I've missed a thing or two or not made something clear, but maybe others will help clarify this approach. Hope that gets those of you that can't connect at least working until the DHCP failing on some networks "mystery" gets solved.