Re: SSHD working in a funky fashion
Ted Mittelstaedt wrote: Check your ssh key size, the newer versions of FreeBSD went from a 1024 bit key to a 2048 bit kay and some ssh clients can't deal with that big a one. Also check reverse DNS records for the IP's involved. Ted That's good info, even though the problem is solved. Thanks, Kurt ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: SSHD working in a funky fashion
Check your ssh key size, the newer versions of FreeBSD went from a 1024 bit key to a 2048 bit kay and some ssh clients can't deal with that big a one. Also check reverse DNS records for the IP's involved. Ted -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Kurt Buff Sent: Wednesday, March 01, 2006 1:18 PM To: Alex Zbyslaw; freebsd-questions@freebsd.org Subject: Re: SSHD working in a funky fashion On 2/28/06, Alex Zbyslaw [EMAIL PROTECTED] wrote: Kurt Buff wrote: sshd: fatal: timeout before authentication from 192.168.11.63 Can you ssh from one of your other FreeBSD boxes to this box? If not then try ssh -v -v -v which may point you in the right direction. Well, today it's working, but it's veeyyy slow to log into, from the Windows boxes. From the FreeBSD boxes it's just a bit slow to log in. If it's just Windows which can't login, then try running sshd in debug mode and see if that tells you anything. from man sshd -d Debug mode. The server sends verbose debug output to the system log, and does not put itself in the background. The server also will not fork and will only process one connection. This option is only intended for debugging for the server. Multiple -d options increase the debugging level. Maximum is 3. If none of that shows anything useful, then maybe you have some network level problem. Does any kind of connection from Windows work? E.g. Samba shared drive? Ftp? Or even (for testing only) telnet, since putty does that too? Don't have telnet or ftp running, but I'm able to browse the samba shares just fine. If it's a network level problem, then some more info about your topology might be helpful. E.g. are all these machines on the same LAN segment connected to the same switch? One Windows box is on a different subnet but the same (layer3) switch, one is on a different switch but same subnet, and the FreeBSD boxes (3 of them) are on the same switch and subnet. PS I assume you've tried your error message through google? Yup - lots of hits, but not much meat. Kurt ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.375 / Virus Database: 268.1.1/273 - Release Date: 3/2/2006 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SSHD working in a funky fashion
Kurt Buff wrote: On 2/28/06, Alex Zbyslaw [EMAIL PROTECTED] wrote: Kurt Buff wrote: sshd: fatal: timeout before authentication from 192.168.11.63 Can you ssh from one of your other FreeBSD boxes to this box? If not then try ssh -v -v -v which may point you in the right direction. Well, today it's working, but it's veeyyy slow to log into, from the Windows boxes. From the FreeBSD boxes it's just a bit slow to log in. Slow SSH authentication is often down to squiffy DNS resolution. Does the FreeBSD host know the names of the windows boxes? If you set UseDNS no in the sshd_config file (don't forget to restart sshd) does the login suddenly speed up? (I don't recommend that as a final solution, but if login does speed up then at least we know it's a DNS issue). --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SSHD working in a funky fashion
On 3/2/06, Alex Zbyslaw [EMAIL PROTECTED] wrote: Kurt Buff wrote: On 2/28/06, Alex Zbyslaw [EMAIL PROTECTED] wrote: Kurt Buff wrote: sshd: fatal: timeout before authentication from 192.168.11.63 Can you ssh from one of your other FreeBSD boxes to this box? If not then try ssh -v -v -v which may point you in the right direction. Well, today it's working, but it's veeyyy slow to log into, from the Windows boxes. From the FreeBSD boxes it's just a bit slow to log in. Slow SSH authentication is often down to squiffy DNS resolution. Does the FreeBSD host know the names of the windows boxes? If you set UseDNS no in the sshd_config file (don't forget to restart sshd) does the login suddenly speed up? (I don't recommend that as a final solution, but if login does speed up then at least we know it's a DNS issue). --Alex We have a winner! I installed the OS at the same time I was changing the IP addresses of my DNS servers, and put the old addresses in my resolv.conf. I am now a happier man. Thanks! Kurt ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SSHD working in a funky fashion
On 2/28/06, Alex Zbyslaw [EMAIL PROTECTED] wrote: Kurt Buff wrote: sshd: fatal: timeout before authentication from 192.168.11.63 Can you ssh from one of your other FreeBSD boxes to this box? If not then try ssh -v -v -v which may point you in the right direction. Well, today it's working, but it's veeyyy slow to log into, from the Windows boxes. From the FreeBSD boxes it's just a bit slow to log in. If it's just Windows which can't login, then try running sshd in debug mode and see if that tells you anything. from man sshd -d Debug mode. The server sends verbose debug output to the system log, and does not put itself in the background. The server also will not fork and will only process one connection. This option is only intended for debugging for the server. Multiple -d options increase the debugging level. Maximum is 3. If none of that shows anything useful, then maybe you have some network level problem. Does any kind of connection from Windows work? E.g. Samba shared drive? Ftp? Or even (for testing only) telnet, since putty does that too? Don't have telnet or ftp running, but I'm able to browse the samba shares just fine. If it's a network level problem, then some more info about your topology might be helpful. E.g. are all these machines on the same LAN segment connected to the same switch? One Windows box is on a different subnet but the same (layer3) switch, one is on a different switch but same subnet, and the FreeBSD boxes (3 of them) are on the same switch and subnet. PS I assume you've tried your error message through google? Yup - lots of hits, but not much meat. Kurt ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SSHD working in a funky fashion
On 2/28/06, luke [EMAIL PROTECTED] wrote: my initial guess is that your firewall is blocking ssh traffic, tcp port 22, on the interface you're trying to log in on. double check your firewall rules and make sure it's explicitly allowed No firewalls involved, sorry to say. See my response to ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SSHD working in a funky fashion
Kurt Buff wrote: I have set up a desktop box with 3 dual port Intel NICs as a router, which function it seems to be performing just fine. I used to be able to ssh into the box from my Windows machines with no problem, but now it hangs after I enter the user name - it won't come back with the password prompt. It's FreeBSD 6.0 Release, and I've installed samba/cups on it, with nothing else on it. I'm not seeing any particular errors in syslog or in dmesg, except when I try to connect to via putty from my Windows boxen. Then it says: sshd: fatal: timeout before authentication from 192.168.11.63 Can you ssh from one of your other FreeBSD boxes to this box? If not then try ssh -v -v -v which may point you in the right direction. If it's just Windows which can't login, then try running sshd in debug mode and see if that tells you anything. from man sshd -d Debug mode. The server sends verbose debug output to the system log, and does not put itself in the background. The server also will not fork and will only process one connection. This option is only intended for debugging for the server. Multiple -d options increase the debugging level. Maximum is 3. If none of that shows anything useful, then maybe you have some network level problem. Does any kind of connection from Windows work? E.g. Samba shared drive? Ftp? Or even (for testing only) telnet, since putty does that too? If it's a network level problem, then some more info about your topology might be helpful. E.g. are all these machines on the same LAN segment connected to the same switch? --Alex PS I assume you've tried your error message through google? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SSHD working in a funky fashion
my initial guess is that your firewall is blocking ssh traffic, tcp port 22, on the interface you're trying to log in on. double check your firewall rules and make sure it's explicitly allowed ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
