If your client PC cannot access the server even though both systems are connected via the network, the issue might be related to Windows Firewall blocking inbound connections.
Follow the steps below to allow Inbound Connections through the Windows Defender Firewall without disabling the firewall entirely.
Press Windows + R, type wf.msc, and press Enter.
The Windows Defender Firewall with Advanced Security window will open.
πΈ Refer to the image below:
Ensure that all three profiles (Domain, Private, and Public) are ON and allow inbound connections that match the rules.
Each profile should say:
Inbound connections that do not match a rule are allowed.
This ensures that rules you've created to allow specific ports (like SQL Server port 1433) will be respected even if the firewall is on.
To allow inbound connections, follow these steps:
Click on Windows Defender Firewall Properties (link at the bottom of the overview section).
In the Public Profile tab (or the profile your PC is using), set:
Firewall State β On (recommended)
Inbound Connections β Allow
Outbound Connections β Leave as Allow (default)
πΈ Example screenshot:
Click Apply and then OK.
π This configuration keeps your firewall ON but allows incoming connections, enabling your client systems to connect to the server for applications like database access or file sharing.
You can further secure your system by creating a rule that allows only specific ports (e.g., SQL Server default port 1433).
Go to Inbound Rules β New Rule.
Choose Port, select TCP, and enter the required port ( 1433 ).
Choose Allow the connection.
Select the profiles (Domain/Private/Public) to which it applies.
Give it a name (e.g., "SQL Server Inbound Rule").
The client PC will now be able to access the server while the Windows Firewall remains ON, ensuring both accessibility and security.