Unanswered: SQL Server Client Source Ports, So Many Opened!
I am attempting to run SQL Server replication across the public Internet inside a SSL VPN Tunnel (Aventail). The SQL Client (an MSDE database) initiating the replication selects random source ports for the connection back to the SQL Server at destination port 1433. Looking at a network sniffer multiple source ports are opened and used for even small replications, adding a great deal of overhead for the Aventail client, and slowing down replication times. I am not sure why multiple ports are used, seems very inefficient on Microsoft's part. I know I can't control which source ports the SQL Client will select, but can I control the number of source ports that are opened. My assumption is no, but maybe somebody has a creative solution.