I've finally been able to trace back a problem that I've been having recently to Parallels Desktop 8 for Mac, but first a little background information is in order. I'm running a MacBook Pro with Retina Display (10,1), with OS X Mountain Lion 10.8.2 and Parallels Desktop version 8.0.18101. No WiFi issues at home connecting to a Time Capsule and other Airport Express units. Now, onto the problem.
I recently traveled to one of our other sites and needed to use WiFi to connect to our network (I normally use a Thunderbolt Ethernet adapter in my office). I fired it up and connected to the network just fine, but then noticed that I kept losing network connectivity. The WiFi signal was fine and I was not disconnecting and reconnecting to the access point, but the Mac was simply unable to communicate over the network sometimes. I tried Windows 7 Pro in the VM and it was communicating via the network with no issues at all, even though OS X could not. I thought that there may be some issues with the other site's WiFi configuration, but it is the same as my normal office's, so no dice there. By the way, this is using a bridged connection with the default adapter in the VM. The office WiFi network uses WPA2 Enterprise security with AES encryption and Microsoft PEAP authentication.
When I got back, I tried the same thing on our network with the same results. Windows VM had no issues over the Mac's WiFi connection, OS X kept losing communication with the network. I started a ping test on OS X to try to see what was going on and it showed that the Mac could see the DNS server for maybe 10 seconds or so and then would not be able to see it for about 20 seconds as the ping request would simply timeout. Then, again for about 10 seconds the Mac would connect and again disconnect. This cycle would repeat over and over endlessly. Very strange. I wondered what on earth could be causing this. I called AppleCare and we removed all the WiFi networking components and reinstalled all of them to no avail. I continued poking around as I got time to and eventually stumbled across the fact that if the VM was shut down or asleep, the Mac would have full WiFi connectivity. Start up the VM and, wham, the Mac would start cycling on and off of the network. I know that I did not have this issue under Parallels Desktop 7, so it definitely has something to do with version 8.
I called in for support from Parallels and we went through all the standard troubleshooting, reinstalling the desktop tools, tried it in shared network mode, which worked just fine, by the way, and a few other things, but there was no change in what I was seeing in bridged mode to the default adapter. The technician then wanted to see if using one of the virtual NICs would help and it did. Then I had full connectivity in bridged mode on both the Mac and the VM. So, he considered the issue resolved and closed the ticket.
Here, finally, is my real concern. My system used to work just fine in bridged mode with the default adapter selected under Parallels Desktop 7. I could switch between a wired and wireless connection at will and all would work just fine. Now I have to play around with the configuration and change NICs when changing network connections, which while not that big of a deal is still rather annoying. I don't consider the problem resolved and wish that the technician would have left it open and pushed the issue back to the development team for a real resolution. Does anyone have any thoughts to share about this? Will this post here in the forums make any difference?
I recently traveled to one of our other sites and needed to use WiFi to connect to our network (I normally use a Thunderbolt Ethernet adapter in my office). I fired it up and connected to the network just fine, but then noticed that I kept losing network connectivity. The WiFi signal was fine and I was not disconnecting and reconnecting to the access point, but the Mac was simply unable to communicate over the network sometimes. I tried Windows 7 Pro in the VM and it was communicating via the network with no issues at all, even though OS X could not. I thought that there may be some issues with the other site's WiFi configuration, but it is the same as my normal office's, so no dice there. By the way, this is using a bridged connection with the default adapter in the VM. The office WiFi network uses WPA2 Enterprise security with AES encryption and Microsoft PEAP authentication.
When I got back, I tried the same thing on our network with the same results. Windows VM had no issues over the Mac's WiFi connection, OS X kept losing communication with the network. I started a ping test on OS X to try to see what was going on and it showed that the Mac could see the DNS server for maybe 10 seconds or so and then would not be able to see it for about 20 seconds as the ping request would simply timeout. Then, again for about 10 seconds the Mac would connect and again disconnect. This cycle would repeat over and over endlessly. Very strange. I wondered what on earth could be causing this. I called AppleCare and we removed all the WiFi networking components and reinstalled all of them to no avail. I continued poking around as I got time to and eventually stumbled across the fact that if the VM was shut down or asleep, the Mac would have full WiFi connectivity. Start up the VM and, wham, the Mac would start cycling on and off of the network. I know that I did not have this issue under Parallels Desktop 7, so it definitely has something to do with version 8.
I called in for support from Parallels and we went through all the standard troubleshooting, reinstalling the desktop tools, tried it in shared network mode, which worked just fine, by the way, and a few other things, but there was no change in what I was seeing in bridged mode to the default adapter. The technician then wanted to see if using one of the virtual NICs would help and it did. Then I had full connectivity in bridged mode on both the Mac and the VM. So, he considered the issue resolved and closed the ticket.
Here, finally, is my real concern. My system used to work just fine in bridged mode with the default adapter selected under Parallels Desktop 7. I could switch between a wired and wireless connection at will and all would work just fine. Now I have to play around with the configuration and change NICs when changing network connections, which while not that big of a deal is still rather annoying. I don't consider the problem resolved and wish that the technician would have left it open and pushed the issue back to the development team for a real resolution. Does anyone have any thoughts to share about this? Will this post here in the forums make any difference?