11 improper ip address, 12 improper or missing gateway address, 13 controller is not in a reset state – Keri Systems NXT Network Connection User Manual

Page 7: 14 controller has been reset, 15 incompatible controller firmware, 16 physical hardware problem, 17 vpn tunnel down, Improper ip address, Improper or missing gateway address, Vpn tunnel down

Advertising
background image

NXT Network Connection

Troubleshooting Guide

Page 7 of 11

P/N: 01508-001 Rev. A

4.11

Improper IP Address

If the IP Address has not been assigned by the Autoconfig process or the IP Address assigned is not within the same
network as the DoorsNXT Server, communication to the controller will fail.

4.12

Improper or Missing Gateway Address

A Gateway address must be specified for controllers that will be communicating to a DoorsNXT Server located outside its
subnet. The DoorsNXT Proxy service must also be installed on a computer within that Subnet to allow the
Autoconfiguration process to complete.

4.13

Controller is Not in a Reset State

A controller will only respond to an autoconfig if it is in a reset state or if the autoconfig request is from the DoorsNXT
server that originally configured the controller. A controller can only be associated with a single DoorsNXT server.

4.14

Controller Has Been Reset

If a controller has been reset, the IP Address and other network data is reset and an Autoconfig is necessary to restore
communications. Performing a controller update or controller status on a reset controller will fail. Performing an
Autoconfig will identify the controller as a reset controller and then the Assign IP button will be enabled so that the
controller can be reassigned its IP address.

4.15

Incompatible Controller Firmware

If DoorsNXT has been upgraded, it may be necessary to also upgrade the controllers’ firmware to a newer version. Failure
to do that may result in controller update and controller status failures.

4.16

Physical Hardware Problem

Check the physical network connections from the DoorsNXT to the NXT Controller. Look at the Link (D22) and Activity
(D33) LEDs on the controller. The Link LED should be illuminated and the Activity LED will flicker when data is
present. If the Link LED is not lit, check the patch cable or replace it with a known good cable. Verify the connection to
the switch/hub/router. Check that there is a Link LED at the port.

4.17

VPN Tunnel Down

If the communication routes through a VPN, verify that the tunnel is operational. Use Ping or the VPN software to
validate connection.

Advertising