I can't see how you're trying to open it from your desktop

Are you actually opening a Chrome window and then typing in the address in the URL bar?

Post deleted by RobertoS

Oops ! Thanks.

Running Kaspersky.

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.

Ping to 192.168.1.254 timed out
Ping to 192.168.0.1 produced positive result

I'm using an ethernet connection to my router which is touchable distance away from me and the PC.

Ping to 192.168.1.254 timed out
Ping to 102.168.0.1 worked fine

In reply to a post by otterboy43:

Ping to 102.168.0.1 worked fine

192. perhaps?

You indirectly got the 192.168.1.254 ping from my typo'ed post, with a different router address. Oliver was correcting me, as you can see from the strike out and replacement in mine, and the valid one in my reply to him.

You have made almost exactly the same typo in your reply to Oliver with your ping that worked.

I actually duplicated a post for some reason, the first one was correct, and yes BatBoy I am opening my Chrome browser and keying the Ip address into the URL.

Are you prefixing it with http:// ?

I'm getting confused here. You and the OP seem to be chasing a non-existent rabbit. Though I would like to see the OP post a result from ping 192.168.0.1

Not just saying it is fine.