For anyone wanting to know the the solution to deal with this on Mac:
1. Launch Activity Monitor...
2.Find vmware-vmx process (which will be flagged as not responding)
3. double click this and "Force quit"
4. Then relaunch VMWare Fusion and affected VM.
Still not a long term solution but a work-aroud rather than needing to reinstall the product... Also affects VCenter as well, so seems like a wide-spread issue.
Is there any other solution ?
I have not seen this happen in a very long time (years), but you can also just reboot the mac.
--
Wil
I get it all the time when i enable folder share in VM and the folder that is shared happens be from a NAS.
I do that rather than direct connection to VM because i prefer VM network be shared not Bridged. This issue happens when I run an A/V scan against it... so perhaps doing a direct connection would bypass this error? *shrugs* (usually about 6 to 7 minutes into the scan).
I'm connected by eithernet dongle but also happens on WI-Fi....
Hi,
Sounds like your A/V is the culprit then?
Perhaps you can have it scan at a lower priority?
Btw, as shared is just NAT, you probably can still access network shares from your network.
At least I remember I did in the past.
--
Wil
doubt its A/V, as folder (external usb drive on Mac but shared the same way) is perfectly fine.
The reason i it this way so i can still use NAT........ Trying to access network does not work when set to NAT, as this is only between Mac and VM's.. Your need Bridnet for direct access, which is why i do this workaround of folder sharing from VM.
I might try Briged and access NAS directly from VM and see how i go.
actually looks like i got this one sorted.. Over on another post i saw abut keeping Network disabled and booting up... that worked.