none
Unable to ping or UNC path from a 2012r2 physical hyper-v server to a 2012r2 physical Hyper-v server on a different sub net RRS feed

  • Question

  • Hi Guys,

    We have three hyper-v Windows 2012r2 DC servers. Two are on the same network which 172.16.64.0, the third is on network 172.16.128.0. The two hyper-v servers on Network 64.0 we'll call Hyper-v4 & hyper-v5 and the one on network 128.0 we'll call hyper-v10. All three servers NIC's are setup exactly the same way. 

    From any server on Network 128.0 we can ping any server on Network 64.0 and use UNC paths to connect to any system. From any server EXCEPT hyper-v4 & hyper-v5 on network 64.0 we can ping any server on network 128.0 and connect using UNC paths. We also have a third network 192.168.220.0 that we can ping any server on Networks 64.0 & 128.0 as well as connect to using a UNC path. 

    This is the problem we're having.

    We can not figure out why the two Hyper-v servers on network 64.0 can't ping or do a UNC path to the Hyper-v10 server on network 128.0.

    Any help would be greatly appreciated. 

    Wednesday, October 31, 2018 9:25 PM

Answers

  • Thanks, we finally figure out that the tunnel for that sub net was missing a access rule.

    Thanks everyone for helping.

    Dan

    • Marked as answer by Fishpoleline Tuesday, November 6, 2018 6:29 PM
    Tuesday, November 6, 2018 6:29 PM

