DHCP automatic IP address v Static IP
Archive - Originally posted on "The Horse's Mouth" - 2007-08-06 07:34:27 - Graham Ellis"My system chose its own IP address ... does it matter?" From Skype - a fresh server (a real "beast") is just being commissioned:
newsystem 06/08/2007 07:22
okay, this beastie has powers beyond my full comprehension. Firstly, it has two ethernet ports. secondly, it automatically chose an IP address. I did no setting up; just plug and play.
06/08/2007 07:23
naturally, it did not like the ip addy you gave it, so it chose 21
06/08/2007 07:23
I cannot see (at first look) how to change its mind on this
wellhograham 06/08/2007 07:24
I doubt whether IT chose 21. It's probably set up to "DHCP" which means it shouts on our network "who am I" and our router gave it that number. You need to say "manual IP" not "via DHCP" and the boxes in which it can be changed will be activated
If you have a DHCP server on your network, newly installed systems will shout out "please give me an address". A great system - works well for individual user's machines (client systems), but isn't recommended for servers. Client machines on our HQ network are allocated in the range 192.168.200.2x, and on the Well House Manor network 192.168.200.8x, with the next number in sequence being issued. As a pooling system where, over time, a lot of machines will connect for just a few days it's brilliant, but as a long term solution for servers it would be utterly impractical as clients had to search for "today's IP address" for the server.
So - an earlier request for a static IP address within our network, and the decision to have the new machine sidestep the default system set up to provide easy network numbering and go this something manual, is correct for the server.