Filter
Top Products
Hardware Platform 10 Installation Guide
22
Testing the Ethernet connection
The ping test
The most basic way to test the network connection is to do a so-called 'ping' test. When
the connection is working, the CER controller will answer with an 'echo' or 'pong'.
Start a command prompt on your local machine and type the following command:
ping <IP address>
Example:
ping 10.0.0.1
The response will be something similar to the following:
Reply from 10.0.0.1: bytes=32 time=1ms TTL=128
Reply from 10.0.0.1: bytes=32 time=1ms TTL=128
...
This means the Ethernet connection is working and the IP settings are correct. You should
be able to open the web page with your browser, see next text.
However, if PING displays something like:
Request timed out.
Request timed out.
...
It appears that your system did not receive a response back. Maybe the unit is configured
to a different address, or you have a hardware problem. You can try to ping another
machine to test if the cabling and network configuration is correct. When it fails, check
the cabling and network setup.
In case you see a response like:
Destination host unreachable.
This indicates that the address you try to ping is outside of your subnet and you did not
define a correct gateway/router address on the machine. Fix the IP settings of your
machine and try pinging again. Note that you might have to restart your machine first.
The browser test
When the ping test has passed, start a web browser on your local machine and enter the
current IP address of your CER controller in the location/address field:
http://10.0.0.1/admin/
The Login page should now appear (see page 16). In case the page does not load, check
the proxy settings of your browser. When the CER controller is on the local network or
connected directly with a cross cable, no proxy server should be used for its IP address.