Troubleshooting method for TCP / IP access controller communication failure
Wide Range Lighting Searchlight,Search Light For Camping,USB Rechargeable Spotlight Guangdong Dp Co., Ltd. , https://www.dp-light.com
1. Debugging and inspection in LAN
Installed equipment, when debugging fails
1 Add the controller in the software, the serial number of the controller must be correct
2 Select "Small LAN" as the communication method
3 On the main console-> "real-time monitoring" of the controller, if the communication is not up, then check down (keep "real-time monitoring")
4 Go to the controller and check whether the lights on the controller are on or flashing,
5 After obtaining the working status of the lamp, first implement that the CPU flashes normally and the Err lamp does not light
Then implement the green and orange lights near the network cable:
If the green light is not on, check whether the line from the controller to the switch is connected properly (line problem);
If the orange light does not flash, check the line (this part is complicated and involves hardware lines and systems)
If the orange flashes, check the computer and turn off the firewall first (in XP, turn off the windows firewall (run: firewall.cpl)) mainly because of system problems. If it still does n’t work, try another computer. Off
Note: To open "Windows Firewall", click "Start", point to "Settings", then click "Control Panel", "Network and Internet Connections", and then click "Windows Firewall".
After the above operations, you should be able to basically determine the problem
Second, cross-segment debugging and inspection
The key to debugging across network segments is the testing of IP addresses and related gateways
The key instruction is ping 192.168.1.168
(Where 192.168.1.168 is the IP address set by the controller, replace it in actual use)
If the normal communication returns, the normal time, LAN will not exceed 2ms, WAN will not exceed 30ms; if the time exceeds 50ms, there may be network problems (such as network viruses)
If the ping controller is not working, try to ping other devices or computers (in the same network segment as the controller).
If you can ping other devices, you need to check whether the controller's IP gateway is set correctly (this requires network management's help)
After pinging the controller, the software still can't communicate. First check if there is "Enable TCPIP" in "Extended Functions". If it is ticked, it will be unchecked. Then check whether the controller IP and port settings are correct. If it doesn't work, it will be analyzed specifically.
.
Third, for the use of dynamic domain names for Internet access control, first obtain the actual IP of the domain name
For example: if I want to know the domain name IP of Baidu, I can open the command prompt tool of the system, Ping
Return: Reply from 220.18.57.217: Byte = 32 Time = 30ms TTL = 56, indicating that the IP bound to the Baidu domain name is 220.18.57.217
The actual IP of your dynamic domain name can be obtained by the same method. If the bound IP is inconsistent with the WAN IP obtained by your router when surfing the Internet, there is a problem with dynamic domain name resolution. (You have to deal with it separately)
Fourth, the solution to special problems is also a professional approach
A. Prepare five things: laptop, two network cables, a four-port small switch, a 12V power supply (for powering the controller), .NET access control controller (no IP address)
B. First in the company, debugging everything is normal
C. Go to the scene, connect the five things, test everything is normal, and then test again. (If the built-in one does not work properly, check the AC power supply)
D. Then change and debug one by one (change the same device, test it, so that you can find the problem)
Note: Add the on-site controller to the management software
1 Replace the on-site computer with your own notebook first, if the communication is feasible, check the on-site computer system
2 Replace the network cable of the computer and the switch with the own network cable. If the communication is feasible, there is a problem with the on-site network cable
3 Replace the on-site switch with its own switch. If the communication is feasible, there may be special configuration for on-site switching, which requires the cooperation of the customer network management.
4 Replace the controller and exchanged network cable with its own network cable. If communication is feasible, there is a problem with the field network cable
5 Use the built-in 12V power supply to supply power to the on-site access controller. If communication is feasible, there is a problem with the controller ’s on-site power supply or installation location.
6 Replace the on-site access control controller with the built-in .NET door controller. If communication is feasible, there is a problem with the on-site controller
At this point, you should be able to find the problem. If it can't, then recheck from item C.