Alright, got a cable modem installed and hooked it up to my linksys wireless g router....I have 4 wireless connections hooked up. The other day, NONE of the computers would detect the wireless router....however, when i plugged into it, the connection worked fine...I went into settings, reset to default...and everything worked good. My roomate called today to say that he could get on the network...but it coulnt find the internet...So it said connected to access point, but cant to internet...
What is wrong now, he plugged his labtop into the cable modem and it worked fine...What is wrong with my cursed router.....It worked all year with my other service provider...and it is set up correct...
Any ideas?
Also, one of the computers can not locate the network unless the SSID is broadcasting. This is even when not using XP wireless config manager..
Help..Having trouble with wifi...
-
crazyjw1971
- Advanced Member
- Posts: 759
- Joined: Wed Dec 13, 2000 12:00 am
- Location: Clinton MD, USA
Go to Linksys' website and download the latest firmware for your router. MAKE SURE YOU GET THE CORRECT VERSION (ex. WRT54Gv1, WRT54Gv1.1. WRT54Gv2, WRT54Gv2.2)! Look under the bottom of the router and you will see a sticker identifying your router. Again, MAKE SURE YOU DOWNLOAD THE CORRECT FIRMWARE FOR YOUR MODEL OF ROUTER.
Have you done a reset lately? Are you running encryption? Are the clients set up to run encryption? Are you using MAC filtering? We need to know all of this stuff. Be prepared to answer...
Have you done a reset lately? Are you running encryption? Are the clients set up to run encryption? Are you using MAC filtering? We need to know all of this stuff. Be prepared to answer...
U.S. Department of Agriculture I.T. Specialist
Ducks, chickens, pigs, and mad cows need computers too!
A+, Net+, MCDST
Ducks, chickens, pigs, and mad cows need computers too!
A+, Net+, MCDST
Yes I have the latest firmware.
I am running mac filtering, along with 64bit wep encryption.
The router has been working fine throughout the year, I upgraded the firmware the day I got the cable installed, and since then nothing but problems.
I was going to try to flash an older firmware, but I have yet to locate it.
Any ideas?
I am running mac filtering, along with 64bit wep encryption.
The router has been working fine throughout the year, I upgraded the firmware the day I got the cable installed, and since then nothing but problems.
I was going to try to flash an older firmware, but I have yet to locate it.
Any ideas?
Been there...
I just went through all of this moving from Earthlink DSL to Comcast and it was a real pain in the neck.
I would NOT recommend flashing an OLDER firmware. If you have the latest one for your router, stick with that.
While I can't diagnose exactly what's going on with your network, let me just say that the installation of SP2 on XP made matters more difficult. I was also running Norton Internet Security, which has its own firewall.
The firewalls were ultimately the problem and the symptoms were much like yours. I also had WEP enabled. I never disabled the WEP but found that by disabling the firewalls (only one should be running in any event) the wireless clients were able to access the router and the internet. I am not using MAC filtering.
So, try disabling XP's Firewall and see what happens. Then you can re-enable it and try configuring it to pass through the requests. In my case, the XP firewall is disabled and Norton is providing the firewall and anti-virus.
Going back to the factory defaults on the router and then completely resetting all the WEP keys is also a major pain, but I did that as well (and I have two wireless access points plus the wired router.)
Another major bone of contention was the apparent reluctance of a cable connection to accept anything but a dynamic (DHCP) setup that lets the router and everything else on the network get the proper DNS server addresses and IP address. The kids at Comcast were no help. They declined to give me the DNS addresses citing their own 'network service' that I could pay to have configured.
One by one, I went through the computers and stuck with DHCP whenever it wasn't critical. Still, some of the addresses on my network MUST be static and that was where I had to go to a machine that was on DHCP and do an
ipconfig /all
from the command prompt in order to see EXACTLY what were the DNS servers. Then, I entered static addresses on the machines/devices that need that and entered those DNS server addresses manually.
IPCONFIG revealed that some of my computers were still trying to use the old DSL DNS suffix search list. In other words, earthlink.net showed up instead of comcast.net
I had to DELETE those connections and start over with new connections. One of the "wonders" of XP is that it never seems to forget a connection. You end up with 'Local Area Connection 5' when you actually only are using one...and have deleted 4 others.
On one machine, I ended up just re-installing XP to finally get it sorted out.
My Linux server seemed to have far fewer problems "adapting" to the change from DSL to cable than anything else running.
Can't help you with the "broadcast SSID" issue. I still broadcast my SSID but have changed the name, of course, from the default...linksys. (I've got two other 'linksys' SSID's showing up from the neighbors!)
Hope that helps!
I would NOT recommend flashing an OLDER firmware. If you have the latest one for your router, stick with that.
While I can't diagnose exactly what's going on with your network, let me just say that the installation of SP2 on XP made matters more difficult. I was also running Norton Internet Security, which has its own firewall.
The firewalls were ultimately the problem and the symptoms were much like yours. I also had WEP enabled. I never disabled the WEP but found that by disabling the firewalls (only one should be running in any event) the wireless clients were able to access the router and the internet. I am not using MAC filtering.
So, try disabling XP's Firewall and see what happens. Then you can re-enable it and try configuring it to pass through the requests. In my case, the XP firewall is disabled and Norton is providing the firewall and anti-virus.
Going back to the factory defaults on the router and then completely resetting all the WEP keys is also a major pain, but I did that as well (and I have two wireless access points plus the wired router.)
Another major bone of contention was the apparent reluctance of a cable connection to accept anything but a dynamic (DHCP) setup that lets the router and everything else on the network get the proper DNS server addresses and IP address. The kids at Comcast were no help. They declined to give me the DNS addresses citing their own 'network service' that I could pay to have configured.
One by one, I went through the computers and stuck with DHCP whenever it wasn't critical. Still, some of the addresses on my network MUST be static and that was where I had to go to a machine that was on DHCP and do an
ipconfig /all
from the command prompt in order to see EXACTLY what were the DNS servers. Then, I entered static addresses on the machines/devices that need that and entered those DNS server addresses manually.
IPCONFIG revealed that some of my computers were still trying to use the old DSL DNS suffix search list. In other words, earthlink.net showed up instead of comcast.net
I had to DELETE those connections and start over with new connections. One of the "wonders" of XP is that it never seems to forget a connection. You end up with 'Local Area Connection 5' when you actually only are using one...and have deleted 4 others.
On one machine, I ended up just re-installing XP to finally get it sorted out.
My Linux server seemed to have far fewer problems "adapting" to the change from DSL to cable than anything else running.
Can't help you with the "broadcast SSID" issue. I still broadcast my SSID but have changed the name, of course, from the default...linksys. (I've got two other 'linksys' SSID's showing up from the neighbors!)
Hope that helps!
reader
_________________________
_________________________
If your computers are seeing the network but aren't seeing the internet, AND you're able to connect when one computer is hooked directly into the modem, it may be a case of where the modem has locked into the mac address of the one computer hooked up directly.
Try unplugging the power from the cable modem, reconnect to the router, then re-apply power to the modem. Then power cycle the router to force the ip to pull. See if that helps
Try unplugging the power from the cable modem, reconnect to the router, then re-apply power to the modem. Then power cycle the router to force the ip to pull. See if that helps
------
“The most beautiful thing we can experience in life is the mysterious. It is the source of all true art and science. He to whom this emotion is a stranger, who can no longer pause to wonder and stand rapt in awe, is as good as dead: for his eyes are closed.” - Albert Einstein
“The most beautiful thing we can experience in life is the mysterious. It is the source of all true art and science. He to whom this emotion is a stranger, who can no longer pause to wonder and stand rapt in awe, is as good as dead: for his eyes are closed.” - Albert Einstein