Dchp

ramdex

Ok i was wondering if i should go ahead and turn off the dchp to the computers on the network and then set it up from the computer or just leave it on dchp and tset it up or if i should just. If i turn it off and something happens where i i cant get into the router how would i be able to reset the router to factroy defaults or get it back to dchp mode enabled if i cant get into it from a comp on the network?

drowd

there is no real problem with leaving dhcp (i assume thats what you mean) on, unless there is some reason you would like for it to be off. for instance, if there is one of the computers on your network that you want to be in the DMZ (demilitiarized zone), then you dont want the ip address assigned to that machine to change (as they will occasionally do either through poweroff or reset). but even then, you dont necessarily have to turn dhcp off. in terms of accessing your router, there should be a static ip that you can reach through internet explorer (i believe linksys is always 192.168.1.1 by default and netgear is 192.168.0.1 by default). that shouldnt change with dhcp. you can also change that address usually in the routers set up. and as far as not being about to reaccess the router, if something DOES happen to where you cant access it for some reason, most routers have an external reset switch that you can use (it is on the very front for linksys routers). i hope this helps . . .

ramdex

ok so i can just leave it on and then configure the comp to use a certain ip ie 192.168.1.102 it will always use that one even with dchp on? Other then that i see what you mean and thanks.

drowd

yes. a computer's static ip usually takes precedence over a dhcp server trying to assign it an ip address.

EMT

A static IP will always take precedence over DHCP. It just says " I Am [Your Static IP] " and everything else has to deal with it. Problems would arise if DHCP happened to also choose that IP to give out to another host, or if another statically configured computer accidentally got the same one. Then neither computer would work right.

So the simple solution is to pick an uncommon IP. My local IP is .152 for instance because DHCP starts at 100. Not likely for anything to interfere. And then all the router settings can be left at .152 and it doesn't have a problem.

Enverex

Originally posted by EMT
Then neither computer would work right.

Actualy both machine will get a warning message and, depending on the client/server software, the newer machine should be reassigned automatically.

In Windows you cant set it to use DHCP AND a static IP address as the static address has to be set first and if it is set then DHCP is turned off. BUT it can work the other way, i.e. it looks for a DHCP server, if it doesnt find one then it falls back onto an IP address that (you) have pre-set (Windows 2000 & XP only).

If you dont set one then it will assign an (almost) totaly useless private address.

NS

MrBill

You should be able to set the range for the DHCP pool.

Example: I have my range set from .100 to .110. I can then assign static IP addresses outside of that range to be sure there is no chance of DHCP assigning an address already in use.

gerignyg

You could also exclude the static ip in your dhcp-scope.
Why do something easy, when it can be done difficult:)

Saytinex

Originally posted by gerignyg
You could also exclude the static ip in your dhcp-scope.
Why do something easy, when it can be done difficult:)

While you're at it, configure the server to assign a specific IP (outside the DHCP lease) to the client system's MAC address. Then the client can leave DHCP settings on and the server would always assign the specified IP to said client system.