Acessing SQL server

[amit]

Dear group,
I have recently had to install an application which uses/needs a direct connection to an SQL server residing on the internet. How can I configure my clients machine to access that SQL server. I have done TCP/IP mapping to the specific IP and the port on the wingate server.
My clients don't use WGIC.
thanks

[Pascal]

Do your clients use NAT ? Or direct proxy connections only ?

From the sound of it, with NAT it should all work transparently.

[amit]

Never used NAT before, dunno how easy it would be enabling it or to control access of the users.... any pointers.. you may know of.. that I should keep in mind... meanwhile I will try read some docs on NAT and how to use it in Wingate 5.x

[Pascal]

With NAT, you will need to authenticate OR identify the users in some fashion if you want to control access to them. The easiest way to do this is normally with Transparent Redirection in the appropriate proxies.

http://support.qbik.com/index.php?_a=knowledgebase&_j=questiondetails&_i=90&nav=+%26gt%3B+%3Ca+href%3D%27index.php%3F_a%3Dknowledgebase%26_j%3Dsubcat%26_i%3D1%27%3EGeneral+Networking%3C%2Fa%3E

That (rather long) URL will point you at a basic overview of NAT.

[amit]

thanks Pascal for the response and the link.. what would I need to configure on the proxy so that the users can access SQL server on the internet

[Pascal]

I'm not 100% sure what ports SQL server requires or how the client application is configured to access the server.

It should be relatively easy to determine what ports are required for the client application, and to simply create a TCP mapping service on the WinGate side that will listen on the port the application is expecting to connect to. That port should be redirected to the SQL Server on the port number it is listening on.

The you'd need to configure the client application to connect to the WinGate Server, which will effectively push that through.

With NAT though, you setup the application to connect to the SQL Server directly. It automatically does the 'mapping' for you.

[amit]

OK I finally tried connecting using the wingate internet client, and all works... meanwhile I will work on the NAT too... as that seems a better option.
FYI standard MsSQL port is 1433
thaks again