This article is about physical Ethernet LAN connectivity.
Every network is different, so this is a general troubleshooting guide for network connectivity issues. For specifics about your local networking equipment, please refer to the respective manufacturer or IT support for your location.
Disconnect the green screw terminal, Modbus and Microlan connections. Only leave the Ethernet cable and the power plug connected to the ezeio.
Make sure the SERVER LED is flashing.
If there are no green lights flashing on the front of the ezeio, there's likely an issue with the power supply.
Make sure there Ethernet cable is connected in the metal jack on the ezeio marked Ethernet. Note that the Modbus jack is not an Ethernet jack.
Make sure the green LED on the Ethernet jack is solid on. The amber light should blink.
Also make sure the other end of the cable is plugged in to a switch/hub/router and that the lights in that end are also on/blinking.
If there is a problem with these lights, please try with a different Ethernet cable or plug it in to a different jack in the switch, or a different piece of networking equipment on your LAN.
Only the SERVER led is relevant to LAN connectivity.
5 blinks : The ezeio has no network connection. It is trying to establish a connection.
4 blinks : The ezeio has communicated with a local DHCP server and was assigned an IP address. This means the physical connection to the network is good. The ezeio will now attempt to query DNS servers for the server address. If it fails to contact DNS servers, it will use pre-programmed addresses for the servers, so it is very unusual that it stays at 4-blink for very long.
3 blinks : The ezeio is trying to communicate with the ezecontrol servers. It is sending contact requests, but no replies are received.
2 blinks : The ezeio is exchanging data with the servers. (All is well!)
1 blink : The ezeio finished exchanging data successfully, and is now idle. (All is well!)
Make sure the physical connection is good (see #1&2 above), and that your network has a working DHCP server. Some corporate networks requires each network device to be specifically allowed on the network. Check with your IT support if this is the case.
If the network does not allow automatic address assignment (DHCP), you may need to set a fixed IP. Consult the ezeio manual for this, or check this knowledgebase article.
The local network connection is established, but attempts to communicate with the ezecontrol servers fail. Make sure your network has connectivity to the Internet. Some networks block certain traffic. The ezeio needs outbound UDP traffic on port 8844, and return traffic needs to be routed back to the ezeio. This is normally the default in most routers, called NAT or Stateful Routing. Contact your IT support to make sure UDP/8844 outbound is open and that return traffic is allowed. Note - you should not need to permanently open any inbound ports.
If there is still no communications, please try moving the ezeio to a different network. For example, try it in your home to make sure it connects to the servers.
Connectivity issues are more common the more 'managed' the networks are. In our experience, schools and governmental organizations are the most problematic as they often default to blocking everything and only explicitly allowing certain traffic. It is very unusual that small corporate or home networks cause problems, and large corporate networks are often well managed and allows the ezeio with no issue.
If there is still no connectivity after trying all the above, please contact eze System and we'll do our best to help.
« Go back
Loading knowledgebase suggestions...