DMZ Server cannot connect to SQL Server
Microsoft resources to help configure DMZ for SQL access
This topic describes how to configure an
instance of the SQL Server Database Engine to listen on a specific fixed port
by using the SQL Server Configuration Manager. If enabled, the default instance
of the SQL Server Database Engine listens on TCP port 1433. Named instances of the Database
Engine and SQL Server Compact are configured for dynamic ports. This means they select an
available port when the SQL Server service is started. When you are connecting
to a named instance through a firewall, configure the Database Engine to listen
on a specific port, so that the appropriate port can be opened in the firewall.
Configure a Server to Listen on a Specific TCP Port - SQL Server | Microsoft Docs
Windows Powershell command to test port openning:
Test-NetConnection -ComputerName sqlservername -Port 1433
How to replicate the DMZ Server SQL Access error:
SQL Server: No Inbound access to port 1433 and SQL Network Configuration for TCPIP is disabled
Changes to the DMZ IIS Server and Private SQL Server to allow HTTP/HTTPS and SQL Server access:
SQL Server Configuration Manger:
SQL Server (Private Server) allow inbound for port 1433 TCP and 1434 UDP
IIS server (DMZ) allow inbound for ports 80 and 443 (HTTP/HTTPS)
Verify Named Pipes security are configured on the MIP/Microix SQL Server
IF the DMZ server is configured on a virtual switch, it may be required to add a DNS address to the IIS server.
TEST SQL Connection Example:
image027.png
image001.png
image002.png
image003.png
OriginalEmail.eml
DataImage88.png
DataImage70.png
DataImage35.png
| Files | ||
|---|---|---|
|
|
image027.png
54 KB
|
|
|
|
image001.png
33 KB
|
|
|
|
image002.png
26 KB
|
|
|
|
image003.png
28 KB
|
|
|
|
OriginalEmail.eml
27 KB
|
|
|
|
DataImage88.png
18 KB
|
|
|
|
DataImage70.png
226 KB
|
|
|
|
DataImage35.png
123 KB
|