<div>
<div class="content wysiwyg-content">
Currently our network is setup to have the router handle DHCP, however, I am running Windows Server 2008 and is setup to run as a DHCP server. &nbsp;We have had some connectivity issues with the router, however, resetting the router always solves the connection problems.<br />
I have considered purchasing a new router, however I was wondering if I should set it up for the Server to handle DHCP or leave it to the router to handle DHCP? &nbsp;Is one better than the other and if so why?
</div>
</div>


Currently our network is setup to have the router handle DHCP, however, I am running Windows Server 2008 and is setup to run as a DHCP server.  We have had some connectivity issues with the router, however, resetting the router always solves the connection problems.
I have considered purchasing a new router, however I was wondering if I should set it up for the Server to handle DHCP or leave it to the router to handle DHCP?  Is one better than the other and if so why?

Best Practice for DHCP Handling

Networking software modules are interfaced with a framework implemented on the machine's operating system that implements the networking functionality of the operating system. The best known frameworks are the TCP/IP model and the OSI model. Systems typically do not use a single protocol to handle a transmission. Instead they use a set of cooperating protocols, sometimes called a protocol family or protocol suite.[9] Some of the best known protocol suites include: IPX/SPX, X.25, AX.25, AppleTalk and TCP/IP. Other protocols indirectly related to networking include the hypertext transfer protocol (HTTP) and its related technologies, Dynamic Host Configuration Protocol (DHCP), Domain Name Server (DNS) and other Internet protocols.

Networking Protocols

Network Management involves issues that are independent of specific hardware or software, including email policies, upgrade planning, backup scheduling and working with managed service providers for Desktop-As-A-Service (DaaS), Software-As-A-Service (SaaS) and the like through the use of tools, coupled with manufacturer standards, best practice guidelines, policies and procedures plus all other relevant documentation. Network management also includes monitoring, alerting and reporting, management reporting, planning for device or service updates, the backup of configurations, the setting of key performance indicators and measures (KPIs/KPMs), associated service level agreements and problem records as part of the IT Service Management (ITSM) framework.

Network Management

Servers are computing devices that are similar to desktop computers in that they have the same basic components, but are significantly different in size, configuration and purpose. Servers are usually accessed over a network, and many run unattended, without a computer monitor, input device, audio hardware or USB interfaces. Many servers do not have a graphical user interface (GUI), and are configured and managed remotely. Servers typically include hardware redundancy such as dual power supplies, RAID disk systems, and ECC memory, along with extensive pre-boot memory testing and verification. Critical components might be hot swappable, and to guard against overheating, servers might have more powerful fans or use water cooling.