Failure Detection Method for Failure of TCP/IP Controller Communication
First, the general method of fault investigation
First of all, understand the following questions are very helpful to quickly investigate the fault:
1. Is it because the newly installed access control is not on communication, or is it not installed after a certain period of time?
2. Has the customer's network management recently made any relevant settings and restrictions on the network?
What tools need to carry?
1, spare to replace the test access controller
2, multimeter
3, laptop with network port
4, a small four HUB
Precautions:
The investigation of the communication failure of the network access control system requires technical personnel to have a certain amount of network knowledge or require the customer's network management to cooperate. His principle is the same as a computer with a network card in the LAN. You can put the controller in a small LAN or use a small network built by the small HUB to test. If the controller has no problem, then check the fault source.
Please do not connect the computer to the controller with a staggered cable because this connection method is not supported. It is recommended that both the controller and the computer network card be connected to the HUB using a straight internet cable for testing.
Chapter 1 Small LANs (Same Network Segments, Simple Architectures, Under the Same Router)
Controller Rx (Link) lights, if they are on, indicating that the line is basically connected, if not,
It may be:
1, the cable line is broken,
2, the terminal did not do a good line without pressure in place, is virtual,
3, RJ45 network terminal is not plugged in HUB or controller side,
4, HUB does not provide power
5, network cable order, not directly online.
If the controller Rx (Link) light is on, indicating that there is no problem with the wiring, continue with the following test:
Open the access control management software, in the basic settings controller interface, click Search.net
Note : The search .net tool can only be used in small LANs and does not support medium and large cross-network segment search.
If clicking on the search.net controller communication indicator does not respond, prove that the line is still a problem.
If there are Rx Tx lights flashing, and the software search feedback interface does not display information about the relevant controller, the computer may be set to a firewall, or the firewall operating system sets limit parameters for the network. Go to the control panel to release the corresponding firewall. Restrictions (After the default installation of the XP operating system, the firewall is turned on, please turn it off), or notify the user's network management, ask him to release the corresponding network restrictions.
If it is possible to search for the controller and it is not possible to communicate on the general console, it is possible that the controller SN serial number was entered incorrectly.
6, other reasons:
Whether the network card is good and the network cable is good. Terminals are in good contact. You can use a computer instead of analog tests.
Chapter 2 Medium-to-large networks (with cross-segment settings):
If it is a medium-to-large-scale LAN that crosses a network segment, you can't automatically communicate by using a small LAN. You need to select the medium-to-large-sized network option and set the corresponding IP address. This is the same as setting a computer. You can seek the help of customer network management.
The reasons why communication may not be possible are:
1, the customer's network is not a hardware firewall to do the corresponding restrictions.
2. The network segment and IP settings are correct.
Whether the same IP is set with another computer network card or controller, causing a conflict.
The default port used by our device is 60000. The customer's network has restrictions on this port. Please ask the customer's network administrator to release the port's limit, or tell an available port number to be set as the port number in our software.
Remarks: Set up in a small network and put it into a large network. If there is a problem with the communication, you can get a small network first to test whether the controller itself is faulty or incorrectly set.
Chapter 3 Internet Access Control System via Internet
The reasons why communication may not be possible are:
1. Whether to apply for the available virtual domain name, and whether the virtual domain name is filled in correctly.
Whether the provider of the virtual domain name is normal at this time (maybe it is being maintained, try again in a few hours),
2. Whether the relevant settings of the router are correct.
Whether we use the router we recommend to specify the model (Other routers may not be the same function support, or the setting method is not the same. Our setup instructions are based on our recommended model.)