Operating System - OpenVMS
cancel
Showing results for 
Search instead for 
Did you mean: 

CIFS SAMBA V1.1-1 Alpha 8.3 - errors using share with no authentication

 
Peter Barkas
Regular Advisor

CIFS SAMBA V1.1-1 Alpha 8.3 - errors using share with no authentication

Following difficulties with mapping a drive (in a Windows service) to a Samba share, I decided to implement a share with no authentication so I could connect using the UNC.

This works but I see a number of errors in the logs and I don't know what is wrong.

SMB.CONF


[global]
workgroup = PHBWORLD
server string = Samba %v running on %h (OpenVMS)
security = SHARE
guest account = jetforms
log file = /samba$root/var/log_%h.%m
load printers = No
printcap name = /dev/null
ldap ssl = no
idmap uid = 15000-20000
idmap gid = 15000-20000
create mask = 0755
guest only = Yes
guest ok = Yes
hosts allow = 10.
vfs objects = varvfc

[JF]
path = DKA100:[jetforms]
read only = No
vms ods5 volume = Yes

LOG_TAL.SMBD

[2010/01/15 19:28:06, 0] SAMBA$SRC:[SOURCE.NSSWITCH]WINBINDD_PASSDB.C;1:(129)
Possible deadlock: Trying to lookup SID S-1-1-0 with passdb backend

[2010/01/15 19:28:06, 0] SAMBA$SRC:[SOURCE.NSSWITCH]WINBINDD_PASSDB.C;1:(129)
Possible deadlock: Trying to lookup SID S-1-5-2 with passdb backend

[2010/01/15 19:28:06, 0] SAMBA$SRC:[SOURCE.NSSWITCH]WINBINDD_PASSDB.C;1:(129)
Possible deadlock: Trying to lookup SID S-1-1-0 with passdb backend

[2010/01/15 19:28:06, 0] SAMBA$SRC:[SOURCE.NSSWITCH]WINBINDD_PASSDB.C;1:(129)
Possible deadlock: Trying to lookup SID S-1-5-2 with passdb backend

[2010/01/15 19:28:09, 1] SAMBA$SRC:[SOURCE.NSSWITCH]IDMAP.C;1:(377)
Initializing idmap domains

[2010/01/15 19:28:09, 0] SAMBA$SRC:[SOURCE.NSSWITCH]WINBINDD_PASSDB.C;1:(129)
Possible deadlock: Trying to lookup SID S-1-1-0 with passdb backend

[2010/01/15 19:28:09, 0] SAMBA$SRC:[SOURCE.NSSWITCH]WINBINDD_PASSDB.C;1:(129)
Possible deadlock: Trying to lookup SID S-1-5-2 with passdb backend

[2010/01/15 19:28:20, 1] SAMBA$SRC:[SOURCE.NSSWITCH]IDMAP.C;1:(377)
Initializing idmap domains

[2010/01/15 19:28:21, 0] SAMBA$SRC:[SOURCE.NSSWITCH]WINBINDD_PASSDB.C;1:(129)
Possible deadlock: Trying to lookup SID S-1-1-0 with passdb backend

[2010/01/15 19:28:21, 0] SAMBA$SRC:[SOURCE.NSSWITCH]WINBINDD_PASSDB.C;1:(129)
Possible deadlock: Trying to lookup SID S-1-5-2 with passdb backend
5 REPLIES 5
Shilpa K
Valued Contributor

Re: CIFS SAMBA V1.1-1 Alpha 8.3 - errors using share with no authentication

Hi Peter,

If you create the guest account "jetforms" in the CIFS database, I think you can access the CIFS shares without supplying the username/password. The account can be created using:

$ pdbedit -a jetforms
new password:AnyPwdWillDo
retype new password:AnyPwdWillDo

Regards,
Shilpa
Peter Barkas
Regular Advisor

Re: CIFS SAMBA V1.1-1 Alpha 8.3 - errors using share with no authentication

Shilpa thank you for the response.

I already have the username and the share is working fine but is logging the errors above.

Initially I did try using the share without the username and there were stack dumps.
Shilpa K
Valued Contributor

Re: CIFS SAMBA V1.1-1 Alpha 8.3 - errors using share with no authentication

Hi Peter,

Sorry, earlier I missed the working part.

These error messages should have been more of informational messages than the severity they indicate. The SIDs (S-1-1-0 and S-1-5-2) that the SMBD process is trying to lookup using WINBIND are neither built-in SIDs or SIDs corresponding to users or groups in the CIFS database. Due to this, WINBIND logs these errors. I think you may want to log a call with HP support so that you can completely disable WINBIND when you have configured CIFS server as Standalone server. This should not be a problem as WINBIND is not required when CIFS is a standalone server. This way you should be able to overcome the errors logged by WINBIND.

Regards,
Shilpa
Peter Barkas
Regular Advisor

Re: CIFS SAMBA V1.1-1 Alpha 8.3 - errors using share with no authentication

I found a presentation on CIFS that indicated that WINBIND is disabled by setting system logical winbinndd_dont_env true or by omitting the idmap uid and gid lines (I added these lines only to stop other error messages).

However, taking either or both of these steps did not stop the error messages.

Performance seems somewhat slow and so I think that there may be delays caused by these failures.

As the share is working, I wonder if it is best to wait for V1.2 and revisit these problems then.
Peter Barkas
Regular Advisor

Re: CIFS SAMBA V1.1-1 Alpha 8.3 - errors using share with no authentication

Next version may have better documentation on how to stop error messages.