
BEST FREE SQL CLIENT FOR WINDOWS WITH SSH TUNNEL KEYGEN

I need some help on the possible ways to bypass this situation. Now, I know the SQLServerBrowser is listening on port 1434, under UDP protocol, and it seems it is not possible for SSH to tunnel an UDP protocol port.

In this case, I know the database instance port is 2048, as it was fixed this way to enable remote connection directly. Normally, a string like "SERVER01\SQLEXPRESS" is inserted here, and obviously something more needs to be addressed beacause this doesn't work.Īs I see it, this type of connection string will delegate to SQLServerBrowser an initial request to check the port under which the required instance. The remote client desktops will use a client application, and to configure the database connection the user is presented with a textbox to insert the database instance. This works like a charm, when I'm connecting directly to the database instance, but I'm having another big difficulty here. SSH client tunnel the communication, and the SSH server will deliver to SERVER01 (192.168.1.70). I can connect to the database using 127.0.0.1:2000 ģ. I use an SSH client to open a tunnel connection as above Ģ. So the situation is, on a remote computer:ġ. SERVER01: (IP 192.168.1.70) Windows 2003 Server, SQL Server 2008 Express, Instance name "SQLExpress" listening on TCP port 2048, SQLServerBrowser listening on UDP port 1434 LISTENER01: (IP 192.168.1.60) Windows 2003 Server, SSH service listening on port 22 with security and tunneling rules Router: Opens port 22 (SSH) and forwards requests to 192.168.1.60 (LISTENER01) Let's say that my external address is, and I have the following setup: So now I have my network, and setup a secure SSH tunnel to the SQL Server.

He just prefers to put the database somewhere else, and I agreed it would be a better solution to him. He also doesn't have any server, and doesn't want to have one. The reason is that he has 2 diferent networks that must access one instance of SQL Server. Now a client if it is possible to host his database on our server. The server is used from within the local network, and everything works flawlessly. I have a small network, which is connected to the internet, and that contains an SQL Server database. I need some help on setting up a convenient way to tunnel an secure access to a remote SQL Server database.
