View Single Post
Old 06-01-2025, 07:30 PM   #8
SteveEisenberg
Grand Sorcerer
SteveEisenberg ought to be getting tired of karma fortunes by now.SteveEisenberg ought to be getting tired of karma fortunes by now.SteveEisenberg ought to be getting tired of karma fortunes by now.SteveEisenberg ought to be getting tired of karma fortunes by now.SteveEisenberg ought to be getting tired of karma fortunes by now.SteveEisenberg ought to be getting tired of karma fortunes by now.SteveEisenberg ought to be getting tired of karma fortunes by now.SteveEisenberg ought to be getting tired of karma fortunes by now.SteveEisenberg ought to be getting tired of karma fortunes by now.SteveEisenberg ought to be getting tired of karma fortunes by now.SteveEisenberg ought to be getting tired of karma fortunes by now.
 
Posts: 7,424
Karma: 43514536
Join Date: Jun 2008
Location: near Philadelphia USA
Device: Kindle Kids Edition, Fire HD 10 (11th generation)
Here's how the problem appears to me:

For the last two days or so, I have been unable to get to mobileread using Verizon Fios WiFi. I have tried disabling OpenDNS, changing the browser, using the IP address, and powering down all devices in the house that have gone to mobileread.com except for the PC or tablet I am testing. On Chrome, the consistent message is "www.mobileread.com took too long to respond." I just downloaded waterfox and the message is "The connection has timed out" regardless of whether I put in the IP4 address or www. mobileread.com.

No other web sites seem to have the problem, and I do not recall these symptoms in the past.

Here is what I get with nslookup from my Windows 11 PC:

C:\Users\MyUserName>nslookup 162.55.243.172
Server: CR1000A.mynetworksettings.com
Address: 192.168.1.1

Name: www.mobileread.com
Address: 162.55.243.1

HOWEVER, I have no problem when using my Motorola Android phone on the Verizon cell network.
SteveEisenberg is offline   Reply With Quote