Operation timmed out

Mark Weisman mark at mystic1.net
Sat Apr 3 00:26:09 PST 2004

This could also be caused by the wrong information about the key at
either the server or workstation. Simply locate the file known_hosts on
both computers to ensure that a key entry does not exist for the other
computer. If it does, delete it. If there are no keys, then the
possibility of a blocked port could be to blame. However, it's just my
two cents.

Res Ipsa Loquitor,
Mark-Nathaniel Weisman
Site Master
Mystic_One Internet Gaming Server
Anchorage, Alaska

-----Original Message-----
From: Vasil Dimov [mailto:vd at datamax.bg] 
Sent: Wednesday, March 24, 2004 9:53 PM
To: mrspock at esfm.ipn.mx
Cc: freebsd-questions at freebsd.org
Subject: ssh: Operation timmed out

> Hello FreeBSD gurus!
> I have a question for you.
> I have two computers, both of them running FreeBSD 2.5.1-RELEASE. Let 
> us call them A and B.
> Computer A receives ssh connections from computers running Linux, 
> Solaris and even Windows; it also receives connections from FreeBSD 
> 4.x and 5.1  but it does not receive ssh connections from B.
> A ask for password and then it takes a long time to say "Operation 
> timmed out" "Connection to A closed".
> Enabling "sshd" in rc.d or using it from inetd makes no difference.
> Strange, isn't it?
> Hope you can help me.
> Thanks in advance:
> PD.  Here you will find what "ssh -v A" dislays:
> B:/home/mrspock> ssh -v A
> OpenSSH_3.6.1p1 FreeBSD-20030924, SSH protocols 1.5/2.0, OpenSSL 
> 0x0090703f
> debug1: Reading configuration data /etc/ssh/ssh_config
> ...

try running
A:/windows> sshd -ddd
on computer A to see if anything happens.
freebsd-questions at freebsd.org mailing list
To unsubscribe, send any mail to
"freebsd-questions-unsubscribe at freebsd.org"

More information about the freebsd-questions mailing list