After Tunneling, Local New Con. R Made Thru Tunnel

[motin]

OR

Title: A tunnel and a local conn.cant work simultaneously

Desc: I have to add '%' to my local root-accnt

Simple: I have a local root account restricted to connecting from localhost. But when I first connect to my webhost (ip: 62.x.x.x) through ssh tunneling and then try to connect to my local root-account, I get: Access denied for 'root'@'62.x.x.x'.

This is rather annoying as it makes it impossible to synchronize between my webhost and local accounts without making them accessible from 62.x.x.x.

Not a big issue, but it would be convenient (and would it not be faster too?) if the local connection was made through the local system instead of the tunnel…

EDIT: This IS a greater issue than I thought. I cannot even access it when i allow '62.x.x.x' for that user, or even '%'!

I cannot sync…

EDIT2: A workaround: It was the fact that I used “localhost” to connect to my local server. I changed to the local ip-address and it works. Maybe it should be included in a FAQ somewhere that using “localhost” while doing any sort of tunneling will target the tunnel's localhost?

[peterlaursen]

Do you remember to uncheck the “Use tunnelling” on the tunnelling tab ?

Have you saved your connections with the “connections manager” ?

I can't reproduce your problem!

[peterlaursen]

OK …

Maybe I was a little bit too fast. I have no SHH-host available outside my own network, so there could be an issue that I can't reproduce. Buit if there is it must be an issue with the SSH-tunneling-daemon running on your lokal port locking hostname “localhost”.

But I have now tried with a dyndns-setup to my own SSH-server and still can't reproduce.

Could we se ALL tabs in the connection manager for the two connections ?

(you may 'paint' ip's etc.)

[Author]

Posts