On Sunday, March 10, 2019 at 12:34:41 PM UTC-7, Robert in CA wrote:
On Sunday, March 10, 2019 at 6:01:53 AM UTC-7, Paul wrote:
Robert in CA wrote:
Boy, you won't believe what happened. I spent
2 hours getting blow off the Internet because
I couldn't connect to a DNS server. It turned out
to be my modem. Luckily I remembered I had a new
one and pulled it out and called and configured
it and now back in business...... whew!

Robert

Did you try power cycling the old modem first,
just to see if it would recover ?

Or did it keep doing that each time ?

It's possible the new modem was getting
DNS info from a different server at the ISP,
and that's why it worked better.

Paul



On Sunday, March 10, 2019 at 6:01:53 AM UTC-7, Paul wrote:
Robert in CA wrote:
Boy, you won't believe what happened. I spent
2 hours getting blow off the Internet because
I couldn't connect to a DNS server. It turned out
to be my modem. Luckily I remembered I had a new
one and pulled it out and called and configured
it and now back in business...... whew!

Robert

Did you try power cycling the old modem first,
just to see if it would recover ?

Or did it keep doing that each time ?

It's possible the new modem was getting
DNS info from a different server at the ISP,
and that's why it worked better.

Paul

I don't know what you mean by powering cycling
but I unplugged it from the outlet, and reset
it and tried to set it up with online support/
phone but it wouldn't accept the admin/password
but they eventually got it back up somehow but
then it crashed again (3) times.

I had to talk to support to get the old one setup
for DHCP and then once finished it started to
recognize everything and the guy stayed on the phone
to make sure all was well.

They were supposedly going to ship me a new modem
so it will be nice if it still comes so I can use that
as a backup.

Robert

I meant I had to talk to support to get the new one set up
for DHCP.

Robert