networking - Local addresses unreachable, remote addresses work

07
2014-04
  • user1217284

    I experienced strange behaviour on my employee's Windows7-Box. I was working via Putty in a local headless Virtualbox (running LXLE and connected via Virtualbox's host-only network adapter) and suddenly got disconnected. While investigating the source of error, I noticed that my network drives also lost connection (to our workgroup's fileserver).

    The Windows7 box has an "Ethernet-Adapter VirtualBox Host-Only Network" with IP 192.168.56.1, which still answered pings. The Virtualbox-guest system has the IP 192.168.56.101 which did not answer to pings. When pinging the .101 address, most of the time I got the answer "request timed out", but only once I got "Reply from 188.1.33.149: Destination host unreachable".

    The latter ping result really puzzles me, as the 188.1.33.149 address is completely unknown to me, and has nothing to do with our LAN. Also it didn't show up anywhere when executing "route print".

    I further noticed that I could not ping local addresses anymore, while pinging remote addresses like google.com worked, as well as opening sites in Firefox. After some time, everything seemed back to normal and I could ping local addresses again, but I still have no clue what caused the error.

    • Answers
  • IfOnlyIHadAGoodUsername

    I would recommend restarting the network from high priority to low priority (Ex: Start host, then add users), I know its a lame answer but you could try.

    If that doesn't work from a previous problem I experienced from accessing localhost could help.

    I once had a problem relating to hosting a fileserver real quick on my pc, I tried having the server host on localhost but it didn't work. But when I was doing ipconfig or something it turns out Windows API has an identifier list.

    So when looking through ipconfig it appeared my computers address was 192.168.1.200 and the 'identifier' was 0.0.0.0.

    But for localhost it said 'undesignated' (I believe this is because I upgraded my computers OS)

    But connecting to 0.0.0.0 worked for me so I guess ipconfig could help (Sorry for the long explanation but I felt it needed context)


    • Related Question

    windows 7 - Can ping IP address and nslookup hostname but cannot ping hostname
  • Puddingfox

    I have a DNS server set up on one of my machines using BIND 9.7 Everything works fine with it. On my Windows 7 desktop, I have statically-assigned all network values. I have one DNS server set -- my DNS server. On my desktop, 

     I can ping a third machine by IP fine.
 I can nslookup the hostname of the third machine fine.
 When I ping the hostname, it says it cannot find the host.

    /

    C:\Users\James>nslookup icecream
Server:  cake.my.domain
Address:  xxx.xxx.6.3

Name:    icecream.my.domain
Address:  xxx.xxx.6.9


C:\Users\James>ping xxx.xxx.6.9

Pinging xxx.xxx.6.9 with 32 bytes of data:
Reply from xxx.xxx.6.9: bytes=32 time<1ms TTL=255
Reply from xxx.xxx.6.9: bytes=32 time<1ms TTL=255
Reply from xxx.xxx.6.9: bytes=32 time<1ms TTL=255
Reply from xxx.xxx.6.9: bytes=32 time<1ms TTL=255

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

C:\Users\James>ping icecream
Ping request could not find host icecream. Please check the name and try again.

    I have also specified the search domain as my.domain

    • xxx.xxx and my.domain substituted for security

    Why can I not ping by hostname? I also can not ping using the FQDN. The problem is that this problem is shared by all applications that resolve hostnames. I cannot use PuTTY to SSH to my machines by hostname; only by IP


    • Related Answers
  • Diskilla

    You could try editing your hosts file. Put there the hostnames and ip-adresses of your other machines. If thats not working try this: Your Router should be able to handle dns-tables for itself. Try to temporarly shut down your dns-server and clear all dns caches on all machines. Then restart your router and try it again.

  • 8088

    I faced the same problem in my network. When you use this command:

    ping icecream

    It uses WINS server since you have used icecream not icecream.my.domain.

    When looking for such words, Windows looks for NETBIOS names, but when you look for complete domain records, it will look in the DNS server. You can use one of the solutions below:

    1. Make sure you have correct records for that station in your WINS server.
    2. Use the complete domain name instead of using the host file. E.g. icecream.my.domain
  • 8088

    You don't have DNS suffixes configured. Either configure them, or use FQDN like this and it should work:

    ping icecream.my.domain
  • bendiy

    I'm looking for a permanent solution to this problem. I don't just have a problem with ping icecream, but also ping icecream.my.domain. It doesn't happen all the time, just randomly on one computer. ipconfig /flushdns fixes it sometimes and rebooting work as well, but it's not a permanent solution.

    I just tried this:

    Based on this:

  • user165568

    To disable this behaviour, disable Negative Caching by setting the value of NegativeCacheTime to 0 at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ Dnscache\Parameter