Okay, I just wanted to make sure I wasn't sending a post that solved a problem
you didn't have, so that's why I asked.

But Mark may be correct, you may not have the server installed. You can have
the client installed and be able to connect to a remote machine, but will not
be able to connect to your own machine.  So run this command

rpm -qa |grep openssh
rpm -qa |grep telnet

That will tell you what packages for openssh and telnet are installed.  For 
example, on a friend's machine I ran those commands, and here's what I got
in return.

[timh@eric timh]$ rpm -qa |grep openssh
openssh-2.1.1p3-3mdk
openssh-askpass-2.1.1p3-3mdk
openssh-clients-2.1.1p3-3mdk
openssh-server-2.1.1p3-3mdk

[timh@eric timh]$ rpm -qa |grep telnet 
ktelnet-0.61-6mdk
telnet-0.16-4mdk
telnet-server-0.16-4mdk

So with out that openssh-server-2.1.1p3-3mdk, you will not be able to create
a ssh connection to that server.  So start out by trying that.

You will need to have a ssh key created.  Using the ssh-keygen command will 
walk you through setting that up.  Keep in mind the key's passwd, DOES NOT
have to be the same as that account's passwd.

So give that a try and let me know if that doesn't work. Then we can go from
there.
tdh
--
T. Holmes
Unixtechs.org
[EMAIL PROTECTED]
www.unixtechs.org/

"Real Men use Vi."

* Ben Edwards <[EMAIL PROTECTED]> [001226 17:24]:
> SSH, the reason the subject says telnet is because that is where the thread 
> started.
> 
> At 11:38 26/12/2000 , you wrote:
> >Wait a minute... I want to make sure I'm address the correct issue first.
> >Are you asking about a telnet issue?  Or a SSH issue?  Meanwhile the two
> >are tied in together, in a very round about way, but they are completely
> >different.  Let us know and I'll try and take it from there.
> >tdh
> >--
> >T. Holmes
> >Unixtechs.org
> >[EMAIL PROTECTED]
> >www.unixtechs.org/
> >
> >"Real Men use Vi."

Reply via email to