Techniques for setting up DHCP address pools in small shared networks

Most small businesses are connected to the Internet with one account plus broadband routers and switches for multi-user sharing of Internet connections, which lowers costs, can also share files and printers over a LAN, and so on ... At present, the more common broadband access mode is mainly ADSL and LAN two ways, as long as the routing of ADSL cat or broadband router can achieve multi-user sharing of the Internet. To reduce the amount of network setup, DHCP services are generally turned on so that shared users ' computers can automatically obtain parameters such as gateways and DNS servers. Do not need a family to adjust the network parameters. However, many users do not pay attention to the reasonable DHCP address pool settings, which can easily cause IP conflicts. The default state, most of the routing of ADSL cats and broadband routers, as long as the DHCP service opened, it will automatically assign all the IP addresses in the network segment to the address pool. For example: The IP of the router is 192.168.0.1, and after the DHCP service is enabled, it automatically adds the IP address of the 192.168.0.X segment to the address pool. So what's going to happen? Users familiar with computers know that setting fixed network parameters (IP address and DNS server) is faster than automatic acquisition, and computer startup is quicker. In the example above, if there are 5 users with fixed network parameters, suppose they occupy the 192.168.0.2~192.168.0.6 six IP addresses. If a fixed IP is set to 192.168.0.2 the user A does not boot for a period of time. There is another user, B, that uses the automatic network parameters method to get online. The DHCP server assigns this IP address to User B when it sees that the current 192.168.0.2 is an idle address. At this point, if User a again online, because this IP address has been occupied by B, will cause IP address conflict, A and B on the computer will appear the IP address conflict prompts. In practical applications, the probability of this happening is very high. In fact, the prevention of such conflicts is very simple, that is, when the DHCP address pool is set, reserving a section of IP address is not used as DHCP allocation. For example, you can set the DHCP address pool to 192.168.0.100~192.168.0.254. Leave the first 99 users with fixed network parameters. In this way, the users who use the Impinging network parameter method will not preempt the IP address of fixed network parameter users, and avoid the occurrence of IP address conflicts. This technique also applies to the use of software to share Internet connections. For specific settings, refer to the description of the specific application tool.