#### Testing the server-to-controller connections If the system is running, go to the WebCTRL® Devices page from different levels of the Network tree to view the status of your communication networks and controllers. If you detect a networking problem with an Ethernet connection, see Troubleshooting an Ethernet connection. After making sure that the Ethernet cabling has been set up properly, use the Ping utility from the WebCTRL® server to test its low-level IP communication with each controller on the IP network, then obtain a Modstat from each controller to ensure its BACnet communication with the WebCTRL® server.
##### To ping a controller on the IP network from the WebCTRL® server Use the Ping utility to test low-level IP connections between the server and each controller on the IP network. PREREQUISITES An IP network connection between the server and the Automated Logic® controller. A solid link light and a flickering LAN light on the Automated Logic® controller and the WebCTRL® server's Network Interface Card (NIC). See Troubleshooting an Ethernet connection. After the link and LAN lights on the server’s NIC and on the controller are lighting properly, ping each controller from the WebCTRL® server. At the Command Prompt, type the following command: `ping xxx.xxx.xxx.xxx [Enter]`, where `xxx.xxx.xxx.xxx` is the IP address of the device you are pinging. The reply should indicate that a device with address xxx.xxx.xxx.xxx is present and passing IP packets on the network. EXAMPLE For a device with an IP address of 192.168.168.100, type the following: `ping 192.168.168.100` TIP To continuously ping a device, type the following command: `ping xxx.xxx.xxx.xxx -t`. Press Ctrl+C to stop the ping command. If you receive the reply Request timed out or you do not receive a reply, contact the facility’s network administrator to check the NIC, the hub's settings, and the IP configuration settings. You do not have a valid IP connection between the 2 devices.