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

How to Resolve Add-On Machine Connectivity Issues via Windows Firewall Configuration

This article helps Webgility Desktop users configure firewall settings on their main server machine hosting Webgility Database to enable successful communication with an add-on machine. It provides step-by-step instructions to resolve connection blocks caused by Windows Defender Firewall.

When an add-on machine fails to connect to the main system (such as during hardware integration or software sync), a common cause is blocked traffic through Windows Firewall. Correctly configuring inbound and outbound rules can resolve these issues and ensure consistent connectivity.

🛠️ Step-by-Step Resolution

Step 1: Verify Network Connectivity

  1. Ensure all Ethernet or USB cables are securely connected.

  2. Confirm both devices are powered on.

  3. Make sure both devices are on the same network segment or subnet.

Step 2: Identify Required Application and Ports

Refer to the device’s documentation or contact your vendor to obtain:

  • The name of the application or service (e.g., a specific .exe file)

  • Required TCP or UDP ports (commonly used: TCP 1433, UDP 1434)

Step 3: Access Windows Firewall Settings

  1. On the main computer, open Windows Defender Firewall with Advanced Security:

    • Press Windows key, search for “Windows Defender Firewall with Advanced Security”, and open it.

Step 4: Add Inbound Firewall Rules

A. Add the Communication Application

  1. In the left sidebar, click Inbound Rules, then select New Rule.

  2. Choose Program, click Next.

  3. Select This program path, then browse to the executable file (e.g., C:\Program Files\App\yourApp.exe).

  4. Select Allow the connection, then click Next.

  5. Choose all three profiles: Domain, Private, and Public.

  6. Name the rule (e.g., Add-On Communication App) and click Finish.

B. Add Port Exceptions

Repeat the process to add each required port:

  1. Under Inbound Rules, click New Rule.

  2. Choose Port, click Next.

  3. Select either TCP or UDP and enter the specific port number (e.g., 1433 or 1434).

  4. Click Next, then choose Allow the connection.

  5. Enable all three profiles: Domain, Private, and Public.

  6. Name the rule (e.g., TCP Port 1433) and click Finish.

Step 5: Add Outbound Firewall Rules (If Required)

Some systems require outbound rules as well:

  1. In the left sidebar, click Outbound Rules, then repeat steps from Step 4A and 4B:

    • Add both the application and port exceptions using the same process.

    • Name outbound rules clearly (e.g., Outbound TCP 1433, Outbound App Access).

Step 6: Test the Connection

  1. Restart the communication service or application on the main computer.

  2. On the add-on machine, attempt to connect again.

  3. If issues persist, check:

    • Windows Event Viewer > Firewall logs

    • That the correct network profile (e.g., Private network) is active

    • That antivirus software isn’t also blocking the connection