Cannot connect to WRT54GL

Soldato
Joined
3 Apr 2003
Posts
3,938
Location
InterZone
FOr the last couple of days I've not been able to connect to my Linksys WRT54GL. The router's SSID is being picked up but when I try to connect it just seems to time out. I'm currently using the latest Tomato firmware which I flashed to it after it stopped allowing me to connect whilst using the DD-WRT firmware, I was kind of hoping an upgrade would solve the problem.


Any ideas at all? I'm really stuck and I can't use my laptop or my 360 properly without it :(
 
I had to sort out my mates Linksys WRT54G the other day, only it wasn't the router that was at fault, he had set a static IP address on his network card that was below the routers IP range, eg: router starts at 192.168.1.100 but he had set the static IP to 192.168.1.1 which is the routers IP address for entering the web based setup and af course it's also the default cateway IP.

All i had to do was set his network card to obtain an IP and DNS address automaticaly and all was fine, i could have also set the IP address manualy to within the routers IP range, eg: 192.168.1.100, and also set the DNS server manualy to 192.168.1.1.

Anyway, try setting the network card to obtain an IP address and DNS server address automaticaly.

Hope this helps!
 
Try doing a hard reset and connecting via WIRE and set your laptop to dhcp and connect to the router using the default ip, username and password.
 
Connect (wired) and look at the logs for any event that may be related to your connection then if you can't see anything relevant do a hard reset
 
Well I got it sorted eventually. It seems that somehow my wireless card on my laptop was trying to connect to a different channel to the one being broadcast by my router. I changed it so it connects on channel 11 and it just connected straight away.

I guess a good thing about it stopping working is I learned something about how the wireless network operates. I didn't even realise there were "channels" involved although now I think about it it seems obvious that it should do in order to avoid confusion with other local wireless activity.
 
Back
Top Bottom