Skip to main content
Server Fault

Return to Answer

Copy edited (e.g. ref. <http://en.wikipedia.org/wiki/PuTTY> and <http://en.wikipedia.org/wiki/IP_address>). IP is a protocol; it is IP addresses that are static, filtered, whitelisted, have different representations, that devices have, etc., not the protocol itself.
Source Link
Peter Mortensen
Peter Mortensen
  • 2.2k
  • 6
  • 23
  • 24

I've just tried with Windows 7 and it does not work for me either. The port will be forwarded, but not remapped, it. It will be still localhost:3306, which collides with the local server in your case. The puttyPuTTY documentation also says, that this would be the right way, but maybe the new security model of Windows Vista blocks the remapping of the ports.

I'd suggest, if you are using port 3306 locally, not to tunnel to localhost (which is normally mapped to 127.0.0.1), but to tunnel to another IP address in your loopback range (maybe 127.0.0.2). If your local SQL server is configured well, it only listens to 127.0.0.1:3306, your remote tunnelled SQL server can listen on 127.0.0.2:3306, so a remapping of the port is not necessary.

I've just tried with Windows 7 and it does not work for me either. The port will be forwarded, but not remapped, it will be still localhost:3306, which collides with the local server in your case. The putty documentation also says, that this would be the right way, but maybe the new security model of Windows Vista blocks the remapping of the ports.

I'd suggest, if you are using port 3306 locally, not to tunnel to localhost (which is normally mapped to 127.0.0.1), but to tunnel to another IP in your loopback range (maybe 127.0.0.2). If your local SQL server is configured well, it only listens to 127.0.0.1:3306, your remote tunnelled SQL server can listen on 127.0.0.2:3306, so a remapping of the port is not necessary.

I've just tried with Windows 7 and it does not work for me either. The port will be forwarded, but not remapped. It will be still localhost:3306, which collides with the local server in your case. The PuTTY documentation also says that this would be the right way, but maybe the new security model of Windows Vista blocks the remapping of the ports.

I'd suggest, if you are using port 3306 locally, not to tunnel to localhost (which is normally mapped to 127.0.0.1), but to tunnel to another IP address in your loopback range (maybe 127.0.0.2). If your local SQL server is configured well, it only listens to 127.0.0.1:3306, your remote tunnelled SQL server can listen on 127.0.0.2:3306, so a remapping of the port is not necessary.

Source Link
Manuel Faux
Manuel Faux
  • 507
  • 3
  • 13

I've just tried with Windows 7 and it does not work for me either. The port will be forwarded, but not remapped, it will be still localhost:3306, which collides with the local server in your case. The putty documentation also says, that this would be the right way, but maybe the new security model of Windows Vista blocks the remapping of the ports.

I'd suggest, if you are using port 3306 locally, not to tunnel to localhost (which is normally mapped to 127.0.0.1), but to tunnel to another IP in your loopback range (maybe 127.0.0.2). If your local SQL server is configured well, it only listens to 127.0.0.1:3306, your remote tunnelled SQL server can listen on 127.0.0.2:3306, so a remapping of the port is not necessary.