Zugg Software :: View topic - [2.03Pro] SSH to Windows Server causing gibberish

Wanderer Joined: 09 Jun 2006 Posts: 62 Location: Florida

I'm connecting to my own, local server. It happens to be running on Windows as opposed to a flavor of *NIX, so I'm wondering if that may be causing the problem... when I connect, I don't get an echo of any kind showing my prompt or anything, it's simply blank. When I type something such as 'ls -l' or 'dir', I get something that looks like...

Posted: Sat Sep 08, 2007 3:54 pm

What type of server are you connecting to? And what's the brand name?

Wanderer Joined: 09 Jun 2006 Posts: 62 Location: Florida

It's WinSSHD server (An... SSH server), by Bitvise. It's a simple SSH server; beyond that I don't know exactly what "type" it is, other than it accepts all of the encryption and comperssion protocols that CMud lists in its preferences and such.

Posted: Mon Sep 10, 2007 8:39 pm

When you get the error, go to the Tools menu and select Message Log. Copy/paste the contents of that into your forum post so I can see what error it might be getting.

Also, what version of Windows is the server running on? XP, 2003, Vista?

I am using a very robust 3rd party SSH component, and there are no reported problems with it on Windows. So it might be a bug in the Bitvise server. Is the Bitvise WinSSHD software up to date?

You can also go into your SSH Preferences and try changing the order of some of the SSH authentication and encryption protocols to see if you can get it to work that way. But I'd appreciate anything that you can find that might help. Or, if there is a way to set up an account for me on your server that I can test, please send me an email with the hostname and login information for me to test.

Wanderer Joined: 09 Jun 2006 Posts: 62 Location: Florida

I'll try getting a warning log and trying some of the other things. I thought it may be the Bitvise server as well, but two other SSH clients I use work fine with it, so it's hard to say if that's what it is. I'm running this on Windows Vista.

The output of the log is as follows:

Posted: Mon Sep 10, 2007 9:04 pm

OK, definitely try disabling various Encyption Algorighms in the Algorithm properties to see if you can find one that works. Also, you might try turning on the Force Compression option in the general SSH preferences to see if that helps.

Programs like PuTTY have obviously been doing this for a long time, so they might have some kludges coded to handle "problem servers".

Also, I've read some reports that on Windows 2003 Server (which would be similar to issues on Vista), that you need to connect to your actual IP address instead of using 127.0.0.1, so you might also try that.

Wanderer Joined: 09 Jun 2006 Posts: 62 Location: Florida

I went ahead and started using a different SSH server and I haven't been having the same problems. I still find it rather odd that my other SSH clients worked and CMud didn't, but I'm just going to be happy that I found a working alternative and say screw it. Thanks for the help nonetheless.

Posted: Tue Sep 11, 2007 12:08 am

Well, since the purpose of Beta Testing is to help me find problems, I'd really appreciate it if you could play with the settings as mentioned above and try to help track down the problem. I'm sure other users who have the same kind of SSH Server would appreciate it if I could fix this.

Wanderer Joined: 09 Jun 2006 Posts: 62 Location: Florida

I did try all of the things suggested (primarily changing the encryption protocol and such), but with no success. I don't have admin access to my local network and my sysadmin was refusing to give me rights to open port 22 so I couldn't do much about making you an account either. I'll keep trying to pick at it as much as I can, however, and see if there's something I can do.

Posted: Tue Sep 11, 2007 5:10 pm

Did you try using the actual IP address of the computer instead of using 127.0.0.1?

Wanderer Joined: 09 Jun 2006 Posts: 62 Location: Florida

Aye. I tried using localhost (which just maps to 127.0.0.1 anyway, I know), 127.0.0.1, and my internal network address as well. I also had a friend on another computer near mine SSH to my machine with the same results.