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@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: OpenSSH, Telnet, Windows Authentication and double-hops
    ... >> ssh -L) ... JM> in seperate DOS console windows in this order: ... I'm using the 3.8 version of OpenSSH. ... >> Kerberos ticket, or your password in order to acquire one. ...
    (comp.security.ssh)
  • Re: OpenSSH, Telnet, Windows Authentication and double-hops
    ... >> ssh -L) ... JM> in seperate DOS console windows in this order: ... >> Kerberos ticket, or your password in order to acquire one. ... JM> We're focusing on the OpenSSH for Windows distribution. ...
    (comp.security.ssh)
  • Re: FC6 VPN
    ... Then you can run any application you would like off the server by simply running it, or if you want to run a whole session, use gnomesession. ... ssh client that supports X forwarding, which is want you want to be looking at. ... SSH allows you to forward any local port to any remote port. ... If you need to connect to, say a windows share, you would forward your local port to the linux server through the ssh tunnel. ...
    (Fedora)
  • Re: OpenSSH, Telnet, Windows Authentication and double-hops
    ... deployment on a Windows network. ... Does this mean that you are setting SSH port forwarding ... does not provide the other side with either a Kerberos ticket, ... We're focusing on the OpenSSH for Windows distribution. ...
    (comp.security.ssh)
  • Re: Windows GSSAPI ssh connection via cross-realm authentication problems
    ... acess to the ssh server. ... Windows AD is primary kdc with realm name KDCTEST.COM and hostname ... the windows ssh client computer to be trusted for delegation. ...
    (comp.protocols.kerberos)