WinGate 7: Reverse Proxy for SQL server

[poohzai1990↑↓]

hi,
I'm beginner for WinGate, can anyone tell me how can I configure reverse proxy for sql server?

any recommended steps?

thanks a lot.

[adrien↑↓]

Hi

there are 2 options.

method 1: TCP mapping proxy.

1. WinGate > Control Panel > Services.
2. Choose "Install service" from the Tasks panel
3. Choose TCP Mapping Service

install TCP mapping.PNG (30.68 KiB) Viewed 14057 times

4. Choose Next, then Finish. Then fill out the properties. For SQL Server, the default port is 1433. Enable default mapping, enter ip of the SQL server (or name) as destination. No SSL.

SQL Server mapping.PNG (29.5 KiB) Viewed 14057 times

method 2: ENS redirect.

1. WinGate > Control Panel > Extended Networking > Port Security
2. Select "Connections from the internet" and "TCP" (these are the default selections)
3. Click "Add"

ENS Redirect.PNG (23.53 KiB) Viewed 14057 times

4. Click OK, OK.

[poohzai1990↑↓]

hi adrien,
thanks for your replied,
May i know is there anyway to proof connection is working after completed the configuration?

many thanks

[adrien↑↓]

Hi

did you try option 1 or option 2?

If option 1, you can just set your SQL client to connect to WinGate's IP. (actually I forgot a step in the setup - if you need to access this from the internet, you will need to go to the bindings tab and change the binding policy to bind to external interfaces).

If option 2, you'll need to connect back into your external IP from another internet connection. This is because ENS inbound relays aren't accessible from the inside of your network.

In both cases, you should see the connection in the activity window in WinGate Management

Regards

Adrien

[poohzai1990↑↓]

thanks adrien,
Saw it in activity window.

Thank you very much

[poohzai1990↑↓]

hi adrien,
the TPC mapping is successful, however it will be slow if there are a lot of connection since the data transferring with TCP stack.
so i would like to test with option 2. due to this, may i know do i need to uninstall tcpmapping service? or need to stop it? or just leave it there with the configuration?

many thanks

[adrien↑↓]

Hi

should just need to stop it.

That will remove the automatic ENS port entry that the TCP mapping service owns

Regards

Adrien

[poohzai1990↑↓]

hi adrien thanks for replied,
i failed to connect to the sql server. but when connecting i can see my machine on activity window.
I using "LAN connection to wingate PC". Since both machines are in same LAN not yet in internet.

below is the error that I get.
[SQL Server Native Client 10.0]Named Pipes Provider: Could not open a connection to SQL Server [1326].
[SQL Server Native Client 10.0]Login timeout expired
[SQL Server Native Client 10.0]A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.

any idea?

setting

Wingate-ENS1.jpg (74.62 KiB) Viewed 14016 times

[adrien↑↓]

Hi

Your native client is configured to use named pipes, which goes over the SMB port (445). You can't forward that.

You need to configure your Native Client to use TCP/IP. Looks like you need to install the Microsoft SQL server configuration manager to do that.

http://msdn.microsoft.com/en-us/library/ms191187.aspx

Otherwise can you use the MS SQL Server driver instead - is your application an ODBC-one?

For instance if you create a DSN using the MS SQL Server driver, you get a Client Configuration button, which allows you to select TCP/IP as the transport, and set port etc.

Adrien

[poohzai1990↑↓]

hi Adrien,
May i know is it possible to see client ip in server than wingate source ip?

many thanks.