VMware network Adapter VMnet1 and VMnet8 are classified as solutions for [unrecognized network-public network] (transcribed)

System: Windows7 x64

Virtual software: VMware Workstation 7.1.3

Scenario: VMware Network Adapter VMnet1 and VMnet8 are identified by the firewall as an unrecognized network-public network, blocked, unable to use port mappings, the virtual machine's 80 port cannot be passed in, and the packet can only be entered. And the public network is restricted from being modified to a home or work network.

Workaround: Refer to the VMware Knowledge Base article [Http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC &EXTERNALID=1004813]

The following paragraph is the specific operation:

Redefine the VMware virtual NICs as endpoint Devicesthis procedure are permanent and allows for the continued use of Bridge D, NAT, and Host only networking. However, doing this causes the VMware virtual NICs to disappear from the Network and sharing Center, even though they rema In visible under Network Connections. This also causes the VMware virtual NICs to is exempt from all Windows Firewall access rules. When implemented, the control of virtual machine network access must is done from the guest operating system of each Virtu Al Machine. This bypasses the default security model of Windows with respect to the VMware virtual NICs, and the implications of U Sing This procedure must is carefully considered. To redefine the VMware virtual NICs as endpoint devices:

2. Click Start > Run, type regedit and, click OK.
4. Navigate to HKEY_LOCAL_MACHINE > System > CurrentControlSet > Control>class > { 4D36E972-E325-11CE-BFC1-08002BE10318}.
   
   Caution: VMware recommends that's back up this registry key before proceeding. To backup the registry:
   1. If {4D36E972-E325-11CE-BFC1-08002BE10318} is not still highlighted, click it.
   2. Go to File > Export.
   3. Pick a location and name for the registration File (*.reg).
   4. Click Save.
6. Click 0000.
8. Look at the content of the Data field associated with the driverdescentry.
10. If you see VMware Virtual Ethernet Adapter for Vmnet<x>, where<x> was replaced by a number and then:
    1. Right-click a empty space in the right content pane.
    2. Click New > Dword.
    3. Type *ndisdevicetype and press Enter.
       Note: Be sure to include the asterisk (*) at the beginning of the entry.
    4. Double-click *ndisdevicetype.
    5. Type 1 and press Enter.
12. Repeat steps 4-6, replacing 0000 in step 4 with the next entry on numerical order, until you have reached the end Of all numerical entries.
14. Follow the Disable the VMware virtual NICs section of this article above.
16. Repeat Step 8 But click to Enable this network device instead.

The simple Chinese translation is:

1, enter the registration form [hkey_local_machine\system\currentcontrolset\control\class\{4d36e972-e325-11ce-bfc1-08002be10318}], Pilot out to do the backup.

2, look under the [item] (0000,0001 to 00XX), and see which of the right [value] is: "DriverDesc" = "VMware Virtual Ethernet Adapter for VMnet1".

3, when found, add a "DWORD" value (32 bits) with the name "*ndisdevicetype" (the * number is required) and the data value to "1".

4, repeat the 2nd step, find VMnet8, repeat the 3rd step, add the value.

Restart Windows when you are finished.

Source: > The blog name is: " a never-ending Pasu”

VMware network Adapter VMnet1 and VMnet8 are classified as solutions (transcribed) for [unrecognized network-public network]