WinGate provides an optional DHCP Service that can be installed to take care of client IP addressing when required. The DHCP Service gives you the ability to create address scopes, IP reservations, and set other address details from a wide range of options.
Setting | Default value |
|---|---|
Service Port | 67 |
Bindings | The DHCP service in WinGate will bind itself to any network interfaces with a private IP address (excluding localhost 127.0.0.1) on the WinGate Server. This is so it can listen and respond to client DHCP requests from the local network(s) automatically from installation. If the DHCP Service is to be made available on specific interfaces only then these can be set manually in the Bindings tab of the DHCP service. |
Registered events | There are no events registered by the DHCP service. |
For easy administration the WinGate DHCP Service can be set to run in three different modes of operation. Each mode determines how much information and configuration the DHCP Service needs in order to provide DHCP services to the client. You can select which mode you want the DHCP Service to operate in on the DHCP Mode tab in the DHCP Service properties.
If some computers require a permanent static IP address that will never change, such as other servers running on the LAN, then these computers can be configured manually. WinGate DHCP checks to see if it can ping an IP address before it will allocate it. If it can ping an address, it knows the address is in use and so it will not allocate it to any other computer.
You can also set excluded IP addresses in each scope that you create in WinGate DHCP specifically for these static IP computers.
Often in Active Directory and complex network environments there will already be a DHCP Service providing IP address details to client computers. In this case there is NO requirement to install or use the WinGate DHCP Service.
Clients who wish to access the Internet using NAT (Network Address Translation) through WinGate, are required to have the IP address of the WinGate server set as their Gateway in the properties of their network interface. If WinGate NAT clients are receiving their IP address details from a DHCP Service other then WinGate, then the other DHCP Service needs to be configured to issue the LAN IP address used by WinGate, as the Gateway setting to clients. (Commonly referred to in DHCP as the Router option).
You can use basic Full-Text Searches against the page title and body to find matching articles. Use the following search modifiers to refine your query:
