Secure Bridge and SDAC

tonibrown · Post by **tonibrown** » Thu 13 Mar 2008 22:52

Hi,

I just wanted to make sure my understanding is correct before getting much further with this.

I have been using SDAC for a couple of years. I want to connect to a SQL Server across the internet using SDAC and our main client application, but protected so that the remote SQL server does not have to expose port 1433 to the internet...

So can I use SecureBridge to achieve this with the SSH client and server components to route the SDAC connection through the SSH client component (which would be embedded into our main client application) which forwards to the SSH server, and onto the remote SQL server?

Thanks in advance

Toni Brown

Antaeus · Post by **Antaeus** » Mon 17 Mar 2008 08:13

Yes, you can do this. You should perform the following steps:

1. Install SSH server on the computer which runs SQL Server, setup it to listen a port allowed for remote connections, and run the SSH server. You can find an SSH server implementation within SecureBridge demos.
2. Add TScSSHChannel and TScSSHClient components to your client application to make an SSH client, and setup port forwarding from a local port to your SQL Server through the port listened by the SSH server. For example, see the SSHClient demo of SecureBridge.
3. Setup your TMSConnection to connect to the localhost on the port that you used for port forwarding. You can change port to which TMSConnection connects by setting the Server property in this format: serverName,portNumber.

tonibrown · Post by **tonibrown** » Thu 19 Mar 2009 10:36

Hi,

Will this become a problem if our users run two instances of our client application? By that I mean will one of the application instances intercept and try and route sql traffic to the remote server for all the instances?

Ideally we only want that instance to route sql communication coming from that instance of the application.

Thanks,

Toni

Dimon · Post by **Dimon** » Mon 23 Mar 2009 13:21

Problems will not be arised when you run two or more instances of your client application.
SSH port forwarding intercepts and transfers data for every MS SQL connection separately, just the same as if you don't use SSH.

sbrvar1 · Post by **sbrvar1** » Thu 01 Oct 2009 04:17

I'm trying to make sense of the SSHserver/client demo programs that come with SecureBridge and the code is not only attrocious but doesn't even work.

I managed to get server to run, finally, and to create new users and keys (because the one that was created originally - i could not see the password for it...). Now I have real issues making client to connect - always get socket error 10061. And that's with the default settings as well as with all different kinds of combinations that make sense to me - but obviously not to the server.

Is there any additional information or additional examples where one could try to understand what's required to make a simple connection from client to server?

I googled and there are no samples yet, I tried to find something here - and again... no go.

Regards,
Sabina

Dimon · Post by **Dimon** » Fri 02 Oct 2009 08:16

To run SSH server and SSH client perform the following steps:
- compile the SSHServerService project;
- install it calling the following command: SSHServerService.exe /install
- compile the SSHServer project;
- run this application, create a new user for authentication or use created user with username test and password test;
- start the service by pressing the "Start server" button;
- compile SSHClient project and run it;
- set the username and password fields and connect to SSH server;
- after this start port-forwarding.

You can find the detailed information about configuring and starting SSH server and SSH client in the "Step-by-step tutorial" topic of the SecureBridge help.