slow router

[hanratty21]

ihoss - if you have a mixed mac/pc environment, you should NOT be using DHCP. I went through many problems until I made that change. Statuc IP's are almost a necessity as OSx macs seem to want to grab other IP's being used by other PC's on the network. This causes conflicts which a residential grade router will always have problems (see: slowness) recovering from. I've gone through this problem with several different brand of router (linksys, netgear, etc.)

For DNS server, each machine on your network should have your router's IP set as their DNS server, while the router should have the public DNS (preferably the one that your ISP provided to you) as it's DNS server. This way, you have a single point to change if your DNS ever changes. Your computers will always contact the router for DNS service and the router will always know to send that request off to the same place everytime.

RH

[PAlexC]

While we're on the topic, my Netgear CG814M is sh*tting the bed when it comes to wireless connectivity. Using 64-bit WEP with MAC filtering on the wireless connection, static IP's all around except for the wired machine. (Static IP's are pulled from outside the DHCP range of IP's.)

After 20 minutes or so the connection will drop and my laptop won't be able to re-connect unless I restart the router. Same with my roommate's. The laptops can find the network and attempt to connect, it just always fails. This thing worked flawlessly before I moved. No firmware updates available.

It's especially a pain because when re-starting, the built-in cable modem gets stuck 9 times out of 10 on 'Waiting for DHCP offer' from the WAN, and sometimes takes 30 minutes up to a couple hours to reconnect.

Should I just pitch it?

[hanratty21]

While we're on the topic, my Netgear CG814M is sh*tting the bed when it comes to wireless connectivity. Using 64-bit WEP with MAC filtering on the wireless connection, static IP's all around except for the wired machine. (Static IP's are pulled from outside the DHCP range of IP's.)

After 20 minutes or so the connection will drop and my laptop won't be able to re-connect unless I restart the router. Same with my roommate's. The laptops can find the network and attempt to connect, it just always fails. This thing worked flawlessly before I moved. No firmware updates available.

It's especially a pain because when re-starting, the built-in cable modem gets stuck 9 times out of 10 on 'Waiting for DHCP offer' from the WAN, and sometimes takes 30 minutes up to a couple hours to reconnect.

Should I just pitch it?

Loving the new avatar.

Question - why are you mixing DHCP and non-DHCP in the same environment? To say this in a language that you'll understand:
Sh*t or get off the pot. DHCP or Static -- pick one and stick with it. This may not solve the problem, but why create more complexity than you need?

Also, to test...have you tried disconnecting the wired machine(s) for a period of time to see if you still experience the same issues with your wireless connections)? Try it...see what happens.

p.s. I see lots of complaints about this model: http://www.amazon.com/gp/product/B00...lance&n=172282

[PAlexC]

DHCP range is 10-11, wireless devices use 101-104 manually assigned, I thought that was ok to do?

I used to use DHCP exclusively, but sometime after SP2, which was near after I moved in, I started having problems. Then I went static, still problems.

It worked fine for the first year I had it on Comcast, not so much once I moved and got Optimum. I don't think I ever restarted it before that unless I made a change that required it. I didn't think devices like this 'just went bad', but I guess I'm wrong.

Come to think of it, this place gets hotter in the summer during the day when I'm not home...