Troubleshooting LAN-520

Troubleshooting LAN-520

LAN-520 Troubleshooting

1.0Cannot Connect to the PXL Network

- Check the LAN-520 IP address and port number is correct in the Doors.NET software. The IP address should match the address which has been programmed in the LAN-520.

 

LAN-520 IP and Port

 

- By default, the Server's Ethernet Port Number is set to 10021 and should not be changed unless it conflicts with another device on the host workstation.

- By default, the Remote Site Port Number is set to 10001 (both in the device and in the Doors.NET software). You can check this by making a Telnet connection to the device and check this value in the Channel 1 settings. This value should be at 10001 unless you have been instructed to change it by an IT or Network Administrator.

 

- When you attempt an auto-config, check the lower green network status LED. If it starts to blink slowly then the software is communicating with the LAN-520. Check that the JP6 and JP7 jumpers on the primary controller have been removed (this configures the controller for an Ethernet communication).

 

- Verify that the primary controller is receiving sufficient voltage (between 12 and 14VDC).

 

- Verify that the primary PXL controller is addressed as number 1.

 

- Telnet into the LAN-520 and set factory defaults (IP address with remain) - Ensure that the Gateway IP address is entered correctly.

 

- Ensure the PC is on the same IP range as the LAN-520. The best way to check this is to run Lantronix Device Installer (can be downloaded from www.lantronix.com) and check that the device shows as Online.

 

2.0The LAN-520 Has a Flashing Red LED

- The LAN-520 may have malfunctioned

- The LAN-520 has been assigned an IP address which already exists on the network.

- The LAN-520 may not be properly connected to the TB13 Ethernet port.

 

3.0The LAN-520 has Only the Top Green LED illuminated

- Verify that the Ethernet cable is not disconnected at the LAN-520 or the network hub/switch.

- Verify that the network hub/switch has not developed a fault.

- If using a cross-over cable check that the Ethernet cable is plugged into the PC

 

4.0Cannot Ping the IP Address of the LAN-520

- There is no power to the LAN-520 unit.

- The IP address may not be programmed properly.

- Another device on the network has that same IP address (you should be seeing a flashing red LED on the unit if this is the case).

- The workstation has not been granted access to that segment of the network.

    • Related Articles

    • LAN-520 and NC-485 Network Converter Setup Guide

      1.0 Introduction The NC-485X offers you more flexibility in managing multiple, remote, physical sites and enhanced networking capability. By using the LAN-520X in combination with an NC-485X Network Converter, PXL-500 controllers, which are normally ...
    • LAN-520 - Quick Start Guide

         1.0 Introduction The following steps explain how to setup a PXL-500 in the Doors.NET software using a LAN-520 module. It assumes you have worked through the steps to install and license the Doors.NET software and that you have also setup the PXL ...
    • LAN-520 AESP - Full Installation Guide

      1.0 Introduction The following are basic setup steps for the LAN-520 AESP. Some settings may not apply to every application. Note: The LAN-520 AESP is an updated version of Keri’s LAN-520X device. If you are using the new NC-485X Network Converter ...
    • What to do if Your LAN-520 Gets Hacked

      1.0 Introduction If the LAN-520 channel 1 port # has been changed to 1234 then this is highly indicative that the device has been hacked. The default value for the port number is 10001. This is the number that identifies the channel for remote ...
    • Verify Communication By Performing a Telnet Session to Port 10001

      This will test the default port used by Doors32/Doors.NET to communicate to the device. The telnet command is preferred over the ping command in testing communications because the telnet command will give a specific response from the device, whereas ...