I had an issue with timeouts and SSH before (5.2 I think and 5.1 before
that). I was able to log in once after a reboot but attamts after the
first timed out. Searching the net told me that AllowUsers was an option
I shouldn't have enabled in sshd_config. Commenting out that line made
all the d
Here are the ping results:
ping statistics for 192.168.1.100: Packets : sent = 4, recieved = 4,
lost = 0 <0% loss>, Approimant round trip time in mili-seconds: Min =
1ms, max = 2ms average= 1ms
It's pingable at least
Matt
___
On 5/25/05, Jens Holmqvist <[EMAIL PROTECTED]> wrote:
> On 5/25/05, Charles Swiger <[EMAIL PROTECTED]> wrote:
> > On May 24, 2005, at 10:42 PM, Matt Smith wrote:
> > > I have a friend that has 5.4 where SSHD keeps timing out before
> > > authentification. Box has a hardwired 3com NIC. We've tried
On 5/25/05, Charles Swiger <[EMAIL PROTECTED]> wrote:
> On May 24, 2005, at 10:42 PM, Matt Smith wrote:
> > I have a friend that has 5.4 where SSHD keeps timing out before
> > authentification. Box has a hardwired 3com NIC. We've tried
> > everything
> > but can't find the cause of the timeouts.
On May 24, 2005, at 10:42 PM, Matt Smith wrote:
I have a friend that has 5.4 where SSHD keeps timing out before
authentification. Box has a hardwired 3com NIC. We’ve tried
everything
but can't find the cause of the timeouts. What gives?
Try "ping _machine_" and see whether that works.
Run
On Tue, May 24, 2005 10:42 pm, Matt Smith said:
> I have a friend that has 5.4 where SSHD keeps timing out before
> authentification. Box has a hardwired 3com NIC. Weve tried everything
> but can't find the cause of the timeouts. What gives?
Make sure DNS is working properly. You may also try
