From: Marko B. <bo...@ks...> - 2004-10-20 13:03:35
|
Ian Bonnycastle wrote: > This DOES sound like a network issue. Can you telnet to other ports? > What happens when you do so? (I mean, do you get the usual protocol > header, or does it just hang?) How are you running sshd on the coLinux > box? Is it by inetd or via a daemon process? If its by inetd, is sshd > being started properly? Is there a CPU spike when you telnet into port > 22? There are a varying number of factors that could cause sshd to > -snip- I run sshd as a daemon. I haven't noticed any spikes when telnet'ing. I can ssh from another box (same network), so I guess sshd is working properly. And now that you mentioned it, when I telnet to port 22, I don't get any kind of message from sshd ("SSH-2.0 ....") I'm also unable to connect with remote X session from the same machine, but from a different machine, things work ok... I haven't tried running it with TAP driver yet... I'l try that, too :) -- Marko ICQ: 5990814 I'm not under the alkafluence of inkahol that some thinkle peep I am. It's just the drunker I sit here the longer I get. |