Samba & PDC Problems.

[Ty Roberts]

We occassionally get the following errors spewing out in our log.smbd. When we get these the only solution seems to be to stop all Samba Services (smbd, nmbd and winbindd) and to re-join the domain.

Has anyone seen these errors before and can anyone give me some explanation of the error that i can go on??

I get this in the log.smbd:
[2005/07/05 15:50:25, 0] auth/auth_util.c:make_server_info_info3(1080)
make_server_info_info3: pdb_init_sam failed!

And often this is a realted message in the log.winbindd:
[2005/07/05 15:21:26, 0] rpc_client/cli_pipe.c:rpc_api_pipe(424)
cli_pipe: return critical error. Error was NT_STATUS_PIPE_DISCONNECTED

I have done some research and have never found anything of worth or with any solution on this topic.

Thanks for all your help!

[Geoff Wild]

I have seen NT_STATUS_PIPE_DISCONNECTED in my log.winbindd - but didn't have to restart samba - nor re-join the domain...

I've never seen "pdb_init_sam" in log.smbd

Here's the main parts of my smb.conf:

bind interfaces only = Yes
security = DOMAIN
password server = ntserver1, ntserver2, etc
log level = 2
syslog = 0
log file = /var/opt/samba/log.%m
max log size = 10000
keepalive = 0
load printers = No
show add printer wizard = No
preferred master = No
domain master = No
wins server = ntserver1
idmap uid = 10000-20000
idmap gid = 10000-20000
template primary group = users
winbind separator = +
winbind enum users = No
winbind enum groups = No
read only = No
create mask = 0664
force create mode = 0664
directory mask = 0775
short preserve case = No
dos filetime resolution = Yes


Rgds...Geoff

[Alessandro Pilati]

Hi Roberts,
what version of samba do you have on your server?

[Alessandro Pilati]

The error indicates that no process is on the other end of the pipe.
The question is, do you need that NT clients can connect to NT SMB IPC$ pipes? if not, try to set "nt pipe support = no" in your smb.conf file.
Otherwise you should set correctly the "socket options" and delays in your smb.conf accordingly to your network architecture and traffic.

Hope this could be an help,

regards,
Alessandro

[Ty Roberts]

Here is a listing of the Global section of my SMB.conf if that would help:

# Global parameters
[global]
workgroup = WARPSPEED
netbios name = WPKGPRD02
interfaces = lan1
security = DOMAIN
encrypt passwords = Yes
password server = *
username map = /usr/local/samba/lib/users.map
deadtime = 15
preferred master = False
local master = No
domain master = False
wins server = 10.10.0.19 10.10.0.14
winbind uid = 1000-9999
winbind gid = 1000-9999
template homedir = /tmp
template shell = /usr/bin/false
winbind separator = +
guest account = smbguest
create mask = 0660
directory mask = 0770

I am running version 3.0.1, figured that the windbindd message is that there was no response, but I don't know why I would need to rejoin the domain or what what exactly that init_sam failed message means.

Thanks for the help so far..

[Ty Roberts]

Alessandro,
I am not sure what you mean by NT SMB IPC$ pipes, can you explain any further??

[Alessandro Pilati]

Roberts,
The option NT PIPE SUPPORT in the section global of smb.conf is used by developers to allow(yes=default) or disallow(no) Windows NT/2000/XP clients to make connections to NT-specific SMB IPC$ pipes, just as for example when you map a disk via smbmount or viceversa mount from windows. I read also that if you set this to no, maybe you cannot create directory in the share mapped.

The log you posted may indicate that a previously opened pipe ( for a connection of a share ) has been disconnected, and maybe the problem could be in the server that shares the resource.

Do the errors you posted stop the normal functions of your server?
Can you describe better your architecture and the kind of services you use?

Regards,
Alessandro