In order for a computer to communicate with other computers on a TCP/IP network, it needs certain information, including where it is itself (its own network address) and where certain essential network resources are located. Under normal circumstances this information, which may include up to four IP addresses or more, must be manually entered into the TCP/IP network control panel of every computer on the network. To further complicate the issues, each computer's TCP/IP network address must be unique, yet should follow a logical order to make future expansion and troubleshooting easier. Each address must be entered perfectly and without error, or the computers will not be able to communicate. In an ideal world, once this information has been entered it should not require any changes. However, computers get replaced or moved and new systems get added to a network. If a major network resource such as a router (which interconnects networks) changes its network address, this could require changing the TCP/IP network configuration of EVERY computer on the LAN. In a large computer network, this is not a task to be taken lightly. With the increase in use of mobile computers, keeping track of allocated addresses becomes even more of a problem especially if mobile users move from one network to another. What's New: Version 7.0.9 fixes the following: Ability to ping an address to see if is is already in use before issuing. Ability to only serve IP Addresses to clients listed in the DHCP Clients file. Ability to disable BOOTP serving. DHCP lease times are now correctly set to 60 minutes in all cases. The router address for DHCP clients can now be within the DHCP range and it will not be issued as a DHCP address. All demos are now 30-day expiry. |  |
| 
