LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   *BSD (https://www.linuxquestions.org/questions/%2Absd-17/)
-   -   sshd refusing remote connection from SecureCRT (https://www.linuxquestions.org/questions/%2Absd-17/sshd-refusing-remote-connection-from-securecrt-331576/)

60s TV Batman 06-08-2005 11:52 AM

sshd refusing remote connection from SecureCRT
 
I've installed FreeBSD on one box, and have WinXP running on my other. They're connected via a Netgear ADSL router and cat5 cables.

I want to log in to FreeBSD from my WinXP box using SecureCRT. This works just fine between Fedora 3 and my WinXP box, so I know for certain that everything is set up correctly in SecureCRT.

sshd is set up for SSH2 and port 22, as is SecureCRT. I can log in locally using (for example) "ssh -l batman localhost", so I'm certain sshd is up and running.

I can ping the FreeBSD box from the WinXP box, and vice versa.

It would seem that sshd (or something else) is routinely refusing remote connections (in this case, remote being on the same network with 192.168.0.3 attempting to ssh into 192.168.0.2)

I suspect the problem lies with some other configuration setting that I...

1) Don't know about
2) Do know about, but am too ignorant to know how to set correctly

Anyone got any useful suggestions, leads, tips for me on this one?

scuzzo84 06-08-2005 04:02 PM

1. check if ssh is listening

dilara: {3} netstat -a | grep .ssh

2. do you have a firewall on that box?

3. run tcp dump on the bsd box and from the windows box try sshing to it and see if the bsd box gets any packets


dilara: {1} tcpdump port 22

4. try restarting ssh in /etc/rc.d ( this is from netbsd i think its the same for freebsd), go to /etc/rc.d/ and

dilara: {6} ./sshd restart

5. try rebooting the box

6. Anything in the log?

dilara: {12} cat /var/log/authlog

These are all just some ideas suggestions, hope it helps

60s TV Batman 06-08-2005 04:45 PM

Quote:

Originally posted by scuzzo84
2. do you have a firewall on that box?
Actually, I don't know. I didn't specifically elect to install one, so assume not.

As it turns out, I've just got it working by making a change to SecureCRT. I found a post on the Internet from another FreeBSD user with exactly the same problem.

For the benefit of others in this situation, the solution is to make a change in the properties dialog for SecureCRT. Under connection, change Authentication Primary from Password to Keyboard Interactive.

For some reason, this did the trick. No doubt, in time I'll found out why.

Thanks for taking the time to make those suggestions. It's always appreciated.


All times are GMT -5. The time now is 06:32 AM.