I'm not a Red Hat user (I prefer Debian...), but I know that in a lot of my
clients' places where we have Red Hat set up, upgrades to RH tend to be
troublesome -- RH has a habit of changing security settings and parameters
without notifying the end users. I would start by checking your inetd.conf
(or xinetd.conf if that's what RH ships now) and make sure it's still
set up
to accept the connection on 901 and fire up SWAT. You might also want to
make sure that inetd is running. 'chkconfig --list | grep inetd' should
do
it on RH -- make sure it's set ON for the appropriate run levels.
---
Keith Rinaldo
Systems Administrator
College of Engineering
University of Nevada, Las Vegas
Email: rinaldok@egr.unlv.edu
----- Original Message -----
From: "Jim Hale" <jim-ml@halemail.dyndns.org>
To: "Mailing List - Samba" <samba@lists.samba.org>
Sent: Thursday, July 04, 2002 7:05 AM
Subject: [Samba] Samba 2.2.5 - Swat Died
> I upgraded this morning to 2.2.5 on both my Linux boxes (Red Hat 7.3)
> and now SWAT doesn't work. I have it setup to start on a reboot and
I've
> tried force turning it off and then turning it back on. I can't even
> connect on the actual Linux box, let alone the Windows machines that I
> used to be able to connect with.
>
> I get that the connection was 'broken' for port 901. What can I do
to
> repair this?
>
> Thanks! :)
>
> Jim Hale
> ---
> http://hale.dyndns.org
>
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions: http://lists.samba.org/mailman/listinfo/samba
>