locked
Can no longer ping Hyper-V server by internal IP RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi guys,

    I have 2 Hyper-V 2012 servers, which are joined to a domain (2 DCs) which are VMs on these servers. There are appropriate DNS records for each Hyper-V server.

    I have noticed that both servers have identical ipconfig settings (with of course different IPs etc), but when I run tracert and the hostname of one Hyper-V server, the first hop returns the destination Hyper-V server.

    If I do this on the other Hyper-V server, it will return hostnames which are of my webhost. It seems to be trying to use the public DNS to find the internal server (the server I am pinging FROM has 2 nics the private network and public internet).,

    As a result, I can't ping this Hyper-V server. The firewall is off and nor can I ping the VMs internally by the private IPs. It looks like on a 2 NIC'd VM, the public NIC is trying to resolve the private IP, and one a server with just the private NIC, I get destination host unreachable.

    Any suggestion what may cause this? I can however ping outwards from this server.



    • Edited by GSS1 Friday, July 26, 2013 11:53 PM
    Friday, July 26, 2013 11:37 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    My first inclination on this is that this is either a DNS issue / name resolution issue - or a misconfiguration issue (your public IP is forwarded to the host IP and not the VM IP).

    Brian Ehlert
    http://ITProctology.blogspot.com
    Learn. Apply. Repeat.
    Disclaimer: Attempting change is of your own free will.

    Monday, July 29, 2013 3:09 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    We need more information to help. Please post the results of ipconfig /all on both host and VM.

    Bob Lin, MVP, MCSE & CNE Networking, Internet, Routing, VPN Troubleshooting on

    http://www.ChicagoTech.net

    How to Setup Windows, Network, VPN & Remote Access on

    http://www.howtonetworking.com

    Saturday, July 27, 2013 3:06 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    IPConfig of problematic hyperv server:


    Windows IP Configuration

       Host Name . . . . . . . . . . . . : HV3-DEV-64-MAIN
       Primary Dns Suffix  . . . . . . . : INFRASTRUCTURE.SHAREPOINT.LOCAL
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : INFRASTRUCTURE.SHAREPOINT.LOCAL

    Ethernet adapter vEthernet (Private Virtual Switch):

       Connection-specific DNS Suffix  . : 
       Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #3
       Physical Address. . . . . . . . . : 00-30-48-FF-15-F3
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::3566:7ed2:1fa2:7920%23(Preferred) 
       IPv4 Address. . . . . . . . . . . : 192.168.0.43(Preferred) 
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 
       DHCPv6 IAID . . . . . . . . . . . : 402665544
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-19-3F-8A-6F-00-30-48-FF-15-F3
       DNS Servers . . . . . . . . . . . : 192.168.0.7
                                           192.168.0.14
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Ethernet adapter vEthernet (External Virtual Switch):

       Connection-specific DNS Suffix  . : 
       Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #2
       Physical Address. . . . . . . . . : 00-30-48-FF-15-F2
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::d9cb:5bca:dbf9:7381%21(Preferred) 
       IPv4 Address. . . . . . . . . . . : xxx
       Subnet Mask . . . . . . . . . . . : xx
       Default Gateway . . . . . . . . . : xxx
       DHCPv6 IAID . . . . . . . . . . . : 352333896
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-19-3F-8A-6F-00-30-48-FF-15-F3
       DNS Servers . . . . . . . . . . . : 4.2.2.1
                                           4.2.2.2
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Tunnel adapter isatap.{CB6A3CD2-E8B1-41A9-BD97-3B02F1C236BE}:

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

    Tunnel adapter Teredo Tunneling Pseudo-Interface:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . : 
       Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter 6TO4 Adapter:

       Connection-specific DNS Suffix  . : 
       Description . . . . . . . . . . . : Microsoft 6to4 Adapter
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv6 Address. . . . . . . . . . . : 2002:d89e:4db2::d89e:4db2(Preferred) 
       Default Gateway . . . . . . . . . : 2002:c058:6301::c058:6301
       DNS Servers . . . . . . . . . . . : 4.2.2.1
                                           4.2.2.2
       NetBIOS over Tcpip. . . . . . . . : Disabled

    Tunnel adapter isatap.{A0FF1155-197F-4B43-BECC-61A8DC4ADA40}:

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

    I've put xxx in for the public IP for security reasons, but that's a normal, working IP.

    Saturday, July 27, 2013 3:36 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    My first inclination on this is that this is either a DNS issue / name resolution issue - or a misconfiguration issue (your public IP is forwarded to the host IP and not the VM IP).

    Brian Ehlert
    http://ITProctology.blogspot.com
    Learn. Apply. Repeat.
    Disclaimer: Attempting change is of your own free will.

    Monday, July 29, 2013 3:09 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Why is there no gateway configured on "Ethernet adapter vEthernet (Private Virtual Switch)"?
    Monday, July 29, 2013 3:23 PM