VMware Workstation 14虚拟机互ping异常：VM2无法ping通VM1求助

Hey there, I’ve dealt with this exact one-way connectivity issue in VMware lab setups before, and it’s almost always the culprit behind failed SCCM PXE deployments. Let’s walk through troubleshooting step by step since your VM1 can ping VM2 but not the reverse—here’s what to check:

1. Lock Down Windows Firewall on VM1 (Critical First Step!) #

By default, Windows Server 2016’s firewall blocks incoming ICMP (ping) requests, plus all the ports SCCM/PXE rely on for bidirectional communication. This is 90% of the time the root cause here:

• Temporarily disable the firewall on VM1 (Windows Defender Firewall > Turn Windows Defender Firewall on or off) and test pinging VM2 again. If this fixes the ping issue, you know the firewall is blocking traffic.
• Re-enable the firewall and create explicit inbound rules:
  • Allow ICMPv4 Echo Requests (to fix the ping issue).
  • Allow SCCM/PXE required ports: UDP 67/68 (DHCP), UDP 69 (TFTP), TCP 80 (HTTP), TCP 443 (HTTPS), and TCP 1433 (if you’re using a local SQL instance for SCCM).

2. Validate VMware Host-Only Network Configuration #

Host-Only networks can have hidden conflicts that break reverse connectivity:

• Open VMware Workstation > Edit > Virtual Network Editor.
• Select your Host-Only network (usually VMnet1) and confirm:
  • The subnet IP matches your DHCP scope on VM1 (e.g., if your DHCP pool is 192.168.1.10-20, subnet should be 192.168.1.0/24).
  • Uncheck "Use local DHCP service to distribute IP addresses to VMs"—VMware’s built-in DHCP will clash with your VM1 DHCP server.
  • Both VMs are assigned to the exact same Host-Only network (no accidental VMnet2 or NAT assignments).

3. Verify VM2’s DHCP-Assigned IP & Network Settings #

Even if VM2 pulls an IP from DHCP, double-check its configuration:

• When VM2 boots to PXE, press F8 to open a command prompt (this works with SCCM’s boot image).
• Run ipconfig /all to confirm:
  • IP address is within your DHCP scope.
  • Default gateway is set to VM1’s IP (if VM1 is your gateway) or the correct Host-Only subnet gateway.
  • DNS server is set to VM1’s IP (critical for SCCM hostname resolution).
• Try pinging VM1’s raw IP first (not its hostname)—if this fails, it’s a connectivity/firewall issue; if hostname fails, check DNS records on VM1.

4. Check DHCP Scope Options on VM1 #

SCCM PXE boot relies on specific DHCP options to find the boot image:

• Open DHCP Manager on VM1 > Your Scope > Scope Options.
• Verify option 66 (TFTP Server Name) is set to VM1’s IP address.
• Verify option 67 (Bootfile Name) is set to boot\x86\wdsnbp.com (for x86) or boot\x64\wdsnbp.com (for x64)—this tells VM2 where to pull the SCCM boot image from.
• Ensure there’s no conflicting MAC address reservation for VM2 that’s assigning an incorrect IP.

5. Reset VMware VM Network Adapters #

Sometimes flaky adapter settings cause connectivity drops:

• Power off both VMs.
• Remove the network adapter from each VM, then add a new adapter and reassign it to the Host-Only network.
• Make sure "Connect at power on" is checked for both adapters.

Final Test #

After applying these fixes:

1. Power cycle both VMs.
2. Boot VM2 to PXE—you should see the SCCM boot menu appear.
3. From VM2’s PXE command prompt, ping VM1’s IP to confirm bidirectional connectivity.
4. Proceed with your SCCM deployment—this should resolve the failure.

内容的提问来源于stack exchange，提问作者M.Naro