Leonard Bouchet wrote: > # Step 1: open the ssh tunnel > $ ssh -fNL 139:myserver:139 [EMAIL PROTECTED]
I'm surprised that this works. Normally if you try this on a windows machine the port forwarding setup will fail because the local SMB service on that machine is already listening on 139, and so it's impossible for ssh to bind to that port. How are you getting around this? Have you tried adding verbosity (-vvv) to the ssh command to see if there are errors setting up the port forwarding? Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
