1. Architectural Root Cause: Cloud Push vs. Legacy Desktop Polling
Before fixing individual errors, it is critical to understand how your attendance setup is wired. Indian offices generally run on one of two architectures:
Desktop Client Polling (eTimeTrackLite)
A desktop PC in the office runs local software that pulls punches over LAN every 10–30 minutes, then re-uploads them to the cloud.
× Fails whenever the PC sleeps, reboots, or encounters Windows updates. Requires static IP and port forwarding.
Native Cloud ADMS (Direct Push)
The biometric machine connects directly to the internet via router Ethernet or Wi-Fi. It pushes punches to the cloud in sub-second real-time via HTTP/HTTPS POST requests.
✓ 100% PC-independent. Operates 24/7 without middle agents or static IP configurations.
2. The 7 Most Common ADMS Sync Errors & Step-by-Step Fixes
1Error 1: ADMS Server Domain & Port Mismatch
In the biometric device menu under Menu → Comm. → Cloud Server / ADMS / Web Server, there are two crucial fields: Server Address and Server Port.
Common Mistake: Entering http://adms.yourprovider.com in the Server Address field. Biometric firmware cannot parse the "http://" prefix!
Correct Configuration: Enter only the domain or raw IP: adms.yourprovider.com.
Port Check: If your cloud HRMS uses Port 80, 443, or 7788, verify that the device port matches exactly.
2Error 2: DNS Server Misconfiguration (Domain Resolution Failure)
When the machine is configured to push data to a domain name (like push.microplesk.com), it relies on DNS to convert that domain into an IP address. By default, many routers assign themselves (192.168.1.1) as the DNS server, but do not forward DNS queries from low-level IoT firmware.
Primary DNS:
8.8.8.8 | Secondary DNS: 8.8.4.4 (or Cloudflare 1.1.1.1).3Error 3: Local Desktop PC Sleep or Auto-Update Kill
If your setup uses a middle-agent utility (e.g. desktop eTimeTrackLite running on an office reception PC), Windows 10/11 power management frequently puts the PC to sleep or restarts it overnight for automatic updates.
services.msc) to "Automatic (Delayed Start)" with recovery option "Restart the Service" on failure. Better yet, switch to direct Cloud ADMS push to eliminate the PC completely.4Error 4: Device Transaction Log Buffer Overflow
Biometric machines store punches in internal flash memory. Popular models like the eSSL K30 or ZKTeco MB20 store between 50,000 and 100,000 logs. Once this buffer is saturated:
- The device slows down significantly when employees swipe.
- HTTP push packets fail to compile or transmit.
- New punches overwrite old un-synced logs.
The Fix: After ensuring all historical logs are safely synced or exported to USB, navigate to Menu → System → Data Mgt. → Delete Attlog. Modern cloud HRMS platforms like MicroPlesk automatically acknowledge and clear processed logs via ADMS protocol commands.
5Error 5: DHCP IP Lease Expiration / LAN IP Conflict
If DHCP is turned on without address reservation, the router may assign the biometric device a new local IP address every week, or give its IP to a smartphone connecting to Wi-Fi.
192.168.1.200), or manually toggle DHCP off on the device and enter a static IP outside the standard DHCP pool.6Error 6: Corporate Firewall & Outbound Port Blocking
Some corporate networks and ISP routers (particularly Airtel Business, ACT Fibernet, or Tata Tele) block non-standard outbound ports like 7788 or 8081 by default.
7Error 7: Employee User ID / Enrollment ID Mismatch
Sometimes the biometric machine is syncing punches to the cloud perfectly, but the HR dashboard shows an employee as absent!
105, but their Employee Code in the HRMS is EMP0105. Because the strings do not match, the system stores the punches in an unmapped queue.The Fix: Ensure your cloud HRMS supports custom Biometric Device Enrollment ID mapping so any device ID maps seamlessly to official employee profile codes.
3. Device Setup Reference: eSSL vs. ZKTeco Menu Navigation
| Device Brand / Family | Menu Path to ADMS Cloud | Recommended Server Format |
|---|---|---|
| eSSL (K30, Identix, SilkBio) | Menu → Comm. → Cloud Server / Web Server | Domain or IP (without http://), Port: 80 / 443 |
| ZKTeco (MB20, IN01, K40) | Menu → Comm. → ADMS / Cloud Server Settings | Enable Domain Name: ON, Web Server: push domain |
| Realtime / BioMax Devices | Menu → Network → Cloud / Web Server | Server IP/URL, Web Port, Heartbeat: 60 sec |
4. Why MicroPlesk Cloud Push Solves Attendance Sync Forever
MicroPlesk was engineered specifically to eliminate the instability of local Windows desktop sync utilities. Our cloud infrastructure implements native ADMS push protocols compatible with all major eSSL and ZKTeco machines.
- Zero Local PCs Needed: Your attendance machine talks straight to MicroPlesk servers through your existing office Wi-Fi or router cable.
- Instant Real-Time Sync: Punches reflect on the HR dashboard and mobile employee self-service within 500 milliseconds of biometric contact.
- Automatic Buffer Flush: Devices never get clogged with 100,000 old records because MicroPlesk automatically sends protocol acknowledgment commands.
- Selfie GPS Mobile Backup: Field sales representatives and remote executives can punch via mobile with live GPS geofencing.
Connect Your Existing Biometric Machine in 15 Minutes
Keep your existing eSSL or ZKTeco hardware. No replacement costs, no desktop PC sync crashes. Get automated attendance, leave sandwich rules, and one-click payroll for under 50 employees at flat ₹2,399/month.
Related Biometric & Attendance Guides
eSSL Biometric Attendance Cloud Sync Guide →
Step-by-step ADMS setup for eSSL K30, uFace, and SilkBio.
ZKTeco Cloud Attendance Setup Guide →
Connecting ZKTeco MB20, IN01, and K40 directly to cloud servers.
eSSL vs ZKTeco Biometric Machine Comparison (2026) →
Detailed comparison of hardware durability, cloud ADMS support, and pricing.
Attendance Management Software India →
Shift roasters, overtime calculation, and biometric-to-payroll automation.