willieej2002 wrote:Thats exactly what I thought. However, why have DHCP enabled whenever it wouldn't be handing out IP addresses? Or does DHCP do more than that and I just dont realize it?
fpthree: Hmm, if I am recieving the new IP address through the router, and its not getting delivered to my PCs, then how are members still able to access my web server via my domain name which is still configged to 216.176.66.240?
I checked my router config page, and it says that my WAN IP is stilll 216.176.66.240, and it also says that my gateway is the same as it was last week. How can I check to see if my WAN IP has changed and I don't realize it?
Btw, I dont use PPPoE. Its configured for "dynamic / DHCP" config from the ISP. I called them a few weeks ago to check on this, and they claimed that they do not use PPPoE.
-Just a note: Im not trying to prove anyone wrong or be witty, Im just curious as to why this behavior began after I manually configured static LAN IPs. I'm really thinking its just a coincidence that this stuff hasn't updated, and sooner or later its just going to hit me by surprise that my IP changed.
-Willie
Leaving DHCP enabled for the LAN side can be good for people not totally comfortable with TCP, how it works. Say someone has their computer set to "obtain auto", and disable DHCP on the router. Suddenly they can't log onto the routers web admin page because they're getting a 169.254.xxx.xxx IP address, and don't know enough to change their IP to whatever matches the LAN scope of the router. That's why I always recommend to just assign static LAN IPs outside of your routers DHCP range. New users have that "safety net" to fall back on.
Quick guide on static LAN IPs behind a router.
http://www.speedguide.net/read_articles.php?id=177
The basic DHCP service of a router really doesn't do much more that you're not realizing...just IP, subnet, gateway, and DNS, some routers allowing WINS entries too.
There are some 3rd party utilities which can be setup to e-mail you if your WAN IP changes. Also there are dynamic-DNS packages, many routers support them, which work with dynamic IPs and DNS names...so you can always get to your home LAN via DNS name even if your IP changes frequently.
Not PPPoE huh? Probably have a Bridged (RFC 1483) DSL, that's what I have at home. Just set the WAN interface to "Obtain Auto" and you're good to go, no username or password at all. Smaller ISPs use this more often, and you do tend to have the same IP address "most of the time" because their pool is so small, and lease times very long. But unless you have an agreement with your ISP...it's not guaranteed not to change, if you NEED a static IP address...you NEED to get a static IP account with your ISP. I can have the same WAN IP for a month or two or three...then sometimes a different IP, then back to my other IP for another few months. Versus many clients that I have, that just have regular DSL through the local phone company...with a HUGE IP pool, and very short lease times. Dynamic accounts get different IPs at regular short intervals with larger ISPs.
When you check your WAN status, your remote gateway usually (almost never) will change, even if your WAN IP address changes. That remote gateway...that's your ISPs main router to the internet...that's something they really don't change, it's there for good.
I agree with your last note...it's just happens that your WAN IP has been the same recently. Or perhaps you had a setting on your router that is now set to "maintain connection" instead of "connect on demand". With connect on demand, it will let go of the IP when not in use, and ask for a new one when in use. Maintain connection will try to keep that connection 24/7, so it more likely to keep the same IP until the lease is up.