none
Can't ping hostname

    Question

  • I can't ping any hostname from one windows 2012 R2 server. However, I can ping the same server using IP with -a. nsllokup also can find the hostname. What could be the problem?


    C:\Users\blin>ping spcex01.printing.local
    Ping request could not find host spcex01.printing.local. Please check t
    he name and try again.

    C:\Users\blin>ping -a 172.16.19.10

    Pinging spcex01.printing.local [172.16.19.10] with 32 bytes of data:
    Reply from 172.16.19.10: bytes=32 time<1ms TTL=128
    Reply from 172.16.19.10: bytes=32 time=1ms TTL=128
    Reply from 172.16.19.10: bytes=32 time<1ms TTL=128
    Reply from 172.16.19.10: bytes=32 time<1ms TTL=128

    Ping statistics for 172.16.19.10:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 0ms, Maximum = 1ms, Average = 0ms

    C:\Users\blin>nslookup
    Default Server:  spcdc01.printing.local
    Address:  172.16.19.14

    > spcex01
    Server:  spcdc01.printing.local
    Address:  172.16.19.14

    Name:    spcex01.Printing.local
    Address:  172.16.19.10


    Bob Lin, MCSE &amp; CNE Networking, Internet, Routing, VPN Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net How to Install and Configure Windows, VMware, Virtualization and Cisco on http://www.HowToNetworking.com

    Tuesday, May 13, 2014 2:03 AM

Answers

All replies

  • netbios is enabled on the NIC?

    Every second counts..make use of it. Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.
    IT Stuff Quick Bytes

    Tuesday, May 13, 2014 4:34 AM
  • Hi Bob,

    I hope all is well!

    Please post an ipconfig /all of this client to help diagnose it.

    Thanks!


    Ace Fekay
    MVP, MCT, MCSE 2012, MCITP EA & MCTS Windows 2008/R2, Exchange 2013, 2010 EA & 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
    Microsoft Certified Trainer
    Microsoft MVP - Directory Services
    Complete List of Technical Blogs: http://www.delawarecountycomputerconsulting.com/technicalblogs.php

    This posting is provided AS-IS with no warranties or guarantees and confers no rights.

    FaceBook Twitter LinkedIn

    Wednesday, May 14, 2014 7:47 PM
  • Thank you, Ace.

    The problem is the server lost the trust to the domain and re-joining the domain fixes the probelm. This is the troubleshooting process;

    Can't ping hostname  - Resolution with screenshots  


    Bob Lin, MCSE &amp; CNE Networking, Internet, Routing, VPN Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net How to Install and Configure Windows, VMware, Virtualization and Cisco on http://www.HowToNetworking.com


    • Edited by chicagotech Thursday, May 15, 2014 2:36 AM
    • Proposed as answer by cguan Thursday, May 15, 2014 3:48 AM
    Thursday, May 15, 2014 2:35 AM
  • Sounds like a DNS Suffix issue.  Post your IPConfig /all and ensure your namespace of printing.local is listed.

    Also, try using debug with your NSLookup to see what is appended:

    NSLookup
    Server: someserver
    Address: someIPaddress
    
    > Set Debug
    > spcex01
    
    
    Review the logs.  Look for which attempt had answers.


    - Chris Ream -

    **Remember, if you find a post that is helpful, or is the answer, please mark it appropriately.**

    Thursday, May 15, 2014 3:37 AM
  • Thank you, Ace.

    The problem is the server lost the trust to the domain and re-joining the domain fixes the probelm. This is the troubleshooting process;

    Can't ping hostname  - Resolution with screenshots  


    Bob Lin, MCSE &amp; CNE Networking, Internet, Routing, VPN Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net How to Install and Configure Windows, VMware, Virtualization and Cisco on http://www.HowToNetworking.com


    I can't see how the secure channel to the domain can cause this, other than a Windows firewall issue where the Domain profile is not applicable. 

    Think of it this way, if the machine wasn't joined,  ping can still use DNS to resolve a query,  right? So something else is occurring that's causing the client side resolver to stop resolving.  Ping uses the client resolver, where nslookup ha its own built-in resolver. The OS uses its resolver ju st as ping, so that would tell me the problem lies in that area, because when the resolver stops resolving, the computer loses the ability to "find" the domain. Maybe it's the anti virus causing it? 


    Ace Fekay
    MVP, MCT, MCSE 2012, MCITP EA & MCTS Windows 2008/R2, Exchange 2013, 2010 EA & 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
    Microsoft Certified Trainer
    Microsoft MVP - Directory Services
    Complete List of Technical Blogs: http://www.delawarecountycomputerconsulting.com/technicalblogs.php

    This posting is provided AS-IS with no warranties or guarantees and confers no rights.

    FaceBookTwitterLinkedIn


    Thursday, May 15, 2014 10:58 AM
  • Hi,

    When troubleshooting name resolution issues, it is important to narrow down whether the application is resolving a NetBIOS name or a host name. You can try to change the client DNS server as others DNS in  your intranet.

    More information:

    Microsoft TCP/IP Host Name Resolution Order

    http://social.technet.microsoft.com/Forums/en-US/cb019c01-7489-44d1-8399-9b0df6fc0842/cant-ping-hostname?forum=winserverNIS

    Hope this helps.


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

    Friday, May 16, 2014 6:48 AM
    Moderator
  • I had a similar issue. I wasn't able to ping any names, only IP's. DNS was apparently running in the background, ipconfig /displaydns was returning DNS queries, although telnet on port 53 was not working to the DNS server, I was receiving error "An invalid argument was supplied telnet on port 53" I was also able to log in with domain credentials.

    In my case the issue was with User Access Control. Somebody enabled it, and didn't reboot the server immediately after that action. Most probably some other actions were performed on the server, that were pending also reboot, and from that point UAC was acting recklessly not allowing users to perform basic actions, like pinging names or telneting the DNS server on port 53.

    I have noticed by chance, after century-old battles that lasted almost 2 days that I could not access directly (an access denied message was received)  one of the system folders, C:\Windows\temp. It is the normal behavior when UAC is enabled. I have checked before the UAC settings, and the slide bar was all the way down(disabled), but apparently this feature was still "live".

    I've enabled it back(moved the slide bar up), rebooted the server and that was it, everything went back to normal. I have disabled it again, afterwards, because we need it like that, and reboot immediately the server and things were also ok.

    So..UAC... a big NO for Microsoft ! 
    Thursday, September 14, 2017 12:40 PM