why do I have to reset my router every once in a while?

[Semidevil]

I just bought a wireless router a week ago and it worked fine for the past week or so. However, now, it seems that I have trouble connecting wirelessly every once in a while. My wireless device detects the router but will not be able to connect. The only way to solve this problem is if I unplug my router and plug it back in. I find that I have to do this once every day.

What's going on and how do I fix it?

Thanks.

wireless router is linksys wrt120N

 

[ChAoTiCpInOy]

Clear the cache?

 

[sonoma1993]

check on linksys website to see if there are any firmware updates for your router.

 

[jlazzaro]

because that router is crap...my parents bought it without asking me first and had to constantly power cycle it. since they had no need for wireless N, a Buffalo WHR-HP-G54 replaced it.

 

[onza]

I would RETURN it and find a DD-WRT/Tomato compatible router instead.

STRONGLY suggest you do this.

 

[RadiclDreamer]

Upgrade your firmware and see if it helps.

http://downloads.linksysbycisco.com/downloads/firmware/1224646102739/FW_WRT120N_1.0.04.002.bin

 

[Rifter]

I would RETURN it and find a DD-WRT/Tomato compatible router instead.

STRONGLY suggest you do this.

This X2, my WRT54GL had a issue where i would need to reset it many times per week, after flashing to tomato its been up 230+ days strait with no issues at all, and i got it for $25 on sale.

 

[Semidevil]

okay, I think I plan to return the wireless router and get another one. I read the reply about flashing to tomato, but first, I would like to get one that has no issues to begin with. Any brand is fine. Linksys, belkin, etc etc.

what are your suggestions?

 

[Engineer]

okay, I think I plan to return the wireless router and get another one. I read the reply about flashing to tomato, but first, I would like to get one that has no issues to begin with. Any brand is fine. Linksys, belkin, etc etc.

what are your suggestions?

Just a FYI..Tomato doesn't run on N routers (yet). DD-WRT is limited on N routers but getting better.

For a Tomato router, go with what Jack recommends and that would be an Asus WL-520GU or BUFFALO WHR-HP-G54. Both are excellent (Buffalo supposedly has a very good stock firmware) with Tomato and I presume DD-WRT.

Good luck

 

[Perryg114]

Well I bought a Buffalo WHR-HP-G54. The stock firmware was crap for my needs. I flashed Tomato and problems went away. The Buffalo stock firmware was supposed to be good and recommended by folks on this forum. I think the quality of stock firmware sucks on pretty much any router these days. It seems strange when a D-link Router (my old one) made in 2003 has better firmware than the latest and greatest. At least Buffalo tech support is US based unlike D-link whose tech support is in BF India.

Perry

 

[Emulex]

ram leaks in dd-wrt and stock firmware - bittorrent will find them quick. you could setup a cron job to reboot the router once a week i spose if you can't afford a router with enough ram to handle your workload

 

[Engineer]

Well I bought a Buffalo WHR-HP-G54. The stock firmware was crap for my needs. I flashed Tomato and problems went away. The Buffalo stock firmware was supposed to be good and recommended by folks on this forum. I think the quality of stock firmware sucks on pretty much any router these days. It seems strange when a D-link Router (my old one) made in 2003 has better firmware than the latest and greatest. At least Buffalo tech support is US based unlike D-link whose tech support is in BF India.

Perry

Good to know on the Buffalo stock firmware. Also, thumbsup to Tomato! :thumbsup:

 

[onza]

CASE CLOSED

Enjoy your stable new router.

 

[Perryg114]

Good to know on the Buffalo stock firmware. Also, thumbsup to Tomato! :thumbsup:

Specifically, I had problems with UPnP and port forwarding not working well with the Stock Buffalo firmware. It would do basic WiFi and Router Functions for accessing the net but that was about all it was good for.

Perry

 

[RadiclDreamer]

Try updating the firmware as mentioned above before you return it, could just be a bug.