Hi
my understanding about MS SQL server was that it didn't need to connect back to the client. Problem with connecting back to the client, is that if the client is behind a NAT, it just won't work, unless there is special protocol support in the NAT for the MS SQL protocol to see which ports to open back to the client.
In the past, customers have been able to connect to MS SQL servers using only a single mapped port (e.g. a TCP mapping proxy) 1433.
http://support.microsoft.com/kb/287932This mentions client port numbers, but only in the context of normal ephemeral ports assigned by the OS to any outbound TCP connection. It's not a requirement for the server to connect back in. The response packets to the outbound connection to the MS SQL server will be allowed by the NAT as part of its stateful TCP connection management... that's how a NAT works, and how any TCP connection can work through a NAT.
So, you should be able to remove that opened port range altogether. It's only there to allow access to other services running on the WinGate computer, such as FTP servers, or FTP clients.
Regards
Adrien