Accessing Sky Router using 192.168.0.1 from my Win 10 Deskto

Cannot access my Sky Router from my Win 10 Desktop using the usual 192.168.0.1. Keep getting the following:-

"This site can�t be reached

The connection was reset.
Try:
Checking the connection
Checking the proxy and the firewall
Running Windows Network Diagnostics
ERR_CONNECTION_RESET"

No problem from my old Win 7 Desktop or my iPhone or iPad. You'll probably say well use one of these three, but I prefer things to work as they should work. Has anybody had similar problems? and if so is there a simple fix?

Are you using Firefox? Have you tried a different browser?

open with IE instead of edge. you can use the three dots top right in edge to find the option.

I am using Chrome, and yes I have tried Edge and IE, but not Firefox.

Can you go to a command prompt, run "ipconfig /all" and paste the results here. That will show how IP is configured on the device and might give an idea of what is going wrong. Could also be that you might have firewall settings on Win10 blocking it but that wouldn't be default behaviour.

Thanks for your help Ian72. I'll check the Windows Firewall. I use Kaspersky Security which has its own Firewall and I thought this turned Windows Firewall off at installation but I'll check this out and post result

C:\Users\Malc>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : DESKTOP-6P6E65N
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : Home

Ethernet adapter Ethernet:

Connection-specific DNS Suffix . : Home
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physical Address. . . . . . . . . : 34-97-F6-D9-A8-77
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2a02:c7d:1ff0:a700:f8f2:cb6c:1038:5ac3(Preferred)
IPv6 Address. . . . . . . . . . . : fda4:cc6b:4f01:0:f8f2:cb6c:1038:5ac3(Preferred)
Temporary IPv6 Address. . . . . . : 2a02:c7d:1ff0:a700:9089:14eb:dbc0:3dfe(Preferred)
Temporary IPv6 Address. . . . . . : fda4:cc6b:4f01:0:9089:14eb:dbc0:3dfe(Preferred)
Link-local IPv6 Address . . . . . : fe80::f8f2:cb6c:1038:5ac3%6(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.0.2(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : 09 March 2017 20:05:12
Lease Expires . . . . . . . . . . : 10 March 2017 20:05:11
Default Gateway . . . . . . . . . : fe80::9201:3bff:fe26:b435%6
192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DHCPv6 IAID . . . . . . . . . . . : 322213878
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-20-07-45-78-34-97-F6-D9-A8-77
DNS Servers . . . . . . . . . . . : 8.8.8.8
8.8.4.4
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Ethernet 2:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Kaspersky Security Data Escort Adapter
Physical Address. . . . . . . . . : 00-FF-75-03-D2-39
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 10:

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:34ac:b067:20d6:1dd7:a52b:56b9(Preferred)
Link-local IPv6 Address . . . . . : fe80::20d6:1dd7:a52b:56b9%13(Preferred)
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 201326592
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-20-07-45-78-34-97-F6-D9-A8-77
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Reusable ISATAP Interface {85A9E7C2-CD19-45D9-B81B-DCB443386535}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : Home
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

C:\Users\Malc>

As I thought Windows Firewall is off and Kaspersky's is on.

OK, so you are on the right subnet. Can you ping 192.168.0.1? I don't use Kaspersky and wouldn't think it would have a rule to block the local router but could be worth checking.

EDIT : also try just clicking straight on http://192.168.0.1 and see if that does anything (just in case something funny is going on in the URL bar of your browsers - shouldn't make a blind but of difference but something weird is going on here).

Edited by ian72 (Fri 10-Mar-17 13:51:39)

My router is on 254, but I am running Kaspersky.

C:\Users\Bob>ping 192.160.1.254

Pinging 192.160.1.254 with 32 bytes of data:
Reply from 192.160.1.254: Destination net unreachable.
Reply from 192.160.1.254: Destination net unreachable.
Reply from 192.160.1.254: Destination net unreachable.
Reply from 192.160.1.254: Destination net unreachable.

Ping statistics for 192.160.1.254:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)

Which is perfect.

Should be:

C:\Users\Bob>ping 192.168.1.254

Pinging 192.168.1.254 with 32 bytes of data:
Reply from 192.168.1.254: bytes=32 time=2ms TTL=64
Reply from 192.168.1.254: bytes=32 time=4ms TTL=64
Reply from 192.168.1.254: bytes=32 time=2ms TTL=64
Reply from 192.168.1.254: bytes=32 time=4ms TTL=64

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

Still perfect - wifi in a steel-framed house with steel joists.

Edited by RobertoS (Fri 10-Mar-17 15:51:34)

In reply to a post by RobertoS:

C:\Users\Bob>ping 192.160.1.254

Did you mean to test 192.168.1.254 ?

Edited by Oliver341 (Fri 10-Mar-17 14:02:38)