Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| troubleshooting:dhcp_server_problems [2010/11/29 09:57] – mats | troubleshooting:dhcp_server_problems [2010/12/01 14:51] (current) – mats | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== DHCP Server problems ====== | ====== DHCP Server problems ====== | ||
| - | This deals with the DHCP Server in the Internet Gate, distributing IP addresses to clients on the LAN. | + | This deals with the DHCP Server in the Internet Gate, distributing IP addresses to clients on the LAN.\\ |
| + | The DHCP Server is configured partly on the [[web_gui: | ||
| + | |||
| + | Read more: [[wp> | ||
| ===== IP address collisions ===== | ===== IP address collisions ===== | ||
| Line 62: | Line 65: | ||
| In this way, the IP collision risk as described above is avoided, even after a restart of the Internet Gate. | In this way, the IP collision risk as described above is avoided, even after a restart of the Internet Gate. | ||
| - | Thus, in practise the host will keep the same IP address as long as the same Internet Gate unit is used, and its (permanent) lease database is not cleared. | + | Thus, in practise the host will keep the same IP address as long as the same Internet Gate unit is used, and its (permanent) |
| However, if keeping the same local IP address is really important for a host, it is more safe to enter that host into the **Fixed addresses** table on the [[web_gui: | However, if keeping the same local IP address is really important for a host, it is more safe to enter that host into the **Fixed addresses** table on the [[web_gui: | ||
| :?: Alternatively, | :?: Alternatively, | ||
| A task that is performed automatically if DHCP server **Fixed addresses** are used instead. | A task that is performed automatically if DHCP server **Fixed addresses** are used instead. | ||
| + | |||
| + | |||
| + | As a consequence of the permanent lease database memory, it is recommended to clear this memory if the Internet Gate unit is moved to a totally new environment, | ||
| + | This is merely to free IP addresses for new usage, addresses that otherwise would be reserved for hosts not likely to show up. | ||
| + | |||
| + | |||
| + | ===== Running out of IP addresses ===== | ||
| + | The **From** and **To** fields on the [[web_gui: | ||
| + | The size of the pool is by default 31 such addresses (ranging from typically 192.168.0.31 to 192.168.0.61), | ||
| + | The default size should be enough for most users. | ||
| + | |||
| + | However, for a network that sees a lot of different users (=hosts) coming and going it is worth remembering that the pool of IP addresses includes the currently " | ||
| + | The DHCP server has a stategy that when a new host (with a previously unknown MAC address) appears, it will get an IP address that is totally unused, that is, it is not present in the stored //lease database// | ||
| + | Only when the server is running short of addresses, because the whole pool is used, it starts using IP addresses that really was reserved for another, currently unseen (=not connected) host, thus deleting the old host from the database. | ||
| + | |||
| + | ===== Why can't my PC get an IP address? ===== | ||
| + | |||
| + | * Is there an Ethernet link at all, both in the PC and with the Internet Gate? (See also [[connect_to_gui|here]]) | ||
| + | * Does a static IP address work? To try that, set the IP interface of your PC to static instead of dynamic address (on Windows, this is done in the Control Panel, Network Connections). Choose an IP address that is within the same subnet as the Internet Gate's local interface (for example 192.168.0.5). | ||
| + | * If the static IP address works, but not the dynamic (by DHCP, " | ||
| + | * Is the address range too small in the Internet Gate? It could be increased on the [[web_gui: | ||
| + | * Could there be an IP collision case, as described [[dhcp_server_problems# | ||
| + | - Disconnect //all// hosts from the LAN | ||
| + | - Click the **Reset** button under **IP address lease status** on the [[web_gui: | ||
| + | - Reconnect all hosts again one-by-one so that each host in turn will get its IP address refreshed from the Internet Gate. | ||
| + | * If it is suspected that the //lease database// in the Internet Gate has been lost, or is wrong (maybe the unit has been moved to a new network, or factory reset), do the same procedure as above. | ||
| + | * If the static IP address doesn' | ||
| + | |||
