On 30 Dec 2002, Oleg Goldshmidt wrote:

>
> Hi,
>
> I must be really dense today, but there is something weird with samba
> on the RH7.3 system I am using at work.
>
> kernel-2.4.18-3
> samba-2.2.3a-6
> initscripts-6.67-1
>
> I start samba (with "/sbin/service smb start" or equivalent), get OK
> from both smbd and nmbd, and I expect to be able to use port 139 and
> port 901 (SWAT). I get "connection refused" on both.

901 is swat, not directly related to the samba daemons. The listener for
swat is (x)inetd.

>
> Things I've checked:
>
> * iptables -L: ACCEPT on everything.
>
> * /etc/hosts.{allow,deny} were both empty (apart from comments), I
> changed hosts.allow to "ALL: ALL", to no avail.
>
> * I put "hosts allow = 127." in smb.conf - no difference.

Not relevant. If it were a tcp-wrappers problem, then a connection would
have opened, but closed immdietly.

>
> * nmap says indeed that ports 139 and 901 on 127.0.0.1 are closed.

'netstat -lnt' ? Anything actually listening?
'netstat -lntp' ? What is it?

Ask your own machine before asking nmap

>
> * "smbclient -L 127.0.0.1" and "telnet 127.0.0.l 139" say
> "connection refused".
>
> * funnily, while "pgrep smbd" gives me a pid, "/sbin/service smb
> status" says "smbd is stopped" ("nmbd is running"), apparently
> because "pidof", called from the status function, does not return a
> pid.
>
> I must be missing something simple here. I'll be grateful for ideas.

What about 'ps auxww |grep smb' , in case you don't trust the init script
?

-- 
Tzafrir Cohen
mailto:[EMAIL PROTECTED]
http://www.technion.ac.il/~tzafrir




=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]

Reply via email to