Networking :: sshd with router

Hi, I want to be able to use Linux through a ssh client (on my windows desktop PC) connecting to my laptop which is DSLinux. sshd can be started (I don't think it runs at bootup by default, anyway I generated the keys as described in the ssh installation instructions and have them in /etc/ssh.

The question is; if from the linux PC i type "ssh localhost" I can login to the system and I have a local ssh session. If I type "ssh <insert-IP-of-DSLinux-PC>" it works -from the linux pc-.

If you type on the Windows PC "ssh <ip-of-DSLinux-PC>" I get "Network error; connection refused".

I am wondering if my d-link firewall is having some sort of issues with the ssh at all, but don't know enough to be able to tell if there is something wrong. If I run Windows on both (XP;desktop, Me;laptop) there is full connectivity.

I'm confused; any help is greatly appreciated.

Thnaks for reading.
-Stu.

Okay,

It turns out that the SSHd is working correctly: if I boot my other PC with a Knoppix live CD and ssh to my DSL box I can login as root (!).

So the problem is then with my WindowsXP pc.

Can anyone recommend a Windows SSH client that actually works??? I've spent about 3 hours tonight trying to get this to work, I've downloaded every SSH client I can from http://freessh.org/ and am unable to find a client that won't give me the "connection refused" error.

The only other thing I can think of is that maybe I don't have the encryption or something ocnfigured correctly?

-Stu.

Is your "Internet Connection Firewall" enabled in XP?

That was once a source of trouble for me, and it was
enabled without my knowledge... (Probably chosen during
XP Install.. )

ke4nt

Thanks for the reply ke4nt. I got it working last night. The problem was not to do with my firewall.

The issue was with the protocols.

I had to add the following line to/etc/ssh/sshd_config:

Protocols 2

Then I set PuTTY to use "SSH 2 only" and it worked!

So thanks for replying, and if anyone else has this problem, and it's not your router, and it's not your firewall it's probably the protocols.

-Stu.

original here.