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

Welcome To SNBForums

SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.

If you'd like to post a question, simply register and have at it!

While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!

(Resolved) Differences in Chrome browser depending on the device

Discussion in 'General Wireless Discussion' started by Michael Gauthier, Mar 6, 2018.

  1. Michael Gauthier

    Michael Gauthier New Around Here

    Joined:
    Mar 6, 2018
    Messages:
    8
    I have a raspberry pi running a server. I connect to it by typing the IP address in a Chrome browser on mobile devices, Windows or a Mac. I can also type the pi's hostname "dimlights/" to access it, except on the Windows 10 PC running Chrome. On that PC I can only reach the pi via its IP address.
    I am using Chrome on all 4 devices:

    iPhone Chrome works with IP or "dimlights/"
    Android Chrome works with both
    Mac running High Sierra and Chrome works with both
    Windows 10 system with Chrome only works with the IP address. With the hostname dimlights/ it gets the error:

    "This site can’t be reached
    dimlights
    ’s server IP address could not be found.
    ERR_NAME_NOT_RESOLVED"

    Why does this only happen on the Win 10 system?
     
  2. ColinTaylor

    ColinTaylor Part of the Furniture

    Joined:
    Mar 31, 2014
    Messages:
    9,267
    Location:
    UK
    To be fair this isn't a question about wireless networking. You might be better served asking your question in a Windows or Chrome forum.

    That aside, from the Windows Command Prompt what do you get when you type "nslookup dimlights"? Also, try using a different browser in Windows 10, I believe it comes with Edge and Internet Explorer.
     
  3. Michael Gauthier

    Michael Gauthier New Around Here

    Joined:
    Mar 6, 2018
    Messages:
    8
    C:\Users\Mike\desktop>nslookup dimlights
    Server: router.asus.com
    Address: 192.168.1.1
    Name: dimlights
    Address: 192.168.1.62
    C:\Users\Mike\desktop>

    I tried Edge and this is the result:
    "Hmmm...can’t reach this page
    Try this


    So, this means it must be something in Windows because both browsers act the same way.
     
  4. ColinTaylor

    ColinTaylor Part of the Furniture

    Joined:
    Mar 31, 2014
    Messages:
    9,267
    Location:
    UK
    Check Windows' Internet Options > Connections > LAN settings. Make sure you're not using a proxy server.

    What router and firmware are you using?
     
  5. Michael Gauthier

    Michael Gauthier New Around Here

    Joined:
    Mar 6, 2018
    Messages:
    8
    It is not using a proxy server.
    The router is Asus RT-N12D1 And the firmware is 3.0.0.4.380_4180
     
  6. ColinTaylor

    ColinTaylor Part of the Furniture

    Joined:
    Mar 31, 2014
    Messages:
    9,267
    Location:
    UK
    I'm running out of ideas.

    What do you get from "ping dimlights"? Does the IP address match the one from nslookup? (I'm assuming that 192.168.1.62 is the correct address)

    Might be worth trying: ipconfig /flushdns
     
  7. Michael Gauthier

    Michael Gauthier New Around Here

    Joined:
    Mar 6, 2018
    Messages:
    8
    Ping dimlights returns:
    Ping request could not find host dimlights. Please check the name and try again.

    ipconfig /flushdns was no help.

    I just updated the router firmware to 3.0.0.4.380_8120 from 3.0.0.4.380_4180 and that did not help either.

    so nslookup dimlights finds it okay, but ping dimlights doesn't. At least that narrows it down a bit.

    Thanks for trying to help Colin!
     
  8. Michael Gauthier

    Michael Gauthier New Around Here

    Joined:
    Mar 6, 2018
    Messages:
    8
    Took your advice and posted the question on a Windows Networking forum. Thanks again.
     
  9. ColinTaylor

    ColinTaylor Part of the Furniture

    Joined:
    Mar 31, 2014
    Messages:
    9,267
    Location:
    UK
    You might want to try the answers here.

    The way Windows resolves names when you use a short name (without the domain part) is a bit cryptic. If you were to ping dimlights with a trailing dot I wouldn't be surprised if it worked. i.e.:

    ping dimlights.

    You might have an incorrect DNS suffix set in Windows. We might be able to spot it if you show us the output of:

    ipconfig /all

    Is/Was this PC part of a Windows domain?
     
  10. Michael Gauthier

    Michael Gauthier New Around Here

    Joined:
    Mar 6, 2018
    Messages:
    8
    This PC is a part of a local workgroup, not on a domain.

    Here is the output of ipconfig /all.

    Windows IP Configuration
    Host Name . . . . . . . . . . . . : Alien
    Primary Dns Suffix . . . . . . . :
    Node Type . . . . . . . . . . . . : Hybrid
    IP Routing Enabled. . . . . . . . : No
    WINS Proxy Enabled. . . . . . . . : No
    Ethernet adapter Ethernet:
    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Killer E2200 Gigabit Ethernet Controller
    Physical Address. . . . . . . . . : 34-E6-D7-88-05-28
    DHCP Enabled. . . . . . . . . . . : Yes
    Autoconfiguration Enabled . . . . : Yes
    Wireless LAN adapter Local Area Connection* 2:
    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
    Physical Address. . . . . . . . . : 72-77-81-5D-5B-FF
    DHCP Enabled. . . . . . . . . . . : Yes
    Autoconfiguration Enabled . . . . : Yes
    Ethernet adapter VMware Network Adapter VMnet1:
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet1
    Physical Address. . . . . . . . . : 00-50-56-C0-00-01
    DHCP Enabled. . . . . . . . . . . : Yes
    Autoconfiguration Enabled . . . . : Yes
    Link-local IPv6 Address . . . . . : fe80::7076:56ab:efdb:daa0%18(Preferred)
    IPv4 Address. . . . . . . . . . . : 192.168.222.1(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Lease Obtained. . . . . . . . . . : Wednesday, March 7, 2018 1:39:25 PM
    Lease Expires . . . . . . . . . . : Wednesday, March 7, 2018 5:54:11 PM
    Default Gateway . . . . . . . . . :
    DHCP Server . . . . . . . . . . . : 192.168.222.254
    DHCPv6 IAID . . . . . . . . . . . : 50352214
    DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-22-02-66-1B-34-E6-D7-88-05-28
    DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
    fec0:0:0:ffff::2%1
    fec0:0:0:ffff::3%1
    NetBIOS over Tcpip. . . . . . . . : Enabled
    Ethernet adapter VMware Network Adapter VMnet8:
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet8
    Physical Address. . . . . . . . . : 00-50-56-C0-00-08
    DHCP Enabled. . . . . . . . . . . : Yes
    Autoconfiguration Enabled . . . . : Yes
    Link-local IPv6 Address . . . . . : fe80::b818:718a:602c:a6eb%4(Preferred)
    IPv4 Address. . . . . . . . . . . : 192.168.184.1(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Lease Obtained. . . . . . . . . . : Wednesday, March 7, 2018 1:39:14 PM
    Lease Expires . . . . . . . . . . : Wednesday, March 7, 2018 5:54:11 PM
    Default Gateway . . . . . . . . . :
    DHCP Server . . . . . . . . . . . : 192.168.184.254
    DHCPv6 IAID . . . . . . . . . . . : 134238294
    DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-22-02-66-1B-34-E6-D7-88-05-28
    DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
    fec0:0:0:ffff::2%1
    fec0:0:0:ffff::3%1
    Primary WINS Server . . . . . . . : 192.168.184.2
    NetBIOS over Tcpip. . . . . . . . : Enabled
    Wireless LAN adapter Wi-Fi:
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Killer Wireless-n/a/ac 1525 Wireless Network Adapter
    Physical Address. . . . . . . . . : 70-77-81-5D-5B-FF
    DHCP Enabled. . . . . . . . . . . : Yes
    Autoconfiguration Enabled . . . . : Yes
    Link-local IPv6 Address . . . . . : fe80::8932:eff0:700e:6ba0%7(Preferred)
    IPv4 Address. . . . . . . . . . . : 192.168.1.95(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Lease Obtained. . . . . . . . . . : Wednesday, March 7, 2018 1:39:45 PM
    Lease Expires . . . . . . . . . . : Thursday, March 8, 2018 1:39:52 PM
    Default Gateway . . . . . . . . . : 192.168.1.1
    DHCP Server . . . . . . . . . . . : 192.168.1.1
    DHCPv6 IAID . . . . . . . . . . . : 40925057
    DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-22-02-66-1B-34-E6-D7-88-05-28
    DNS Servers . . . . . . . . . . . : 192.168.1.1
    NetBIOS over Tcpip. . . . . . . . : Enabled
    Ethernet adapter Bluetooth Network Connection:
    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
    Physical Address. . . . . . . . . : 70-77-81-5D-5C-00
    DHCP Enabled. . . . . . . . . . . : Yes
    Autoconfiguration Enabled . . . . : Yes
    Tunnel adapter Local Area Connection* 11:
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Microsoft Teredo Tunneling Adapter
    Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes
    IPv6 Address. . . . . . . . . . . : 2001:0:9d38:90d7:340e:be2:e731:27b1(Preferred)
    Link-local IPv6 Address . . . . . : fe80::340e:be2:e731:27b1%17(Preferred)
    Default Gateway . . . . . . . . . : ::
    DHCPv6 IAID . . . . . . . . . . . : 268435456
    DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-22-02-66-1B-34-E6-D7-88-05-28
    NetBIOS over Tcpip. . . . . . . . : Disabled
     
  11. ColinTaylor

    ColinTaylor Part of the Furniture

    Joined:
    Mar 31, 2014
    Messages:
    9,267
    Location:
    UK
    Well that looks OK. I can only suggest that you try some of the suggestions in the thread I linked to. Particularly this:

    netsh winsock reset

    (must be done with the command prompt "run as administrator")
     
  12. Michael Gauthier

    Michael Gauthier New Around Here

    Joined:
    Mar 6, 2018
    Messages:
    8
    Netsh winsock reset didn't help, but the suggestion to add a period to the hostname did work.
    I can just simply type "dimlights." and the server comes up!
     
  13. ColinTaylor

    ColinTaylor Part of the Furniture

    Joined:
    Mar 31, 2014
    Messages:
    9,267
    Location:
    UK
    By adding the period you are effectively using a fully qualified domain name (the domain is null), which forces Windows to resolve the name with DNS. Without the period Windows tries other methods (like NetBIOS and local hosts files).
     
    Last edited: Mar 7, 2018
  14. john9527

    john9527 Part of the Furniture

    Joined:
    Mar 28, 2014
    Messages:
    6,096
    Location:
    United States
    It looks like you you don't have a domain name specified on the router's LAN>DHCP Servers page. If you are unsure, a safe one to use is
    home.lan
     
  15. ColinTaylor

    ColinTaylor Part of the Furniture

    Joined:
    Mar 31, 2014
    Messages:
    9,267
    Location:
    UK
    :D I was just about to say the same thing. I have a vague recollection from way back that when your LAN doesn't have a domain name specified, Windows will not query DNS for short names. It relies entirely on /etc /hosts and NetBIOS.

    If my memory is correct then John's suggestion of creating a local domain should fix it. After rebooting all your clients of course.
     
  16. Michael Gauthier

    Michael Gauthier New Around Here

    Joined:
    Mar 6, 2018
    Messages:
    8
    I added the domain name home.lan and now it works without the '.' Thank much for the information.
     
  17. sfx2000

    sfx2000 Part of the Furniture

    Joined:
    Aug 11, 2011
    Messages:
    14,149
    Location:
    San Diego, CA
    On Windows - install ITunes - it includes a very good mDNS stack (Bonjour and Avahi for linux).

    Raspbian supports mDNS out of the box - so going to http://dimlights.local/ should work across most devices (except Chromebooks, long story there).