Switch to full style
Use this forum to post questions relating to WinGate, feature requests, technical or configuration problems
Post a reply

Wingate endpoint termination

Feb 26 18 10:51 pm

Will like to understand how Wingate handle the proxy for other service like Database. We will like to use Wingate to act as a proxy for our Microsoft SQL Server database. When the user initiates the connection to Wingate, does Wingate redirects the same connection out to the database server, or does Wingate creates a new connection and connects to the database server. In other words, does Wingate terminates the connection at itself, and then always creates a new connection?

In addition, when we access SQL Server, only certain users will be granted access to the database (via Windows Security Groups). The Authentication/authorization is handled by Windows directly via NTLM/Kerberos and not by Wingate, correct? Does WIngate store any of the username/password information?

Re: Wingate endpoint termination

Mar 04 18 9:04 am

for something like a SQL server mapping, you would typically use either an extended networking (packet level reverse NAT) redirect, or a TCP mapping proxy.

The TCP mapping proxy can do authentication if the client supports it using SSL and client certificates, but otherwise will not do any authentication.

The Extended Networking redirect won't do any of this, it just forwards packets.

Regards

Adrien de Croy

Re: Wingate endpoint termination

Mar 05 18 2:37 pm

I have read the TCP mapping service. It does not mention whether the connection terminates at Wingate Server and new connection is established to the destination.

http://help.qbik.com/index.php?topic_id=349

Anyway knows?

Re: Wingate endpoint termination

Mar 05 18 4:48 pm

Yes

the TCP connection terminates at the proxy, which then makes another connection (as configured) and relays data between the 2 connections.

Adrien
Post a reply