All replies

  • "All three servers NIC's are setup exactly the same way. "

    There should be some difference.  The default gateways must be different for each subnet.


    tim


    Thursday, November 1, 2018 1:53 PM
  • Thanks, Sry, I meant they are configured the same as in if NIC teaming is used all three servers have the same NIC teaming configuration. The actual IP and gateway are different on each network.
    Thursday, November 1, 2018 2:05 PM
  • Thanks, active directory domain services is not installed on the hyper-v's. We are confident that the firewall profiles and routing and ICMPv4 are all set correctly since we can ping the hyper-v server from different server on the network. It's on the two Hyper-v servers on network 64.0 that can't ping or do a UNC path to the Hyper-v10 server on network 128.0.

    Dan

    Thursday, November 1, 2018 2:08 PM
  • Posting the text output from ipconfig /all from a working and non-working system would be helpful.

    tim

    Thursday, November 1, 2018 2:23 PM
  • Windows IP Configuration

       Host Name . . . . . . . . . . . . : Hyper-V4
       Primary Dns Suffix  . . . . . . . : ad.mydomain.com
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : ad.mydomain.com

    Ethernet adapter ManagementTeam:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft Network Adapter Multiplexor Dri
    ver
       Physical Address. . . . . . . . . : 
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : (Preferred)
       IPv4 Address. . . . . . . . . . . : 172.16.64.222(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 172.16.64.1
       DHCPv6 IAID . . . . . . . . . . . : 
       DHCPv6 Client DUID. . . . . . . . : 

       DNS Servers . . . . . . . . . . . : 172.16.64.64
                                           172.16.64.65
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Ethernet adapter NicISCSI1:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Intel(R) Ethernet 10G 2P X540-t Adapter #
    2
       Physical Address. . . . . . . . . : 
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : (Preferred)
       IPv4 Address. . . . . . . . . . . : 172.64.32.20(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . :
       DHCPv6 IAID . . . . . . . . . . . : 
       DHCPv6 Client DUID. . . . . . . . : 

       DNS Servers . . . . . . . . . . . : fec0:1:0:gfgf::1%1
                                           fec0:1:0:gfgf::1%2
                                           fec0:1:0:gfgf::1%3
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Ethernet adapter NicISCSI2:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Intel(R) Ethernet 10G 2P X540-t Adapter
       Physical Address. . . . . . . . . : 
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : (Preferred)
       IPv4 Address. . . . . . . . . . . : 172.64.32.21(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . :
       DHCPv6 IAID . . . . . . . . . . . : 
       DHCPv6 Client DUID. . . . . . . . : 

       DNS Servers . . . . . . . . . . . : fec0:1:0:gfgf::1%1
                                           fec0:1:0:gfgf::1%2
                                           fec0:1:0:gfgf::1%3
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Tunnel adapter Local Area Connection* 12:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft Failover Cluster Virtual Adapte
    r
       Physical Address. . . . . . . . . : 
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : (Preferred)
       IPv4 Address. . . . . . . . . . . : 168.128.5.37(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.0.0
       Default Gateway . . . . . . . . . :
       DHCPv6 IAID . . . . . . . . . . . : 
       DHCPv6 Client DUID. . . . . . . . : 

       NetBIOS over Tcpip. . . . . . . . : Enabled

    Tunnel adapter isatap.{56743665673333573}:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
       Physical Address. . . . . . . . . : 
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter isatap.{56743665673333573}:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
       Physical Address. . . . . . . . . : 
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter isatap.{56743665673333573}:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter #4
       Physical Address. . . . . . . . . : 
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter isatap.{56743665673333573}:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter #5
       Physical Address. . . . . . . . . : 
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
    Thursday, November 1, 2018 3:48 PM
  • Windows IP Configuration

       Host Name . . . . . . . . . . . . : Hyper-V10
       Primary Dns Suffix  . . . . . . . : ad.mydomain.com
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : ad.mydomain.com

    Ethernet adapter Managment:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft Network Adapter Multiplexor Dri
    ver #2
       Physical Address. . . . . . . . . : 
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : 
       IPv4 Address. . . . . . . . . . . : 172.16.128.210(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 172.16.128.1
       DHCPv6 IAID . . . . . . . . . . . : 
       DHCPv6 Client DUID. . . . . . . . : 

       DNS Servers . . . . . . . . . . . : 172.16.128.20
                                           172.16.128.21
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Ethernet adapter NicISCSI2:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Broadcom NetXtreme E-Series Advanced Dual
    -port 10GBASE-T Ethernet Network Daughter Card #2
       Physical Address. . . . . . . . . : 
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 172.16.34.55(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . :
       NetBIOS over Tcpip. . . . . . . . : Disabled

    Ethernet adapter NicISCSI1:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Broadcom NetXtreme E-Series Advanced Dual
    -port 10GBASE-T Ethernet Network Daughter Card
       Physical Address. . . . . . . . . : 
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 172.16.34.56(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . :
       NetBIOS over Tcpip. . . . . . . . : Disabled

    Tunnel adapter isatap.{56875678594576363}:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
       Physical Address. . . . . . . . . : 
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter isatap.{56875678594576363}:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter #4
       Physical Address. . . . . . . . . : 
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter isatap.{56875678594576363}:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter #5
       Physical Address. . . . . . . . . : 
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
    Thursday, November 1, 2018 3:56 PM
  • "From any server EXCEPT hyper-v4 & hyper-v5 on network 64.0 we can ping any server on network 128.0 and connect using UNC paths."

    Was hoping for a working server from the 64.0 network.  That way we could compare a machine that is working on the 64 subnet with the Hyper-V4 server that is not working on the same subnet.

    From what you did post, it appears you have DNS servers on other nodes.  You state in your original post that these VMs are DCs.  Are you using integrated DNS?  Are the referenced DNS servers in the reported configurations working DNS services on working domain controllers?  Why do the two machines have different DNS servers?  (That is not necessarily a problem, but it is different to see different DNS servers used in a domain unless you have some special requirements for different subnets.)

    Another potential issue (but should not be affecting ping) is that on Hyper-V4 you have two adapters on the same subnet.  They have names containing the string 'iSCSI' so I am guessing they will be used for accessing an iSCSI target.  Unless you are using certain Dell storage, it is generally not recommended (often won't even work) to have two NICs on the same subnet.  Dell has special configuration issues for some of their iSCSI storage that requires such a configuration, but in any other configuration, it is generally not done.


    tim

    Friday, November 2, 2018 1:22 PM
  • Thanks for the reply. The VM's are not DC's sry for the confusion for the OS on all the Hyper-v servers is Windows Server 2012r2 Data Center.

    For the iSCSI, Microsoft does not recommend TEAMING iSCSi NIC's. In our case the two iSCSI NIC's are handled by the MPIO for the SAN.

    Dan

    Monday, November 5, 2018 6:47 PM
  • Hi,

    Just want to confirm the current the situation. How are things going on? 

    Please feel free to let me know if you need further assistance.

    Best regards,

    Michael


    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    • Marked as answer by Fishpoleline Tuesday, November 6, 2018 6:27 PM
    • Unmarked as answer by Fishpoleline Tuesday, November 6, 2018 6:29 PM
    Tuesday, November 6, 2018 9:36 AM
    Moderator
  • "For the iSCSI, Microsoft does not recommend TEAMING iSCSi NIC's."

    Correct, Microsoft does not recommend teaming iSCSI NICs.  Nor does it recommend two NICs on the same subnet.  The exception is when accessing certain iSCSI targets from DELL.  Then Dell requires it and they provide specific instructions on how to do it.  Otherwise the iSCSI NICs are on different subnets and MPIO handles it properly.


    tim

    • Marked as answer by Fishpoleline Tuesday, November 6, 2018 6:29 PM
    • Unmarked as answer by Fishpoleline Tuesday, November 6, 2018 6:29 PM
    • Proposed as answer by Dave PatrickMVP Tuesday, November 6, 2018 11:38 PM
    Tuesday, November 6, 2018 2:39 PM
  • Thanks, we finally figure out that the tunnel for that sub net was missing a access rule.

    Thanks everyone for helping.

    Dan

    • Marked as answer by Fishpoleline Tuesday, November 6, 2018 6:29 PM
    Tuesday, November 6, 2018 6:29 PM
  • Hi,

    I am glad to hear that your issue was successfully resolved. 

    Thanks for your sharing as it would be very helpful to others who encounters a similar issue.

    Best regards,

    Michael


    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Wednesday, November 7, 2018 8:27 AM
    Moderator