SQL Server ODBC Port Filtering on a DMZ
I have a problem with my MS Server 2003 on the DMZ network requesting an ODBC
connection to another MS Server 2003 on my trusted network with SQL Server
The DMZ server has its ODBC configured to use port 1433 which is the
standard port for MS_SQL_Server.
I made a rule on the Firewall to allow port 1433 in order for incoming and
outgoing traffic from the DMZ to reach the SQL Server on the trusted network.
But it does not work because the DMZ Server makes the ODBC connection
request with a dynamic port number (it changes port numbers every time).
The good news is that the MS Server 2003 on my trusted network with SQL
Server 2000 listens with port 1433, as configured.
I verified this with the "netstat" command.
The ODBC connection only works when I allow "Any" ports from the DMZ to the
But, by doing this it will disavow the use of the firewall.
My question is...how can I force the MS Server 2003 on the DMZ to make the
request with a static port number instead of a dynamic port number?
|Tags: dmz, filtering, odbc, port, sql|
|Thread Tools||Search this Thread|
|Similar Threads for: "SQL Server ODBC Port Filtering on a DMZ"|
|Thread||Thread Starter||Forum||Replies||Last Post|
|ODBC driver Windows 2008 R2 Server||Andreas Sperling||Windows Server Help||1||12-06-2010 03:51 PM|
|Need Content filtering proxy server||Savannah87||Networking & Security||4||24-03-2010 02:01 AM|
|Tips to improve performance in SQL server and ODBC.||Florence_USA||Tips & Tweaks||3||29-01-2010 05:18 AM|
|Server 2008 Filtering is blocking even when turned off||Chris Harris||Windows Server Help||0||09-03-2009 11:36 PM|
|How to Export and import ODBC connections from one server to other||VauGhna||Window 2000 Help||1||20-06-2007 09:44 AM|