Posted: 6/8/2005 8:55:16 AM EDT
|
Just thought I'd try to get some insight on this issue. I've got a Comcast cable connection for my internet uses, which is facilitated via Motorola SurfBoard cable modem. This hooks into a Linksys WRT54AG router. Two systems access the router, my base PC via ethernet connection and my laptop via wireless connection (Linksys PCMCIA card). Both systems run Windows XP Professional SP2. The router has been reconfigured, such that it uses a different IP than default, different SSID (non broadcast), signal encryption, and only authorizes connections from specific IP addresses. The problem is this....every so often, though what seems to be with increasing frequency, I'll pop on to the system and though everything 'seems' to be connected, I can't access the internet. The only thing that usually fixes it is to power off both the router AND the modem, then power them back up (cycling the modem itself does no good). Now, this tends to be problematical for a number of reasons, not the least of which is my system is pretty much designed to run 24/7...thankfully not for any important purpose, but I do a lot of bittorrent transfers (mostly unlicensed anime). I also just like the convenience of just dropping into the chair and going right to work on the system without waiting for booting to complete. So....anyone have any ideas on what might be causing this? Owing that resetting the cable modem doesn't do the trick I'm thinking it might not be a cable connection issue but something with the router, or possibly the communication between the router and cable modem (all signals on the cable modem indicate a steady connection). Any thoughts? |
|
What type of connection is it? PPPoE, Static IP...etc? First of all, make absolutely sure the firmware on the router is the absolute newest that linksys has available. Also, what is the connection option set at - Connect on Demand or Keep Alive....? If it is set at Connect on Demand, set the idle timeout to 9999, if you havent allready done so. If you are allready using connect on demand, set it up for Keep Alive, and see if that does anything. |
|
If your running a single connection with Comcast, the modem will only allow one system/link (single computer). The modem will connects to comcast with it own IP adrress, then the IP address of the system hooked up to it. This means every once in a while, the modem thinks that the server/computer is a differnt/additional system and will not allow it connect to the Comcast server. To resolve this, you will have to unplug the moden for 30 sec to allow it to reset. Again, the problem is the moden and the single user comands/addressing in it (read comcast wanting to charge for extra users). Now the good news, if you have a firewall box in between your network and the comcast modem (single user sevice), then nothing really stopping you from running something like Netproxy on the server to allow the single user modem to run the net work*. *Comcast really frowns on this, so best not to run more than a few systems connection with the net at one time. |
Yep. The only 'computer' the cable modem should see is the WRT54AG, which will get typically get its IP via DHCP from the modem. NAT should take care of everything in the network behind the WRT54AG. What IP did you assign to the WRT54AG? Is it in the 192.168.x.x, 10.x.x.x, or 172.16.x.x range? How do your network clients obtain their IP addresses? Is it via DHCP from the WRT54AG, or are IPs configured statically? |