Second SSH/MySQL connection uses existing tunnel from first connection #2359
Description
Description
Both sessions are set to use the same local port (3307 in my case).
Second connection to a testing server shows databases from the first one, so I'm reusing the first tunnel.
Probably because apphelpers.PortOpen(3307) fails?
Probably only on Windows?
In my case the command returns the expected string :3307 and should then use a different port:
$ netstat -na -p TCP
...
TCP 127.0.0.1:3307 0.0.0.0:0 ABHÖREN
HeidiSQL version
12.14.1.1
Database server version
Reproduction recipe
Open one SSH tunnel session, then another one. Watch out for the databases displayed in the second connection.