Quick Answer
Mantra error 2100, which shows as “Could not connect to vendor server,” means your MFS100 or MFS110 fingerprint device is unable to reach the RD (Registered Device) service or the authentication server it needs to verify a fingerprint. It’s almost always caused by one of three things: the Mantra RD Service isn’t running, your Windows Firewall is blocking the connection, or your system’s time zone or internet connection is misconfigured. Restarting the RD Service and checking your firewall settings resolves this for most users.
TL;DR
- Error 2100 is a connectivity failure between the Mantra RD Service and the vendor/authentication server.
- Check that the RD Service is actually running before anything else.
- Windows Firewall blocking the RD Service is one of the most common causes.
- An incorrect system time zone can also break the connection.
- If it still fails, reinstall the latest RD Service and driver from Mantra’s official site.
On this page
What does error 2100 actually mean?
Mantra biometric devices like the MFS100 and MFS110 are widely used across India for Aadhaar-based authentication, e-KYC, UIDAI login, PAN card downloads, and banking correspondent transactions. These devices work through a background program called the Mantra RD (Registered Device) Service, which sits between the physical scanner and the software or portal requesting a fingerprint capture.
Error 2100, shown as “Could not connect to vendor server,” means that background service failed to establish a connection with the server it needs to complete authentication. It’s a connectivity error, not a hardware fault, which is why it’s fixable through software and network settings in the vast majority of cases.
Important points to check first:
- Confirm the RD Service is actually running in the background (check your system tray or Task Manager).
- Check whether your internet connection is active and stable.
- Verify your system’s date, time, and time zone are set correctly.
- Note whether the error happens on every scan attempt or only intermittently.
Common causes of error 2100
RD Service not running
If the Mantra RD Service isn’t active in the background, the device has nothing to route the authentication request through, which produces this exact error. This is the single most common cause and the first thing worth checking.
Stan Error Code A30 Fix: “Sorry, We Can’t Play the Video” Error Code
Windows Firewall blocking the connection
Windows Defender Firewall sometimes blocks the RD Service from reaching the vendor or UIDAI servers over the network, especially after a Windows update resets firewall rules. This is a well-documented trigger for error 2100.
Incorrect system time zone
Mantra devices require the system’s time zone to be set correctly, since authentication requests are time-stamped and validated against the server. A mismatched time zone can cause the connection attempt to fail outright.
Outdated driver or RD Service version
Running an old version of the RD Service or driver can lose compatibility with current server requirements, particularly after Mantra or UIDAI push a protocol update on their end.
Network or ISP-level restrictions
Some networks, particularly restrictive office or institutional connections, block the specific ports or domains the RD Service needs to reach the vendor server, even when general internet access works fine.
Step-by-step fixes
Work through these in order. Most cases of error 2100 resolve within the first three steps.
- Check that the RD Service is running. Look for it in your system tray, or open Task Manager and confirm the Mantra RD Service process is active. Restart it if it isn’t.
- Restart your computer after confirming the RD Service is set to start automatically, then try the scan again.
- Check your internet connection. Confirm you can browse normally, then also check whether the connection is being restricted at the network or router level.
- Verify your system time zone and date under Windows Settings, and correct them if they’re wrong.
- Temporarily disable Windows Firewall to test if that’s the cause (see the dedicated section below for the safer, permanent fix).
- Reinstall the latest RD Service and driver from Mantra’s official downloads page, since an outdated version is a common root cause.
- Reconnect the USB device to a different port, and confirm it’s recognized properly in Device Manager before retrying.
Fixing the firewall block properly
Disabling Windows Firewall entirely will confirm whether it’s the cause, but leaving it off isn’t a safe long-term fix. If turning off the firewall resolves the error, the better approach is to add a specific exception for the Mantra RD Service instead of disabling protection altogether.
- Open Windows Defender Firewall settings and go to “Allow an app through firewall.”
- Locate the Mantra RD Service in the list, or add it manually if it isn’t there.
- Enable both Private and Public network access for the service.
- Save the changes and restart the RD Service before testing again.
Does this apply to MFS100 and MFS110?
Yes. Error 2100 is reported across both the MFS100 and the newer MFS110 AVDM models, since both rely on the same underlying RD Service architecture to communicate with the vendor and authentication servers. The troubleshooting steps above apply to either model; the main difference is simply which driver package you need to reinstall if that step becomes necessary.
Cause and fix reference table
| Cause | How to Confirm | Fix |
|---|---|---|
| RD Service not running | Check system tray / Task Manager | Start the service manually, restart PC |
| Firewall blocking connection | Test with firewall temporarily off | Add a firewall exception for RD Service |
| Incorrect time zone | Check Windows date & time settings | Set correct time zone, sync automatically |
| Outdated driver/RD Service | Check version in Device Manager | Reinstall latest version from official site |
| Network/ISP restriction | Try a different network | Switch network or contact IT/ISP |
Before you contact Mantra support, have this ready:
- Your exact device model (MFS100 or MFS110 AVDM).
- The RD Service and driver version currently installed.
- Whether the error happens on every attempt or only sometimes.
- A screenshot of the exact error message and code.
Frequently asked questions
Is error 2100 a hardware problem with my Mantra scanner?
No, in almost all reported cases it’s a software or network connectivity issue between the RD Service and the vendor server, not a fault with the physical fingerprint scanner itself.
Why does disabling the firewall fix it, and is that safe to leave off?
Disabling the firewall removes the block causing the error, which confirms the cause, but leaving your firewall permanently off isn’t recommended. Add a specific exception for the Mantra RD Service instead, so the rest of your system stays protected.
Can an incorrect time zone really cause a connection error?
Yes. Aadhaar authentication requests are time-sensitive and validated against the server’s clock, so a mismatched system time zone can cause the connection attempt to be rejected before it even reaches the point of scanning a fingerprint.
What should I do if none of these steps fix the error?
Reinstall the latest RD Service and driver directly from Mantra’s official downloads page, and if the problem persists after that, contact Mantra support with your device model and exact error details for further diagnosis.
For the latest official RD Service and driver downloads, visit Mantra’s official website. For more device and app troubleshooting guides, browse our Outage Tracker section.
Reviewed and published by Anup V Naick, Games and Technology Editor. This guide reflects general, verifiable troubleshooting practice for the Mantra RD Service and will be updated if Mantra issues further official guidance.
