What's new

(Resolved) Differences in Chrome browser depending on the device

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Michael Gauthier

Occasional Visitor
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?
 
Why does this only happen on the Win 10 system?
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.
 
Check Windows' Internet Options > Connections > LAN settings. Make sure you're not using a proxy server.

What router and firmware are you using?
 
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
 
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!
 
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?
 
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
 
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")
 
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!
 
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:
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
 
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
: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.
 
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:

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).
 

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top