Configure Windows Firewall for SQL Server TScan Instance

draft · os-and-system windows-firewallsql-serverudp-port

Generated by docuprocessor (prompt article/v3) · 2026-04-22 15:57

Source thread

thread_id: spaces/AAAA05BdS6s/threads/hMjP3QBXQVg · 21 msgs · first 2025-02-16 · participants: Tech ATech BTech C

Tech A 2025-02-16 16:25

@all I cannot figure out the WIn firewall issue :( Software TScan, SQL based. I configured the SQL port to be 51444, opened in Win firewall but the software does not launch unless I disable the FW completely any ideas?

image/png image.png

**PowerShell** on machine **SVR22** shows a successful `Test-NetConnection` to remote address **192.168.1.220** on port **51444** (`TcpTestSucceeded: True`). A **Database Error** dialog reads: *"An error occurred while attempting to access the patient database"* with database location listed as **svr22\TSCAN10**. **SQL Server Configuration Manager** shows TCP/IP **Enabled** with TCP Port **51444** configured under IPAll, and Named Pipes **Enabled**.

Tech B 2025-02-16 16:27

Did you change port on all 3 service protocols besides tcpip?

Tech A 2025-02-16 16:27

Yes, I did

Tech A 2025-02-16 16:28

oh, wait. what do u mean?

Tech B 2025-02-16 16:28

Services restarted after, to take effect?

Tech A 2025-02-16 16:28

yes

Tech B 2025-02-16 16:29

(no text)

image/png Image_20250216_102857.png

**SQL Server Configuration Manager** is open on host **SVR22** (Windows 10.0.20348, 64-bit), showing **TCP/IP protocol enabled** under SQL Server Network Configuration. The **TCP/IP Properties** dialog displays **TCP Port 51444** configured for both **IP1** (127.0.0.1, Active: Yes, Enabled: Yes) and **IPALL**, with **IP2** showing Active: Yes but Enabled: No and IP Address **::1**. Memory reads **5.9GB / 31.7GB**; Service Tag is **11X4V64**.

Tech A 2025-02-16 16:29

how do u change ports for Shared and NamePipes?

Tech A 2025-02-16 16:30

i dont see the option to do so

image/png image.png

The image shows a SQL Server Configuration Manager window displaying client protocol settings, with **Shared Memory**, **Named Pipes**, and **TCP/IP** all listed as **"Enabled"** in the protocol list. A **Shared Memory Properties** dialog is open, showing the **"Enabled"** field set to **"Yes"** under the General/Protocol tab. No error codes or warning indicators are visible; all settings appear as standard enabled configurations.

Tech A 2025-02-16 16:30

(no text)

image/png image.png

**SQL Server Configuration Manager – Named Pipes Properties Dialog** The Named Pipes Properties window shows the protocol is **Enabled: Yes**, with the Pipe Name set to `\\.\pipe\MSSQL$TSCAN10\sql\quer` (truncated). The parent protocol list confirms **Shared Memory**, **Named Pipes**, and **TCP/IP** are all in **Enabled** status.

Tech B 2025-02-16 16:31

Oh nvm

Tech B 2025-02-16 16:31

All ports on tcpip

Tech A 2025-02-16 16:32

yes, this I did

image/png image.png

**TCP/IP Properties dialog box, IP Addresses tab** — IP1 is Active/Enabled with IP Address **192.168.1.220** and TCP Port **51444** (circled in red). IP2 shows Active: Yes, Enabled: No, IP Address **::1**, TCP Port **0**. IP3 shows Active: Yes, Enabled: Yes, IP Address **127.0.0.1**, TCP Port **51444** (circled in red).

Tech B 2025-02-16 16:34

Does the client know to connect on that port ?

Tech A 2025-02-16 16:35

no setting in the client's config XML.

Tech C 2025-02-16 16:38

do you have multiple entries for desired port in windows FW? Check if in allow an app through windows firewall you have existing entry and if it's set for current type of network private/public...

Tech B 2025-02-16 16:38

splash me in

Tech A 2025-02-16 16:40

952347334

Tech A 2025-02-16 16:40

i do, just deleted, left one entry

Tech A 2025-02-16 16:50

did not help as well

Tech A 2025-02-16 17:11

there also was a UDP port that I missed. Alex to the rescue, as always 🙂

image/png image.png

The image contains a text note stating that the Network Administrator needs to **setup a static TCP port for TSCAN10 instance**, open the server firewall for that port, and also open **UDP port 1434**. No equipment, indicator lights, error codes, or physical components are visible — the image contains text only.

---
title: "Configure Windows Firewall for SQL Server TScan Instance"
category: os-and-system
tags: ["windows-firewall", "sql-server", "udp-port"]
source_thread_id: "spaces/AAAA05BdS6s/threads/hMjP3QBXQVg"
source_space: "spaces/AAAA05BdS6s"
generated_at: "2026-04-22T15:57:15"
participants: ["Tech A", "Tech B", "Tech C"]
---

# Configure Windows Firewall for SQL Server TScan Instance

## Problem

TScan software failed to launch with Windows Firewall enabled, displaying "An error occurred while attempting to access the patient database" for database location svr22\TSCAN10. The software would only function when Windows Firewall was completely disabled. SQL Server was configured with TCP port 51444 and the port was opened in Windows Firewall, but the connection still failed despite successful Test-NetConnection results to the configured port.

## Resolution

1. Configure SQL Server to use a static TCP port (51444) in SQL Server Configuration Manager under TCP/IP Properties for all active IP addresses
2. Restart SQL Server services to apply the port configuration changes
3. Open TCP port 51444 in Windows Firewall for the SQL Server instance
4. **Critical step**: Also open UDP port 1434 in Windows Firewall - this is the SQL Server Browser service port required for named instance discovery
5. Ensure only one firewall rule exists for each port to avoid conflicts
6. Verify the firewall rules are configured for the correct network profile (private/public) matching your current network type

The missing UDP port 1434 was the root cause preventing the TScan client from properly discovering and connecting to the TSCAN10 named SQL Server instance.

## References
- Source discussion: `spaces/AAAA05BdS6s/threads/hMjP3QBXQVg`
- Attachments:
  - ![image.png](../attachments/hMjP3QBXQVg.0HuviMbN8qg/image.png) — The image contains a text note stating that the Network Administrator needs to **setup a static TCP port for TSCAN10 instance**, open the server firewall for that port, and also open **UDP port 1434**. No equipment, indicator lights, error codes, or physical components are visible — the image contains text only.
  - ![Image_20250216_102857.png](../attachments/hMjP3QBXQVg.Jw7-Eaue99I/Image_20250216_102857.png) — **SQL Server Configuration Manager** is open on host **SVR22** (Windows 10.0.20348, 64-bit), showing **TCP/IP protocol enabled** under SQL Server Network Configuration. The **TCP/IP Properties** dialog displays **TCP Port 51444** configured for both **IP1** (127.0.0.1, Active: Yes, Enabled: Yes) and **IPALL**, with **IP2** showing Active: Yes but Enabled: No and IP Address **::1**. Memory reads **5.9GB / 31.7GB**; Service Tag is **11X4V64**.
  - ![image.png](../attachments/hMjP3QBXQVg.b4lAaKbHYOY/image.png) — **TCP/IP Properties dialog box, IP Addresses tab** — IP1 is Active/Enabled with IP Address **192.168.1.220** and TCP Port **51444** (circled in red). IP2 shows Active: Yes, Enabled: No, IP Address **::1**, TCP Port **0**. IP3 shows Active: Yes, Enabled: Yes, IP Address **127.0.0.1**, TCP Port **51444** (circled in red).
  - ![image.png](../attachments/hMjP3QBXQVg.hMjP3QBXQVg/image.png) — **PowerShell** on machine **SVR22** shows a successful `Test-NetConnection` to remote address **192.168.1.220** on port **51444** (`TcpTestSucceeded: True`). A **Database Error** dialog reads: *"An error occurred while attempting to access the patient database"* with database location listed as **svr22\TSCAN10**. **SQL Server Configuration Manager** shows TCP/IP **Enabled** with TCP Port **51444** configured under IPAll, and Named Pipes **Enabled**.
  - ![image.png](../attachments/hMjP3QBXQVg.oCkdlwlblyw/image.png) — **SQL Server Configuration Manager – Named Pipes Properties Dialog**

The Named Pipes Properties window shows the protocol is **Enabled: Yes**, with the Pipe Name set to `\\.\pipe\MSSQL$TSCAN10\sql\quer` (truncated). The parent protocol list confirms **Shared Memory**, **Named Pipes**, and **TCP/IP** are all in **Enabled** status.
  - ![image.png](../attachments/hMjP3QBXQVg.qnIyxuEM3hQ/image.png) — The image shows a SQL Server Configuration Manager window displaying client protocol settings, with **Shared Memory**, **Named Pipes**, and **TCP/IP** all listed as **"Enabled"** in the protocol list. A **Shared Memory Properties** dialog is open, showing the **"Enabled"** field set to **"Yes"** under the General/Protocol tab. No error codes or warning indicators are visible; all settings appear as standard enabled configurations.

Generated article

draft