Bookmark this page:
Yahoo!
Windows Live
del.icio.us
digg
Netscape
|
|
||||||||||||||||||||||||||||||||||
|
Posted by Bob Willard on March 4, 2008, 9:16 am
Please log in for more thread options Linksys WRT54G v2 router (v4.20.7 µCode), tied to WAN via Moto SB 4200 to Comcast. Symptom 1: Could not send or forward long (>1000 bytes) emails
from Moz v1.7 on wired XP PRO PC: after ~60 Secs, Moz reported
failure to connect to smtp server; but, short (<200 bytes) emails sent OK. Same problem with Moz v1.7 on wireless XP MC PC, and same problem with Netscape v7.1 on wired W98 PC. No problem with WinMail on wireless Vista PC at any message size. Symptom 2: Could not connect to some websites with either FF v2 or IE v7 from wired XP PRO PC: connections timed out. I think the common factor was using https instead of http, but I'm not really sure. Aside: transfers of up to 1 MB uphill and up to 16MB downhill via FTP work OK, and at full speed; no sign of errors. Solution: power down the router for >3 minutes, then power back up.
long enough to clear the problem, but a surprisingly long power-off
Note that powering down for >20 seconds (tried twice) was *not* period (while I temporarily bypassed the router) did the job. Weird, huh? Maybe this 3-year old router has Alzheimer's? -- Cheers, Bob | ||||||||||||||||||||||||||||||||||
|
Posted by Bill Kearney on March 4, 2008, 12:21 pm
Please log in for more thread options > Solution: power down the router for >3 minutes, then power back up.
> Note that powering down for >20 seconds (tried twice) was *not* > long enough to clear the problem, but a surprisingly long power-off > period (while I temporarily bypassed the router) did the job. > > Weird, huh? Maybe this 3-year old router has Alzheimer's? Long timeouts like that sound more like there's gear UPSTREAM at the ISP that has to timeout, not this equipment. Try this, instead of powering it off, physically DISCONNECT it from the cable modem. Wait that 3 minute period, reconnect it and see if the "problem" went away. I'm guessing it will. That being the case there are other debug steps to consider. | ||||||||||||||||||||||||||||||||||
|
Posted by Bob Willard on March 4, 2008, 1:56 pm
Please log in for more thread options Bill Kearney wrote:
>> Solution: power down the router for >3 minutes, then power back up.
>> Note that powering down for >20 seconds (tried twice) was *not* >> long enough to clear the problem, but a surprisingly long power-off >> period (while I temporarily bypassed the router) did the job. >> >> Weird, huh? Maybe this 3-year old router has Alzheimer's? >
> > Long timeouts like that sound more like there's gear UPSTREAM at the ISP > that has to timeout, not this equipment. Try this, instead of powering > it off, physically DISCONNECT it from the cable modem. Wait that 3 > minute period, reconnect it and see if the "problem" went away. I'm > guessing it will. > > That being the case there are other debug steps to consider. Interesting. I can't tell the diff, since the router was both powered down and uncabled. And, the problem has gone away (for now). -- Thanks & Cheers, Bob | ||||||||||||||||||||||||||||||||||
|
Posted by Bill Kearney on March 4, 2008, 3:53 pm
Please log in for more thread options > Interesting. I can't tell the diff, since the router was both powered
> down and uncabled. And, the problem has gone away (for now). Here's a thought, what other traffic was being routed through it? Is it an open wifi network? Might've been something else hammering a ton of traffic through the link and that tripped something on the ISP's side of things. | ||||||||||||||||||||||||||||||||||
|
Posted by Bob Willard on March 4, 2008, 6:38 pm
Please log in for more thread options Bill Kearney wrote:
>> Interesting. I can't tell the diff, since the router was both powered
>> down and uncabled. And, the problem has gone away (for now). >
> > Here's a thought, what other traffic was being routed through it? Is it > an open wifi network? Might've been something else hammering a ton of > traffic through the link and that tripped something on the ISP's side of > things. > The WiFi segment is secured with WPA, and usually pretty light anyway. The bulk of my LAN traffic is on the wired side, including a gamer (sometimes 2). But the traffic wasn't unusually heavy when the router went funny. I'm holding my breath, to see if the router (or whatever) goes awry again. This Linksys router is ~3 years old, and the previous router (Linksys) lasted for ~5 years before the radio front-end died. -- Cheers, Bob | ||||||||||||||||||||||||||||||||||
| Similar Threads | Posted |
| Strangeness with Linksys WRT54G | March 4, 2008, 9:16 am |
| Linksys WRT54G vs Linksys WRT54GS | November 14, 2006, 12:03 pm |
| LINKSYS WRT54G--HELP! | May 12, 2005, 12:57 am |
| Linksys WRT54G $59.00 | February 25, 2005, 3:07 pm |
| Linksys WRT54G | April 5, 2005, 12:12 am |
| VPN with Linksys WRT54G v5 | January 17, 2006, 6:04 pm |
| LINKSYS WRT54G | March 5, 2006, 11:42 pm |
| Linksys WRT54g | October 28, 2006, 3:20 pm |
| dd-wrt for Linksys WRT54G v6 | December 28, 2006, 9:24 am |
| Linksys WRT54G vs GL vs GS | June 23, 2007, 8:01 pm |
| Linksys WRT54G issue | October 18, 2004, 12:30 pm |
| Linksys WRT54G WPA problem... | November 11, 2004, 7:48 pm |
| Linksys WAP54G v. WRT54G - Which one? | December 7, 2004, 5:43 am |
| Linksys WRT54G & ?Bridging? | February 6, 2005, 8:16 pm |
| Using the Linksys WRT54G as a client ? | June 4, 2005, 1:22 pm |

Strangeness with Linksys WRT54G
Yahoo!
Windows Live
del.icio.us
digg
Netscape 






