TCP/IP controller communication failure detection method

Time:2016-04-20 16:08:23Hits:1028

   

First.The general method of fault investigation

 

First of all, understanding the following questions is of great help to rapid fault investigation:

1.Is the newly installed access control on the communication, or after installation for a period of time, suddenly not on the communication?

2. Has the customer's network management made any related Settings and restrictions on the network recently?

 

What tools do I need to bring?

1, spare to replace the test access controller

2, multimeter

3, laptop with network port

4, a four-port small HUB

Note: 

Communication fault investigation of network access control system requires technical personnel to have certain network knowledge, or requires the customer's network management to cooperate. It works the same way as a computer with a network card on a LAN. You can put the controller in a small local area network or a small network built with its own small HUB test, whether the controller has no problem itself, and then check the fault source.

Do not interlace the computer to the controller for testing, as this connection is not supported. It is recommended that both the controller and the computer network card be connected to the HUB with a direct network cable for testing.

 

Chapter 1 Small Local Area Network (same network segment, relatively simple network structure, under the same router)

 

Controller Rx (Link) light, if it is steady on, indicating that the line is basically connected, if not,

it may be:

1, the network cable line is broken,

2, the terminal is not done, the cable is not pressed in place, is virtual,

3, the RJ45 network terminal is not plugged in the HUB or controller end,

4, the HUB has no power supply

5, the network cable line sequence, Not a direct network line.

If the controller Rx (Link) light is on, it indicates that there is no problem with the wiring,continue the following test:

Open the access control software, click on the 【 Basic Settings 】 【 Controller 】 interface, and 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 the communication indicator of the controller does not respond by clicking on 【Search.NET】, there is still a problem with the line.

If the Rx Tx light blinks, and the software search feedback interface does not display the information of the relevant controller, it may be that the computer has set a firewall, or the firewall operating system has set restrictions on the network, please go to the "firewall" in the "Control Panel" to release the corresponding restrictions (after the default installation of XP operating system, the firewall is turned on, please turn it off). Or notify the user's NMS and ask him to release the corresponding network restrictions.

If the controller can be searched but cannot be communicated on the master console, the controller SN may have been entered incorrectly.

6,other causes:

Whether the network adapter is good or whether the network cable is good. Check whether the terminal is in good contact. It can be tested by computer instead of analogy.

 

 

Chapter 2 Medium and large networks (with cross-network segment Settings)

 

If it is a medium and large LAN across the network segment, you can not automatically foolishly communicate by selecting the "small LAN", you need to select the "medium and large network" option, and set the corresponding IP address, and set a computer method is the same, do not understand can seek the help of customer network management.

The reasons for the failure to communicate may be:

1.The customer's network is not a hardware firewall to do the corresponding restrictions.

2. Check whether the network segment and IP address are set correctly.

Whether to set the same IP with other computer network cards or controllers, resulting in a conflict. The default port used by our device is 60000. If the customer's network has any restrictions on this port, please let the customer network management release the restrictions on this port, or tell us an available port number and set it as this port number in our software.

Note: Set it up on a small network and then use it on a large network. If there is a problem with communication, you can first take the small network to test whether the controller itself is not a problem, or the wrong setting.


Chapter 3 through the Internet access control system can not communicate the reasons may be

1, whether to apply for the available virtual domain name, the virtual domain name is filled in correctly.

Whether the provider of the virtual domain name is at this time, whether his server is normal (maybe it is being maintained, try again in a few hours),

2, the relevant Settings of the router are correct.

Whether to use the recommended router model (other routers may have different functions or different Settings). Our setup manual is written according to the model we recommend.