You are here: Troubleshooting > Working with DHCP, Static IP Addresses, and Routers
Working with DHCP, DNS, Static IP Addresses, and Gateways
Does your installation require the use of DHCP and/or static IP addresses? Do you need to set up DNS and a Gateway so that your HAL can synchronize its internal clock with an NTP Server? Never fear, it's as simple as can be. But there are a few things you need to know as well as a few issues that could arise:
- To configure a static IP or enable DHCP on a HAL, you should first connect directly to the HAL via its link-local address. In other words, it is best to configure these addresses prior to connecting the HAL to your network. To do so, install the Halogen software, connect your computer directly to the HAL device, start Halogen, connect to the HAL from within Halogen, and then open the HAL properties, and then configure its IP addresses (and/or enable DHCP). Once the system is installed at the site, you (and all subsequent users) may need to type in a static IP address to search for, and connect to the HAL, so write this IP address somewhere!
- On a local network, Halogen always uses the link-local IP (169.254.x.y) to connect to HAL. Behind a router, Halogen uses one of HAL’s static IPs or a DHCP-assigned IP—provided the user knows it and types it into the Search field in the Connect to Device dialog box. Because link-local connectivity is automatic, the user should never need to search for a HAL by its link-local IP address.
note: If your HAL is located on the WAN side of a router and Halogen is unable to find the HAL, check with your IT department to find out if the router has NAT (Network Address Translation) enabled. If not, enable it and try again.
- Although Halogen does not prevent you from adding a static IP that conflicts with a static IP on another machine on the network, it does prevent the addition of a duplicate IP on the same HAL.
tip: To change a static IP address to another value, you must first delete the existing IP address and then add the desired IP address.
If the DHCP server on the network supports setting up the Gateway and DNS, the HAL uses these addresses and places them in the proper priority order in the Gateway and DNS lists. Gateway and DNS setup is important if you want your HAL to synchronize its internal clock with an NTP server.
If the DHCP server doesn’t support the Gateway and DNS, or the HAL is on a network without a DHCP server, both the Gateway and DNS lists should be configured with static addresses.