1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

WRT54GL suddenly stopped working correctly.

Discussion in 'Cisco/Linksys Wireless Routers' started by FurtiveDog, Dec 18, 2006.

  1. FurtiveDog

    FurtiveDog Guest

    A cordless phone was placed near it (around a foot away), about 10 minutes before it stopped, but I don't see how that could have caused the actual problem.

    It's still providing DHCP to my local network, but it's not picking anything up from my ISP (cable connection which uses DHCP). Connecting the cable modem directly to a PC proves that my ISP is not at fault.

    A "firmware default" reset didn't help. Problem continues.

    It had DD-WRT firware on it, but replacing the firmware with the current Linksys standard version (4.30.5) didn't work. Same issue.

    The very interesting thing is, the cable modem WAS connected to the "internet" port (WAN port) of the router. Placing the cable modem into one of the standard LAN ports allows a cabled PC to connect to the internet, but not a wireless PC. Also, when connected this way, the PC appears to get it's IP directly from my ISP, not from the router's DHCP server.

    Any asssistance would be greatly appreciated.
     
  2. ka9yhd

    ka9yhd LI Guru Member

    Try doing a reset by holding in the reset button for 30 sec. Then you will need to re-enter your settings.

    I had to do that with my WRT54GL ver. 1.1 with the Linksys firmware on it. It stopped communicating with my ISP and I am using PPPoE with a DSL line. It was strange, it would get the DNS entries from the ISP but the ip address would show as all zeros. Other times everything was blank, no DNS entries and the ip address as all zeros.
     
  3. ifican

    ifican Network Guru Member

    Indeed try another reset. It connects with the cable modem connected to the lan ports because its just a switch at that point. The other thing to do is test the wan port itself. Do you get any lights when connecting the cable modem? Lots of stuff come to mind, the mdix function could have just died, so you might need a crossover, the autonegotiate died so you need to set it manually, there could be any number of things thats causing it, none very common but all possible. The cordless phone places next to the unit if it is on the same frequency 2.4ghz could have caused it some trama. However if it was a different freq it should have been fine.
     

Share This Page