locked
Can't get the real client IP address when using Netsh Interface Portproxy RRS feed

  • General discussion

  • Hi,

    For security considerations, we don't give our clients the real IP and port for connecting to SQL Server instances. So, we use Netsh Interface Portproxy to configure v4tov4 (IP1, Port1 -> IP2, Port2, IP2 is the real IP address for the server where running SQL Server, and Port2 is the port that SQL Server is listening on), therefore our clients can connect to SQL Server using IP1, and Port1 which is successfully.

    But there is one problem here, in the SQL Server (some views), we find the connection's IP address is not client's but displayed as IP1, which is not desired. I am wondering to know whether it is by design or there is some configurations that we miss.

    Thanks in advance. 


    Alex Feng | SQL Server DBA, ALIBABA.COM
    My Blog | MCTS: SQL Server 2008, Implementation and Maintenance
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    Friday, January 6, 2012 3:06 AM

All replies