L
Larry Grant
There is a problem that only hits me now and then, but when it does it
drives me batty. I have a Win2K Server system connected to a Netgear
router, in turn connected to a DSL modem (Verizon). (The router is
mainly for there to act as a firewall, but I occasionally connect
another machine to it, to share the DSL connection.) Everything
usually works perfectly. However, every once in a while (roughly
every month or so), the DSL connection gets extremely slow, but I can
tell it is still working somewhat.
A typical symptom is that I will try to go to a web page, I will get
"Connecting to whatever.com ..." on the status line of the browser,
nothing will happen for about 20 seconds, then I'll see that title of
the browser changes to reflect the title of the page (that's how I
know it's somewhat working), but then after more waiting, I'll get
"Page cannot be displayed". All sites act in a similar way.
The only cure I've come up with is to power everything down, wait a
while, then power things up one by one. However, unfortunately, this
does not always work the first time, and I have to repeat it. I've
called Verizon and they say they have not been having any network
problems that would cause that behavior.
Any ideas?
Thanks,
Larry
drives me batty. I have a Win2K Server system connected to a Netgear
router, in turn connected to a DSL modem (Verizon). (The router is
mainly for there to act as a firewall, but I occasionally connect
another machine to it, to share the DSL connection.) Everything
usually works perfectly. However, every once in a while (roughly
every month or so), the DSL connection gets extremely slow, but I can
tell it is still working somewhat.
A typical symptom is that I will try to go to a web page, I will get
"Connecting to whatever.com ..." on the status line of the browser,
nothing will happen for about 20 seconds, then I'll see that title of
the browser changes to reflect the title of the page (that's how I
know it's somewhat working), but then after more waiting, I'll get
"Page cannot be displayed". All sites act in a similar way.
The only cure I've come up with is to power everything down, wait a
while, then power things up one by one. However, unfortunately, this
does not always work the first time, and I have to repeat it. I've
called Verizon and they say they have not been having any network
problems that would cause that behavior.
Any ideas?
Thanks,
Larry