That would be a bad idea - the server needs a static IP address to go with its DNS entry. If the server kept changing its address because of DHCP then the DNS entries would need to be constantly updated as well.
This would cause unnecessary traffic on the network and more work for DNS to do, plus the fact that the new DNS entries are not replicated fast enough. What could happen is that a user might specify a DNS address, such as microsoft.com, and go to the wrong or a missing site as a result of the DNS entry not updated.
Of course, you could configure a server with DHCP (there isn't anything stopping you from doing that), but as a rule of thumb it isn't a good idea because it isn't very efficient from the user's standpoint.
No!
yes, one can configure two dhcp server on a same network. But for doing this, one has to define different scopes in both dhcp server in order to avoid ip address conflict. Eg. one can configure a scope for a lan with network address of 10.0.0.0 as- 10.0.0.10- 10.0.0.100 in one dhcp server. while other scope would be 10.0.0.101-10.0.0.200 . In this way we can have to dhcp servers on a same network. Which ever dhcp server receives the request for the ip address will provide the ip address. IN case for servers, one can use mac bindingin both servers so that they obtain same ip address
DHCP Dynamic Host Configuration Protocal
Yes, a LAN could have two DHCP servers, but it wouldn't make much sense. Typically each LAN has it's own DHCP server or uses a DHCP relay agent to get an address from another subnet.
See related link. You can use MyLanViewer and detect DHCP servers.
Benefits:1. DHCP is easier to configure, the network information does not need to be put into the computers on the network.2. Less network administration. If any information is changed in the future, like the gateway or DNS servers, they will be updated automatically.Drawbacks:Your IP address would change after being off for awhile, if you were trying to access that computer via hostname a ipconfig /flushdns would need to be performed first.Usually the Servers are static IP's and the workstations are DHCP.
netsh
There can only be one DHCP server on a network. Two DHCP servers will conflict.
The use of a DHCP relay agent is an agent that relays DHCP between DHCP clients and DHCP servers on different IP networks. The DHCP relay agent is compliant with RFC 1542.
There are mail servers, FTP servers, Web servers, DNS servers, DHCP Servers, those are the most common types
DHCP support is already included in every distro capable of networking. It isn't a program; it's a basic part of the TCP/IP protocol.Answer:Well, if you are referring to the DHCP client, the program /sbin/dhclient is likely already installed on your Linux distro of choice.If you would like to run a DHCP server for one or more DHCP client machines or devices, you would go to www.isc.org and download the dhcp.x.x.x package (whatever the latest and greatest version is) and compile it on your Linux host machine. After compilation, configure it as desired, launch dhcpd (usually via the service command or directly from /etc/init.d), the DHCP daemon and you're ready to boot your DHCP clients.
For a Windows based system you use the DHCP MMC snapin console. This is installed when the DHCP server service is installed. For Linux and Unix based systems you can edit the DHCP configuration file in /etc