gmh4
join:2000-08-04
West Palm Beach, FL
| BEFSR11 hanging
Hi I would like to know if anyone else has experienced similiar problems to this with there router.
I have the 1 port linksys BEFSR11 firmware is 1.385
I have linksys lne100tx nic connecting to a linksys 5 port switch connecting to the router
Using PPPOE
My connection is fast everything works fine but eventually cant connect to sites ,I am not able to connect on demand and I have to manually go into the router setup and connect. After I connect I have extreme slowdows and cannot access anything until I disconnect the power to router and plug it back in. |
|
wguimb
join:2001-04-29
Houston, TX
 ·Comcast
| In the Linksys setup, turn on "Keep Alive: Redial period = 180 sec." if it is not already on. Or try "Connect On Demand: Max Idle Time = 0".
I have a BEFSR11 also but not using PPPoE. However, occasionally my router freezes and I have to reset the power on it to clear the problem. This has happened with every firmware from 1.37 to 1.38.7. I am now trying 1.39. so far so good. |
|
bbier
Retired G.I., Member T.V.R.W.C.
Premium
join:2000-11-25
Centralia, WA |  reply to gmh4
I have the same set up that you do, except my NIC's are Kingston's. My setup just sits there and runs. I have PPOE enabled. "Keep Alive: Redial period = 30 Sec.". I am also running version 1.39. |
|
Linksys Tech_3
join:2001-04-20
Irvine, CA
| reply to gmh4
one thing i have customers do is go to dos and use the following command:
C:\WINDOWS\DESKTOP>ping -t 216.32.74.50
Pinging 216.32.74.50 with 32 bytes of data:
Reply from 216.32.74.50: bytes=32 time=71ms TTL=242
Reply from 216.32.74.50: bytes=32 time=69ms TTL=242
Reply from 216.32.74.50: bytes=32 time=70ms TTL=242
...
the pings will continue until the ctrl+c command is used to stop them. the statistics will display. typically there may be some loss, but no more than 5-10%
also create another dos window and do a ping -t to a well known domain name, such as yahoo or google, as they are always up, and reply to pings.
if the ip address portion has significantly less packet loss, you may want to statically assign the dns servers to the router and in the tcp/ip properties. this may help out some with the inablility to access websites. also when unable to connect to sites, try using the ip address equivalent. here are some sites to try using the ip address instead of domain name:
»216.23.162.142 - www.linksys.com
»216.32.74.50 - www.yahoo.com
»64.209.200.100 - www.google.com
»208.196.145.21 - www.faqs.org
»199.172.136.40 - www.ieee.org
-ian
--
welcome to california. home of the world's 6th largest economy, powered by a third world power grid. |
|
wguimb
join:2001-04-29
Houston, TX
·Comcast
| When the Linky locks up, all pings die regardless of where they are directed (DNS is not the issue here). The thing locks up tighter than Fort Knox. I put 1.39 on last night, hoping for some relief. Still locks up, except more frequently now. Arrggghhhh.
It's important to note, the lock ups occur during periods of high bandwidth utilization. It leads me to think it is either firmware or hardware related. Could it be that the Linky needs more RAM or buffers to handle customers such as myself that consume mass quantities of bandwidth? If Linksys does not do something about this soon, I feel the product line is doomed in the market place. And that would be such as shame since it is otherwise a fine device. |
|
