After installing VMware in Windows Vista or 7, there are two public networks that can't be identified, but upon further inspection are virtual networks created by VMware. The problem is when you're on a Home network, these "Unidentified Networks" are still there and mess up file sharing settings, among other things.
-
I don't mind with the unidentified networks thingy but I don't like the fact that it messes with file sharing– user4951May 14, 2012 at 7:23
-
That is nice. Do you also have a question?– HennesJul 19, 2016 at 19:39
Add a comment
|
2 Answers
Per this site:
Click Start, click Run, type regedit, and then click OK.
Click the following subkey:
HKLM\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}Browse through the 00xx subkeys until you find the REG_SZ VMNet subkey with a value of either “\DosDevices\VMnet8” or “\DosDevices\VMnet1” (default values)
On the Edit menu, point to New, and then click DWORD Value.
Type *NdisDeviceType, and then press Enter.
On the Edit menu, click Modify.
Type 1, and then click OK.
Exit Registry Editor.
Disable & re-enable the VMWare NICs
Log-out of your Windows account and log back in.
Done
Or, optionally, use this powershell script to do the same thing automatically. This is most useful in Windows 7 which has PowerShell built in.
answered Jul 23, 2009 at 19:57
-
BTW, still coming back to this almost a year later as a reference every time I need to fix this on a new system / install of Vmware. :) May 6, 2010 at 3:19
Go to the Windows Firewall properties and disable the firewall for the VMWare adapter.
-
-
-
I've had this issue when deploying Virtual Machines to RDS... This worked great in this circumstance too, thanks! May 23, 2016 at 18:33