[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Allowing access to a newly installed machine


Ran through all of those tasks, and they're all as you say they should be.
I made sure to install everything from both CDs, but just did another:

   rpm -qa | grep ssh

and see all 5 packages running.  Further, I ran ntsys, and sshd is
checked.  I also did ps -ef | grep ssh and I show that sshd is running.

The message I'm receiving back from the client machines indicates that the
problem is not from sshd not running, but that I'm not being allowed
access.  I'm getting the message:

   Secure connection to jupiter.software-specialists.net refused.

This leads me to believe it is running, but not configured properly.  I'll
check my settings, but it looked like the appropriate lines were set up in
the ipchains file after the install.

- Mike

On Mon, 9 Apr 2001, Tom Diehl wrote:

> On Mon, 9 Apr 2001, Michael J. McGillick wrote:
> > Umm .. maybe I need to be a little clearer here.
> No, I think I understood.
> >
> > This was a fresh install of the wovlerine beta.  During the install, I'm
> > prompted with a screen that asks what level of security would I like, and
> > are there any services (you check off the box) that you would like to
> > have.  I checked the box marked SSH and the one marked HTTP.  Does the
> > install only allow access for a SSH client from the machine you're on
> > out, or does it also allow access for other SSH clients to come in?  HTTP
> > the same?
> It will allow connections to and from the box provided it is set up properly.
> In order for you to be able to ssh into a machine from another machine you
> need an ssh server running. Just to be sure you have what is necessary
> try rpm -qa | grep ssh. On the machine here I get
> (roo pts0) # rpm -qa | grep ssh
> openssh-askpass-2.3.0p1-4
> openssh-2.3.0p1-4
> openssh-server-2.3.0p1-4
> openssh-clients-2.3.0p1-4
> I am not 100% sure you _need_ askpass but you do need the others. Then you need
> to run ntsysv and see if sshd is checked. If not check it. That will allow it
> to start at boot. Then you can either run "/etc/init.d/sshd start" or do it the
> winbloze way and reboot if that makes you feel better. Rebooting is a waste
> of time though but it makes some people feel better. :-)
> A simple "/etc/init.d/sshd status" will tell you if the server is running or
> you could do a "ps auwx | grep ssh" and see if that returns anything. If none
> of the above works or I am somehow misunderstanding what you are trying to do
> try sshing to the machine in question and tell me what you get.
> As far as http goes you need the server to be running and properly set up for
> it to work.
> HTH,

        _ _
       (o o)

 Michael J. McGillick
 Internal Document Writer for the Symantec Corporation
 Email: mmcgillick symantec com
 Phone: 1-888-727-8671


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]