Wow, lots of help and all within an hour or so of asking. I could go into detail on each suggestion, I looked at them all, but it turned out to be an NIS problem. It was timing out trying to find the NIS server. The servers are up and running and serving and pingable, etc. but ypwhich simply can't seem to find any of the servers.
Actually several of the suggestions I received are still things I need to look into, so Thanks to all. Steve A > Return-Path: <[EMAIL PROTECTED]> > References: <[EMAIL PROTECTED]> > Content-Type: text/plain > Content-Transfer-Encoding: 7bit > Mime-Version: 1.0 > X-Note: This E-mail was scanned by Declude JunkMail (www.declude.com) for spam. > Approved-By: David Andrews <[EMAIL PROTECTED]> > Sender: Linux on 390 Port <[EMAIL PROTECTED]> > From: David Andrews <[EMAIL PROTECTED]> > Subject: Re: RH .vs. Suse login performance > To: [EMAIL PROTECTED] > > On Thu, 2002-04-11 at 11:46, Patterson, Ross wrote: > > > > That sounds to me like an identd- or tcpwrapper-related issue. > > Alternately, a DNS resolver issue. Check that the remote system > reverse-resolves (if not then perhaps there's a problem in your > /etc/resolv.conf), or (stopgap) that the remote system is named in > /etc/hosts. > > -- > David Andrews > A. Duda and Sons, Inc. > [EMAIL PROTECTED] Steve Arden [EMAIL PROTECTED] IBM-Global Services @ Lucent (630)979-7124
