On Debian establishing SSH connection from Winswitch fails with the following error:

EE] 2012/10/08 02:13:11 format_util.logerr(SSH-2.0-OpenSSH_6.0p1 Debian-2)arguments are missing quotes
[EE] 2012/10/08 02:13:11 ProtocolHandler.handle_command(SSH-2.0-OpenSSH_6.0p1 Debian-2) command parsing failed
[EE] 2012/10/08 02:13:11 format_util.logerr(Protocol mismatch.)arguments are missing quotes:Protocol mismatch.
[EE] 2012/10/08 02:13:11 ProtocolHandler.handle_command(Protocol mismatch.) command parsing failed
[EE] 2012/10/08 02:13:11 ServerReceiver.connectionLost([Failure instance: Traceback (failure with no frames): <class 'twisted.internet.error.ConnectionLost'>: Connection to the other side was lost in a non-clean fashion.\n])
[EE] 2012/10/08 02:13:11 ServerReceiverConnectionFactory.clientConnectionLost(<twisted.internet.tcp.Connector instance at 0x4990f38>,[Failure instance: Traceback (failure with no frames): <class 'twisted.internet.error.ConnectionLost'>: Connection to the other side was lost in a non-clean fashion.\n])

In the first time I have made the connection to my remote computer via "New Connection" menu item. It was successful. My remote computer have been automatically added in "Servers" tab list in Configuration. But I can't connect to it via menu items. The system shows me "SSH authentication failed" message. I can only make connection via "New Connection"

P.S. Both systems - Ubuntu 10.04 P.S.S. Sorry for my English.

Windows clients can't mount a remote tunneled server since we can't tell them what port to use (sigh). So maybe we should always do a reverse mount? (server mounts shares from the client)
We need to find out the list of shares (pysamba?) and allow the user to configure what is mounted (read-only, password,...)

The actual mounting is the easy part:

mount.cifs //127.0.0.1/public ./guest -o port=21062 -o guest

But we have to make sure we always unmount stuff when the server goes down... Problem is that some files might still be open!

We should also deal with non-tunneled setups nicely: simply connect to SMB on client or server directly. This weighs in favour of supporting client-mounts-server option.

We can figure out what shares are available with (needs a bit of magic parsing... sigh):

smbclient -U guest -N -L localhost

or

smbclient -A /path/to/auth-file -L localhost

​pysamba does not seem to help here, unless I am missing something.

See bug #91 for the next step.