[Samba] U/G to 3.0.11, need explanation of log messages (Was:
Re: Trying to resolve issues on samba-3.0.11)
burgergold at hotmail.com
Thu Feb 17 22:51:32 GMT 2005
I've found the the help of abartlett that the first log message was
generated because samba was listening on port 139 and port 445. I've set
the parameter "smb ports = 139" and it has been resolve.
When this has been fixed, samba was now able to resolve the hostname for
each client. It still create a logfile log.ip that has a size of 0bytes,
but it writes in the log.hostname file.
For the third question, I can understand that the client will try to use
a guest authentication first, but it should not call the user_ok()
function since the guest ok is set to No. I'll probably ask the question
thanx for your help
Jonathan Johnson wrote:
> Changed the subject to something more meaningful that might get
> noticed by someone who knows. The original subject is too vague and
> See my comments below about "logfile name" and "guest on
> authenticate." Other questions left to others to answer.
> Yannick Bergeron wrote:
>> Recently, we undertook to upgrade our samba server 2.2.8a towards
>> version 3.0.11. There remain however still some issues which I try
>> to regulate or to understand.
>> OS: AIX 4.3.3
>> CC: ibmcxx 3.6.6
>> 1: "Software caused connection abort" in log.smbd
>> On every connection, I've the following error in my log. What could
>> be the problem?
>> [2005/02/14 16:43:22, 0] smbd/server.c:open_sockets_smbd(388)
>> open_sockets_smbd: accept: Software caused connection abort
>> 2: logfile name
>> The name of the log files are supposed to be log.hostname but some of
>> them are log.ip
>> How could this be possible? everything is ok with samba 2.2.8a
>> in smb.conf
>> log file = /usr/local/samba/var/log.%m
> I've noticed this too. Not sure why. Perhaps the first time a client
> connects, Samba uses the machine name, then for subsequent activity in
> that session it's using the resolved IP? Are the log.name files
> generated by smbd while the log.ip files are generated by nmbd? I
> don't really know. Regardless, I'd strongly urge you to change the log
> file to %m.log instead of log.%m, as log rotation scripts (see man
> logrotate) can be confused by having it your way. You end up with
> log.%m.0 and then log.%m.0.0 then log.%m.0.0.0 and so on, the logs
> never really get rotated properly.
>> 3: guest on authenticate
>> On every authentication, the guest account (nobody) is trying to
>> authenticate, the connection is refused, then it's trying with the
>> username. We would like the guest account to never be used.
>> in smb.conf
>> map to guest = Never
>> guest account = nobody
>> guest only = No
>> guest ok = No
>> in a log.hostname file
>> [2005/02/14 16:43:22, 0] smbd/password.c:user_ok(386)
>> rejected user nobody:3004-302 Your account has expired; please see
>> the system administrator.
> I would guess this is happening on the client side, not the Samba
> side. Your Windows machine may be first trying "guest" before trying
>> 4: Is there a way to know what is the OS of the client (logfile?
>> which debug level? which debug message?)
>> If anyone is able to answer or explain me one of those issues :)
>> Yannick Bergeron
>> burgergold at hotmail.com
More information about the samba