Tyrion wrote: > James G. Sack (jim) wrote: >> So with everything else equal, your laptop (in Linux) can connect via >> ssh to mythbox over wired but not over wireless? >> >> > correct. > >> Hmmm.. >> You might try the verbose option, and posting the output. >> ssh -v [EMAIL PROTECTED] >> > did this and compared it to ssh -v 127.0.0.1 both are the same right up to > > debug1: Sending env LANG = en_US.UTF-8 > > at this point localhost connects and mythbox just sits there until it > times out with > > debug1: channel 0: free: client-session, nchannels 1 > Read from remote host 192.168.0.5: Connection timed out > Connection to 192.168.0.5 closed.
Yeah, openssh is not real good at telling the client why something failed <sigh>. > > >> You might temporarily remove the mythbox's ~user/.ssh/known_hosts file. >> (or just delete lines referring to your laptop ip and/or hostname) >> You might try posting the sshd_config from the mythbox. >> Is anything special in your mythbox ~user/.ssh/authorized_keys file? >> > I didn't really even look at this because this problem has persisted > through a complete format and reinstall so it's not likely to be the > mythbox settings. Well, the ~user/known_hosts file is not a mythbox settings result, it is a history result. I am very familiar with client problems when a server host key changes, but maybe something similar happens when the client's host key changes. I'm stretching here, but imagining that you get different IP's for wired and wireless, and that your earlier windows connection perhaps effectively interferes with connecting from the linux OS because the IP is the same but the hostkey is different. ==> Can someone with more expertise say whether this might be possible? Anyway, that was the reason I was suggesting removing the mythbox's ~user/.ssh/known_hosts file. If my wild speculation was correct, you could perhaps fix things up by duplicating the wired entry in the server's known_hosts but change the ip. I guess you would end up with 3 different entries for that one laptop. > > Thanks for the ideas, anyone have any more? Another place to look is in the mythbox /var/log/messages (or /var/log/secure) file for any log message telling that a connection failed. Regards, ..jim -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
