[ Your PC / Server ] │ ├── (Broadcasts Discovery Command) ▼ [ Network Switch ] │ ├──► [ Biometric Device 1 ] ──► (Replies: "I am at 192.168.1.150") ├──► [ Attendance Clock 2 ] ──► (Replies: "I am at 192.168.1.151") └──► [ Access Control Panel] ──► (Replies: "I am at 192.168.1.152") Method 1: Using the ZKTeco Device Search Tool (Standalone)
If multiple newly unboxed ZKTeco devices are plugged into the network simultaneously, they will all attempt to claim the default factory IP address, causing an IP conflict that disrupts normal network discovery.
This tool is typically included in the software package that accompanies the device on the installation CD, or it can be downloaded from the "Downloads" section of the ZKTeco website or authorized regional distributor portals. zkteco ip scanner
(e.g., ZKTime.Net, ZKBioSecurity, or ZKBio Access IVS) and navigate to Device Management Add Device followed by Search Device
Standard tools like ping or nmap check if a device is online via ICMP. Many ZKTeco devices disable ICMP ping responses for security or power saving. The ZKTeco scanner uses the SDK handshake protocol; if the device has the ZK biometric server running (even with ping disabled), the scanner will find it. [ Your PC / Server ] │ ├──
In enterprise networks, Access Control VLANs are isolated from workstation VLANs for security.
: Plug the ZKTeco device into your network switch using a standard Cat5e/Cat6 Ethernet cable. Power on the device. Many ZKTeco devices disable ICMP ping responses for
For IT administrators comfortable with the command line or developers building custom integrations, npm packages offer powerful scanning capabilities:
Compatibility can be an issue, particularly with older devices. The official ZKTeco tools (like the Communication Setting Tool) are designed to be backward-compatible with many generations of hardware. Community tools, on the other hand, rely on protocol reverse-engineering and may not support every model or firmware version. If you are using a community package, check its documentation for a list of supported devices.
Faulty RJ45 Ethernet termination or broken copper pairs in the network cable.