This is a discussion on ODBC, Sql Server and TCP/IP Ports within the MS SQL ODBC forums, part of the Microsoft SQL Server category; --> Hi all, I have one question that I think has not an easy solution. I have one SQL Server ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hi all, I have one question that I think has not an easy solution. I have one SQL Server (SQLSrv) and a server (CLISrv) that requires an ODBC entry to access to one database that exists on SQLSrv. For security reasons, I need to use TCP/IP port filtering on CLISrv and I will only allow some ports for communication. The problem that I have is that ODBC driver on CLISrv chooses a port for comunication on the public range of ports (1024-5000) and I do want to open all these ports. Does anyone know how to control the ports that ODBC driver side computer uses? The problem is on ODBC driver side, not on SQL Server side that uses 1433/1434 ports. Thanks in advance. Pedro PS. This is the second time I post this message. I though that maybe someone from Microsoft could help or give an answer, even that answer is "that's not possible to do what you want". After all, we don't know the source code... |