can you ps -C or ps -aux |grep sshd or telnet to port 22 and see if sshd is running. also did you check you firewall rules? not trying to seem degrading just wanting to get in my head what steps have been taken.
--- Jason Dale <[EMAIL PROTECTED]> wrote: > Thanks, Jim. > > I'm not in the US, and it's going to be quite a long > while > before we have a holiday .... and no prizes for > guessing > what I'll be doing while some individuals on > this list are going to be drinking beers and > munching > hotdogs ;) > > B.T.W. I forgot to mention the /etc/securetty file. > I wonder if that's what is causing it? This file > looks like it is used to restrict root logins, but I > am not sure how it's logic works, or whether I need > to > send a SIGHUP to some bloomin' daemon after editing > it. The file contains a list terminal devices, so > probably > these are the terminals it (accepts?) root logins > from. > > Interestingly, the /etc/securetty file on my > RH 7.1 server contains tty1 thru to 8, but I can > still use PuTTY to access it remotely. As per usual, > this > server was set up by someone else, and it's > our (my) job to administer it. > > Jason > > > ----- Original Message ----- > From: <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Thursday, July 03, 2003 6:00 PM > Subject: Seawolf-list digest, Vol 1 #1744 - 3 msgs > > > > Send Seawolf-list mailing list submissions to > > [EMAIL PROTECTED] > > > > To subscribe or unsubscribe via the World Wide > Web, visit > > > https://www.redhat.com/mailman/listinfo/seawolf-list > > or, via email, send a message with subject or body > 'help' to > > [EMAIL PROTECTED] > > > > You can reach the person managing the list at > > [EMAIL PROTECTED] > > > > When replying, please edit your Subject line so it > is more specific > > than "Re: Contents of Seawolf-list digest..." > > > > > > Today's Topics: > > > > 1. RE:remote ssh denied (James P. Roberts) > > 2. dhcp (pump) (David J. R. Brook) > > 3. Re:dhcp (pump) (Steven W. Orr) > > > > --__--__-- > > > > Message: 1 > > From: "James P. Roberts" > <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > Subject: RE:remote ssh denied > > Date: Wed, 2 Jul 2003 18:18:33 -0400 > > Organization: Punster Productions, Inc. > > Reply-To: [EMAIL PROTECTED] > > > > > Hi, > > > > > > I have a Windows program that I use (Called > > > 'puTTY' to SSH from a Windows workstation > > > to a Linux server. This program works with all > > > of the Red Hat Linux and UnixWare 7 servers > > > that I have here at the office, and works with > > > my client's machines as well, saving for one > > > particular Red Hat 7 server. > > > > > > I tried loading the PuTTY program on a Windows > > > workstation on the same LAN IP Block as the > Linux > > > server itself. There is Samba on this machine, > and the > > > Windows work station is able to connect to it > fine. > > > > > > However, when I try to SSH to the Linux server > > > using root and the correct password, I get the > > > message 'Access Denied', even when I can SSH in > to > > > this Linux server from another Linux server > which is > > > also on the same LAN !! > > > > > > Also, when I am logged onto this troublesome > machine, > > > I can SSH to the Linux server at my office > accross the > > > WAN, but I cannot SSH back from that location to > the > > > offending Linux machine. In otherwords, the > command-line > > > SSH only works in one direction. I could not > find > > > anything in /etc/hosts.deny that could cause > this. > > > > > > Does anyone know what can be causing this? > > > > > > Thanks ! > > > > > > Jason > > > > > > > I can think of two possibilities. One is a > firewall rule. The other is > an > > ssh setting, something along the lines of denying > access to root, even > with a > > correct password. I forget the exact syntax, but > IIRC it is > self-explanatory > > when you see it. Try grepping the ssh config > file(s) for "root". > > > > Step one: Try logging in as someone other than > root. If it works, then > check > > the ssh config, as above. (Heck, check it > anyway). > > > > Step two: Review your firewall logs to see if > anything is getting blocked > > to/from either machine during an attempt. If your > firewall is not > logging, > > you may be able to figure it out with the -L -n > flags on the firewall > command. > > (I know it works with iptables, not sure about > ipchains). What I > sometimes do > > is: > > > > iptables -L -v -n >x.1 > > [do whatever I am testing, then] > > iptables -L -v -n >x.2 > > diff x.1 x.2 > > > > Just be aware that anything else that comes along > during the testing will > show > > up, too. > > > > Step three: Relax, have a beer and a hot dog, > watch some fireworks, and > > tackle it after the Holiday? (just kidding... I > don't even know if you > are > > in the U.S.) ;) > > > > Happy Fourth of July to you all, anyway. > > > > Regards, > > Jim > > > > > > > > --__--__-- > > > > Message: 2 > > From: "David J. R. Brook" <[EMAIL PROTECTED]> > > Subject: dhcp (pump) > > To: [EMAIL PROTECTED] > > Date: Thu, 03 Jul 2003 08:01:48 -0400 > > Reply-To: [EMAIL PROTECTED] > > > > I have an old pentium box running 7.1 that acts as > a > > firewall between my cable modem and home > computers. > > The external ip address is configured via dhcp > using pump. > > Problem is that the computer fails to renew the > lease on the > > ip address on a regular basis. If I log on to the > computer > > and type 'pump' it (somtimes) renews the lease, > but it > > doesn't seem to do it automatically. I called the > ISP > > (Comcast) to ask if there were any problems on > their end - > === message truncated === __________________________________ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com _______________________________________________ Seawolf-list mailing list [EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/seawolf-list
