Solvline SG-3011DCL232 V1.0 - Manual (Page 29)

SerialGate User Guide
Troubleshooting
This section describes procedures for troubleshooting problems you may encounter with
SerialGate.
Troubleshooting Installation Problems
If you cannot access the connected serial device via SG-3011DCL/232, first check the network
connection and cabling.

Check the physical cabling to ensure all cables are plugged in (Ethernet and DB-9 serial
cable)

If the appropriate LEDs are not illuminated, then there is probably a bad 10baseT or
100baseTX cable, or the hub port is bad. If possible, try a different cable and hub port, or
try connecting a different device to the cable.

Verify that you are using the correct values for both IP Address and Port Number.
If you are using a hub, verify that the hub port is operating correctly by trying SG-3011DCL/232
on a different port.
Troubleshooting Network Configuration Problems

If you are using TCP/IP, make sure that your computer and SG-3011DCL/232 are on the
same IP segment or can reach each other with a PING command from the host. The IP
address you assign to SG-3011DCL/232 must be on the same logical network as your host
computers (e.g., if your computer has an IP address of 192.189.207.3 and the subnet mask
of 255.255.255.0, SG-3011DCL/232 should have an IP address of 192.189.207.x, where x
is an integer between 1 and 254), or you must properly configure your router address to
work with SG-3011DCL/232.

If your SG-3011DCL/232 is set to auto or DHCP for obtaining an IP address, it is possible
that IP address in SG-3011DCL/232 can be changed. Either configure your DHCP server
to give SG-3011DCL/232 a permanent lease, or configure SG-3011DCL/232 to be on a
STATIC IP address outside the scope of the DHCP addresses.

The problem may be the result of mismatched or duplicate IP addresses. Verify that the IP
address is correctly loaded into SG-3011DCL/232 (via the displayed or printed configuration
information or through the remote console), and make sure that no other nodes on the
network have this address (duplicate addresses are the biggest cause of TCP/IP
29