Hi Grant
> Hi Martin,
>
> One thing to check to is to see if DNS lookup is configured correctly.
> One thing you could quickly do is add the IP address of the client (or
> the firewall if you NAT between your internal LAN and the the DMZ) to
> /etc/hosts.
The response time from the 'nslookup' command for good and bad
target hosts is so close as to be identical. Ditto form those target hosts
to find the source host,

>
> Other than that it could be an issue with pam.d (pluggable
> authentication module) and another authentication source you might
> have configured
Not running pam on the target hosts.

>
> It might be worth using wireshark (might be known as ethereal in your
> Linux distro) to sniff the network to see what response the server is
> waiting for.

Can't find it on the host.

I'll download wireshark and see if the Sysprog will configure it for me....

Marty

>
> Regards,
>
> grant
>
> > -----Original Message-----
> > From: info-ingres-bounces@kettleriverconsulting.com
> [mailto:info-ingres-
> > bounces@kettleriverconsulting.com] On Behalf Of
> martin.bowes@ctsu.ox.ac.uk
> > Sent: 16 March 2007 12:45
> > To: info-ingres@kettleriverconsulting.com
> > Subject: [Info-Ingres] very slow login times - off topic
> >
> > Hi Everyone,
> >
> > This is a little off-topic but someone may me able to point me in
> > the right direction, so here goes.
> >
> > I have several brand new Linux hosts which are - as far as I can
> > tell
> -
> > identically configured. They all sit at the same region in the
> firewall
> > and
> > can all be contacted with ssh or scp.
> >
> > But one of the four takes an inordinate amount of time to respond to
> the
> > connection attempt. Try about 26s response versus sub-second
> > response - thats the sort of difference you tend to notice!
> >
> > Once the connection is established all is OK and response is
> > perfectly fine.
> >
> > Using ssh -v -v -v it appears that there are two choke points in the
> > connection.
> >
> > The first is a ten second or more pause at:
> > debug2: we sent a publickey packet, wait for reply
> >
> > The second is a similar pause at:
> > debug1: Entering interactive session.
> >
> > Anyone got any ideas what I should be looking at from here?
> >
> > Martin Bowes
> > --
> > Random Duckman Quote #33:
> > Ajax - If the answers not 'Isoceles Triangle' then I've wasted
> > another
> > year of school.
> >
> >
> >
> > _______________________________________________
> > Info-Ingres mailing list
> > Info-Ingres@kettleriverconsulting.com
> > http://www.kettleriverconsulting.com...fo/info-ingres
>