QBM Client Connection Troubleshooting Advanced Guide

Diagnose QBM desktop connection failures by checking workstation, network, QBM Server, SQL Server, version, and permissions in order.

Where to find it

Path: Help > Help Center, then search for Client Connection troubleshooting.

This topic is a help or support guide rather than a transaction entry screen. Open it from the Help Center and search by the guide title or the main keyword.

Guide Summary

AudienceSupport staff, implementation team, AI agents, and advanced users.
Applies ToQBM Client, QBM Server, SQL Server, firewall, VPN, ZeroTier, LAN, hosted environments.
PurposeProvide a support-level checklist when QBM Client cannot connect or login is unreliable.
Last Updated2026-05-18

Normal Flow

QBM Client on workstation
-> Network, LAN, VPN, or ZeroTier
-> QBM Server Windows Service
-> SQL Server
-> QBM Company Database

Expected result: Users can open QBM Client, connect to the configured server, sign in, and load company data.

Step-By-Step Checks

  1. Confirm whether one user, one workstation, or all users are affected.
  2. Check network access to the server name or IP.
  3. Confirm the configured QBM Server port.
  4. Confirm QBM Server service is running.
  5. Confirm SQL Server service and database are online.
  6. Confirm QBM Client and QBM Server versions match.
  7. Check firewall, antivirus, VPN, ZeroTier, or hosted network rules.
  8. If only one user fails, check password, inactive status, and security permissions.

Common Problems

SymptomLikely CauseFirst Check
One workstation cannot connectLocal network, firewall, cached setting, DNS, VPN, ZeroTier.Test from another workstation and compare settings.
All users cannot connectQBM Server, SQL Server, server restart, network outage.Check server-side services first.
Only one user cannot sign inPassword, inactive user, permissions, account lock.Check user account without requesting password.
Version mismatch warningPartial update.Align QBM Client and QBM Server versions.
Slow loginNetwork latency, SQL performance, service timeout, large startup load.Test from server computer and compare timing.

Troubleshooting Decision Tree

  1. If all users are affected, start at QBM Server and SQL Server.
  2. If one workstation is affected, compare network, firewall, DNS, and connection settings.
  3. If one user is affected, check account status, password reset need, and permissions.
  4. If remote users are affected, check VPN or ZeroTier status before changing QBM settings.
  5. If version mismatch appears, update both QBM Client and QBM Server.
  6. If services and versions are correct, collect logs and escalate.

What To Send To Support

  • Affected scope: one user, one workstation, all users, remote users only.
  • Server name or IP, port, SQL instance, and database name.
  • QBM Client and QBM Server versions.
  • Exact message and screenshot.
  • Recent update, restart, network, VPN, ZeroTier, or firewall change.

Security Notes

  • Do not ask for passwords.
  • Do not expose QBM Server directly to the public internet.
  • Use approved VPN, ZeroTier, hosted, or tunnel patterns for remote access.