Page 6
Technical Help
1 - Cannot detect ACU via a TCP/IP interface.
Q
1. The TCP/IP interface must be listed in the Net2 Server Configuration Utility, and responds
Q
when PINGed from the utility. We recommend that a static IP address is used.
Q
2. If the interface is responding, try a loopback test. (See Loopback section)
Q
3. The Net2 data line should be checked for resistance readings.
2 - Cannot detect TCP/IP interface.
Q
1. Click Detect in the Net2 Server Configuration Utility to search for the TCP/IP interfaces.
Q
2. Power the device down and ensure it is connected to the network, then power it up again.
Q
3. Check the LED's to ensure there is network activity and confirm the server is connected.
Q
4. If they have a firewall running, make sure the ports are not blocked. (see port list)
Q
5. Ensure the TCP/IP interface and server PC are on the same subnet.
Q
6. PING the IP address. If it is being used over a WAN/VLAN then add it manually.
Q
7. Check the unit with a Loopback test (see previous section).
3 - Direct connection to a PC via the network port.
Q
To communicate directly via the TCP/IP interface on the PC, a standard network cable may
Q
be used. If the unit does not detect the presence of a DHCP server it will default to an
Q
IP address in the range 169.254.X.X.
Q
Check the IP address of the network card of your PC by typing IPCONFIG at the command
Q
prompt. Detect the interface through the Net2 Server Configuration Utility and change the
Q
IP address of the interface to an address similar to that of your machine. For example, if
Q
the IP address of the PC is 192.168.10.7, change the IP address of the TCP/IP interface to
Q
192.168.10.8. Once the IP address of the interface has been changed into the range of the
Q
PC then Net2 will be able to communicate with it.
Q
NOTE: Do not change the IP address of your PC to 169.254.x.x, this will not allow the IP
Q
address of the TCP/IP interface to be fixed correctly.
4 - Can we use a DHCP IP address?
Q
The Ethernet interface does support DHCP, but for more reliable communication, a static IP
Q
address must be reserved for the unit. Some network servers issue different DHCP
Q
addresses each time they are restarted. This then requires the Net2 interface to be
Q
manually set up again - a time consuming process for the user.
