Very Computer

by **Robert Moni** » Sat, 22 Mar 2003 00:11:57

Hi.

We just applied this update to some of our machines, and now when we
try to connect via ssh from an outside host, we get the message:
"Connection closed by 150.108.xx.xx". This happens prior to
authentication. We can connect to that machine with no problems from
other hosts within the 150.108 domain. Machines that are still on
glibc-2.2.93-5 are accessible as before from inside and outside the
domain. The connection attempts that fail do not generate any lines
in /var/log/messages or /var/log/secure.

We are trying to figure out what is going on here. Any clues?

Thanks,
Bob Moniot
Fordham University

by **Rex Diete** » Sat, 22 Mar 2003 00:45:19

Quote:> We just applied this update to some of our machines, and now when we
> try to connect via ssh from an outside host, we get the message:

You need to restart the sshd service after the glibc update.

-- Rex

by **Robert Moni** » Sun, 23 Mar 2003 03:39:34

> > We just applied this update to some of our machines, and now when we
> > try to connect via ssh from an outside host, we get the message:

> You need to restart the sshd service after the glibc update.

> -- Rex

That did it. We found that sendmail also needed to be restarted. At
that point we decided that a reboot would be a good idea, instead of
waiting to see what else might be out of order.

Thanks,
Bob

Very Computer

update to glibc-2.3.2-4.80 makes ssh refuse connections

update to glibc-2.3.2-4.80 makes ssh refuse connections

update to glibc-2.3.2-4.80 makes ssh refuse connections

update to glibc-2.3.2-4.80 makes ssh refuse connections