Fix: Reply from xxx.xxx.xxx.xxx: Destination host unreachable

In my test Hyper-V environment, I created several virtual machines (VMs). One of them is a domain controller, ADSrv which is also a DSN server. I have two other VMs, which are successfully added to the domain. However, I encountered the problem to add a third server, TestSrv to join the domain. All these servers are added the same Virtual Network created using Virtual Network Manager in Hyper-V. I cannot ping ADSrv or TestSrv from each other, and get the following error message from Ping IPAddress command:

clip_image001
Figure 1: Ping TestSrv from ADSrv

clip_image002
Figure 2: Ping ADSrv from TestSrv

The first step I would like to check the network configuration for each server, which looks correct as fellows:

clip_image003
Figure 3: ADSrv (Domain Controller, DNS server)

clip_image004
Figure 4: TestSrv

The second step I would think this issue should be due to that the ICMP traffic was blocked by Windows Firewall therefor I created an exception for ICMPv4 protocol on both ADSrv and TestSrv for ICMP protocol. However, I still cannot ping each them from each other server, which frustrated me a lot. (P.S. This is usually the cause when the server cannot be Pinged.)

Finally, after some diggings, I noticed the following different virtual LAN Identification configurations as fellow:

clip_image005
Figure 5: Network Adapter configuration for ADSrv

clip_image006
Figure 6: Network Adapter configuration for TestSrv

I think you have already noticed the differences, the both servers ADSrv (Domain Controller as VM name)and TestSrv (SAN as VM name) are configured with the same virtual network, called Domain Network in this case, and have “Enable virtual LAN Identification” checked, but with different VLAN ID – which is the root cause in this case. Since the two servers with different VLAN ID, therefore they cannot access each other as all traffic for the managed operating systems that goes through the network adapter will be tagged with the VLAN ID you set.

To resolve this issue, we have two solutions:

  1. Update the VLAN ID to the same value (I updated the VLAN ID to 5 for TestSrv server).
  2. Uncheck the “Enable virtual LAN identification”.

P.S. If you have any other servers also use this network (such as Domain Network in this case), make sure all of these servers using the network either have “Enable virtual LAN identification” checked with the same VLAN ID or with it disabled.

References:

Advertisements

About Alex Feng

SQL Server DBA in Alibaba Cloud Computing
This entry was posted in Hyper-V and tagged , , . Bookmark the permalink.

One Response to Fix: Reply from xxx.xxx.xxx.xxx: Destination host unreachable

  1. washington says:

    thanks for share, this information open my mind for my problem, i resolved already.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s