Skip to content
  • There are no suggestions because the search field is empty.

How to Resolve SQL Database Connection Issues on an Add-On Machine

This article helps Webgility Desktop users troubleshoot and resolve connection issues between an add-on machine and the main server machine hosting SQL database. It guides users through identifying and fixing common causes such as network misconfigurations, firewall restrictions, incorrect credentials, and incompatible SQL drivers to restore proper connectivity and integration.

Step-by-Step Troubleshooting

Step 1: Verify Network Connectivity

Check if the add-on machine can reach the SQL host:

  • Open Command Prompt and run:

    php-template
    CopyEdit
    ping <SQL host IP or hostname>
    telnet <SQL host IP or hostname> <port>

  • Replace <SQL host> and <port> with your database’s details (default SQL port is 1433)

🔍 If the ping or telnet fails:

  • Confirm network cables or Wi-Fi connections are active

  • Check for VPN or firewall rules blocking traffic

  • Ensure the SQL host allows incoming connections from the add-on machine

Step 2: Validate Connection Configuration

Double-check the database connection details entered on the add-on machine:

  • Database Host/IP

  • Port number (default: 1433 for Microsoft SQL Server)

  • Username and password

✏️ Tip: Copy/paste credentials to avoid typos. Confirm credentials with your database admin if unsure.

Step 3: Confirm Authentication and Permissions

  • Ensure the database user account has permission to connect and perform the required actions.

  • If using Windows Integrated Authentication, verify:

    • The add-on machine is joined to the same domain

    • Group policy allows remote SQL access

  • If using SQL Authentication, confirm the login exists and is not locked or expired.

Step 4: Check SQL Driver Compatibility

  • Ensure the SQL driver installed on the add-on machine matches the database version.

  • Supported drivers for SQL Server include:

    • ODBC Driver 17 for SQL Server

    • Microsoft SQL Server Native Client

🔁 If unsure, reinstall or update the driver from the official Microsoft website.

Step 5: Configure Firewall and Security Rules

  • On the add-on machine, allow outbound connections to the SQL port (e.g., 1433).

  • On the SQL Server, ensure inbound connections are allowed for the same port.

To allow SQL traffic in Windows Firewall:

  1. Open Windows Defender Firewall with Advanced Security

  2. Go to Inbound Rules > New Rule

  3. Choose Port > TCP > 1433

  4. Select Allow the connection

  5. Apply to all network profiles (Domain, Private, Public)

  6. Name the rule (e.g., SQL Port 1433)

🛡️ Also check antivirus or security software that may block ports or SQL applications.