Connecting to multiple servers via ssh tunnel bug
When connecting to multiple servers via SSH tunnel, it appears that heidisql uses the only one already established connection for all further connections. When changing a path to plink.exe in one connection, it magically changes in all other connections.
Yes, the location of plink.exe is not set for each session, but is a global setting, for conveniance reasons.
Make sure you use different local ports on the "SSH tunnel" tab, in order to get separate connection paths. Using the same port on 127.0.0.1 twice will result in a conflict.
Make sure you use different local ports on the "SSH tunnel" tab, in order to get separate connection paths. Using the same port on 127.0.0.1 twice will result in a conflict.
I am having the same issue but my sessions have different ips.
I have one for my local ip (127.0.0.1) and another for a remote ip (which has a local ip of 192.168.100.200). When I connect to my local one and then try to connect to the remote on it says I am not allowed and in the error msg I can see that it using localhost. When I connect first to the remote machine and then to my localhost the same thing happens but this time showing the 192.168.100.200 ip
I have one for my local ip (127.0.0.1) and another for a remote ip (which has a local ip of 192.168.100.200). When I connect to my local one and then try to connect to the remote on it says I am not allowed and in the error msg I can see that it using localhost. When I connect first to the remote machine and then to my localhost the same thing happens but this time showing the 192.168.100.200 ip
I am having the same issue but my sessions have different ips.
I have one for my local ip (127.0.0.1) and another for a remote ip (which has a local ip of 192.168.100.200). When I connect to my local one and then try to connect to the remote on it says I am not allowed and in the error msg I can see that it using localhost. When I connect first to the remote machine and then to my localhost the same thing happens but this time showing the 192.168.100.200 ip
Just do as ansgar advised.
Please login to leave a reply, or register at first.