1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

XP ping can't look up local hosts

Discussion in 'Networking Issues' started by Quatrix, Aug 6, 2007.

  1. Quatrix

    Quatrix Network Guru Member

    I'm using dnsmasq on a WRT54G with the HyperWRT Thibor firmware. I added the local routers and cable modem to the dnsmasq .hosts file:

    192.168.1.1 WRT54G
    192.168.1.2 BEFW11S4
    192.168.1.3 WRT54GL1
    192.168.1.4 WRT54GL2
    192.168.100.1 BEFCMU10

    I'm able to look up and ping these by host name from the busybox shell without any trouble:

    # nslookup befcmu10
    Server: localhost
    Address: 127.0.0.1

    Name: befcmu10
    Address: 192.168.100.1

    # ping befcmu10
    PING befcmu10 (192.168.100.1): 56 data bytes
    84 bytes from 192.168.100.1: icmp_seq=0 ttl=64 time=1.8 ms
    84 bytes from 192.168.100.1: icmp_seq=1 ttl=64 time=1.8 ms
    84 bytes from 192.168.100.1: icmp_seq=2 ttl=64 time=1.8 ms

    XP nslookup resolves the hosts/IPs just fine, BUT they don't work in ping, tracert, or any Windows apps.

    < D:\Windows > nslookup befcmu10
    Server: WRT54G
    Address: 192.168.1.1

    Name: befcmu10
    Address: 192.168.100.1

    < D:\Windows > ping befcmu10
    Ping request could not find host befcmu10. Please check the name and try again.

    Any idea what the problem might be?
     
  2. Quatrix

    Quatrix Network Guru Member

    Never mind...

    I checked the syslog, and "ping befcmu10" isn't even connecting to the DNS. It works if I add a dot to the end (ping befcmu10.) to force TCP/IP. Otherwise it tries NetBIOS.
     
  3. mstombs

    mstombs Network Guru Member

    so that's why you are recommended to define names with a domain, such as wrt54gs.lan, then they work!
     
  4. Quatrix

    Quatrix Network Guru Member

    It's working with just a dot though. I think "WRT54G." is easier than "WRT54G.lan", even if it looks a little strange.
     
  5. Stavr0

    Stavr0 Addicted to LI Member

    Now that's an obscure bug.

    Same here. What would be the standard naming convention for local hosts?

    .lan? .local?

    Also adding a dot at the end only works for ping, browsing a local resource creates a page with all the dots removed, which then fails DNS again. To solve this problem, set the domain name to 'local' 'lan' or whatever name you choose as long as no global name exists out there. With the opening up of TLD names it's going to be very important to choose an unambiguous name.

    Next thing to do is go in Network Connections/TCPIP Properties/Advanced and set the default DNS suffix for the connection to the same value as the router's.

    Then all unqualified hostnames will automatically get appended with the local DNS domain.
    Pinging my printer:
     
  6. HennieM

    HennieM Network Guru Member

    Always good to have hostname.domainname. If you set your domain name on the router, then

    ping hostname
    OR
    http://hostname/

    will work as good as

    ping hostname.domainname

    because your XP machine gets the message that it and other hosts on your local network are something.domainname.

    However, the source of the original problem, IMO, is the broken DNS client on Windoze. Try turning the "DNS Client" off in XP's services.
     

Share This Page