Macbook Pros (Mid 2012) and (Early 2015) models OSX 10.11.6 Windows 10 v1511 Enterprise via Bootcamp Parallels 12.0.2 (41353) Both connecting via wireless in multiple spots Both laptops are experiencing network drops on the VM host (Windows) only. Changing the bridged adapter from WiFi to Default appears to be the only way to regain network access on the VM. Problem seems more likely to happen if there is little network traffic. Drops don't appear to happen if actively using the connection like streaming a video or music. Running in Coherence mode doesn't resolve issue.
Hi, could you please send a problem report from running VM (no another action is required) from menu Parallels Desktop -> Help -> Send technical data and post here its number
A user just had this happen this morning, and the Technical ID: 128370572. FWIW, this problem seems to present itself more often when using a VPN.
Another Problem, Technical ID: 128397146 Some more information... The Mac side continues to function as normal when the PC loses connection. The Windows installation will drop back to an auto-assigned "169.x.x.x" address if you wait long enough. Pinging an IPV4 address results in a "PING: transmit failed. General Failure.".
Both users noticed there was a Parallels update this morning. They installed this update, which took them to Parallels version 12.1.0 (41489). One of the users just had the same disconnect issue. Another Technical ID: 128646426 has been submitted.
Any update on this? The update appears to cause more disconnects than the previous version on one of the machines.
Same problem here, since I've change my Imac and update to Pararelles 12 my Window partition drop out when I'm not working on for 2-3 minutes, I've check all other setting like screen saver or else
I maybe fine something, on your Window partition (sorry but mine is French) go to network share center than clic on property and you'll see NetLimiter Ndis Driver, just unselect it and clic ok. It's working for me and it's been weeks that i'm searching
This issue still is not resolved. The fix about the NetLimiter Ndis driver doesn't affect it (for us). We have found that running a "ping /t google.com" in a cmd window mitigates it, though. So it must be something about not having network traffic for a period of time.
