Samba problem setting UID and GUI

[Pierre Bilodeau]

I have another problem, this time with Samba.

It works almost OK, but still from my windows XP machine one time out of two, windows would complain about "Access to Drive:\FileName was denied" when accessing a file on the HP/UX Samba server.

The Samba.log file shows the following errors:

[2002/02/05 20:44:49, 1] smbd/files.c:(215)
file_init: Information only: requested 10000 open files, 1014 are available.
[2002/02/05 20:44:49, 0] smbd/service.c:(336)
bml logged in as admin user (root privileges)
[2002/02/05 20:44:49, 0] smbd/service.c:(336)
bml logged in as admin user (root privileges)
[2002/02/05 20:44:49, 1] smbd/service.c:(550)
pblaptop (10.232.60.94) connect to service bml as user bml (uid=0, gid=4) (pid 27677)
[2002/02/05 20:44:51, 0] smbd/nttrans.c:(2516)
call_nt_transact_ioctl: Currently not implemented.
[2002/02/05 20:44:52, 0] lib/util_sec.c:(69)
Failed to set gid privileges to (-1,-2) now set to (0,0) uid=(0,0)
[2002/02/05 20:44:52, 0] lib/util.c:(2381)
PANIC: failed to set gid

I see that it tries to authenticate me as "bml" which is my user ID on UNIX, and that indicates that the "users.map" file was used correctly as my windows UserID is different.

The weird things about the log:
1) call_nt_transact_ioctl: Currently not implemented.
What is this all about?
2) Failed to set gid privileges to (-1,-2) now set to (0,0) uid=(0,0)
Why is it trying to authenticate me as uid/gid -1/-2 when it recognized me as bml (uid/gid 106/4) in the first place.
3) PANIC: failed to set gid
Wow! That looks kinda serious!

When I try to open the same file that was denied on me, right after it opens up just fine.

When I try to create a new file on the samba directory, it creates it as user root?!

Can someone sched some light on this?

For more information, here is a copy of the smb.conf file.

Thanks in advance!

# Samba config file created using SWAT
# from 99.999.99.99 (99.999.99.99)
# Date: 2002/02/06 10:56:02

# Global parameters
[global]
workgroup = DDI_NT
netbios name = JAKE
server string = Jake HP Server
security = DOMAIN
encrypt passwords = Yes
password server = ARS-DB
username map = /opt/samba/lib/users.map
log file = /opt/samba/lib/samba.log
debug uid = Yes
max xmit = 16384
wins server = 99.999.99.99 /* Address removed intentionaly for this forum */
admin users = ms1 bml
create mask = 0664
directory mask = 0775
level2 oplocks = Yes

[appl]
comment = /appl Directory
path = /appl/
valid users = bml ms1 mf1
writeable = Yes

[out]
comment = /trdftpd/out Directory
path = /mnt1/trdftpd/out/
valid users = bml ms1 mf1

[bml]
comment = BML Home Directory
path = /home/bml
writeable = Yes

[harry d brown jr]

Pierre,

With this message:
"requested 10000 open files, 1014 are available"

what are the kernel parameters? (kmtune)

live free or die
harry

[Keith Lautenschlager · Accepted solution]

Pierre,

1) call_nt_transact_ioctl: Currently not implemented.
What is this all about?

This is not normally a problem, it means that some application, or function of the operating system, sent Samba a ioctl request via the nt transact smb, and that particular ioctl function is not implemented in Samba. Normally a well written app will simply fall back to a different way to doing it. Volumes of information on this message can be found on www.samba.org.

2) Failed to set gid privileges to (-1,-2) now set to (0,0) uid=(0,0)
Why is it trying to authenticate me as uid/gid -1/-2 when it recognized me as bml (uid/gid 106/4) in the first place.
3) PANIC: failed to set gid
Wow! That looks kinda serious!

This may be caused by the guest account. Some versions of Samba be default use the Unix user account 'nobody' for the guest account. If the user nobody has a uid of -1, and a gid of -2, this will generate this error in the log file. If this is the case on your system simply choose a different user account, one with a postive uid and gid, and set the guest account parameter in smb.conf to equal this new user account.

I believe the reason your files are being created as root, even though you've been authenticated as bml, is because you have admin users = ms1 bml in the global section of your smb.conf file. Samba treats anything you do as the "admin user" which in unix is root. Unless you have specific reasons as to why you would need to define your user account as the admin user, simply remove your uid from admin users and the files will be given the uid bml instead of root.

As far as file access failing, perhaps after trying the above if you still have issues you may want to increase the log level to 10 and reproduce the failure. More detailed logging might give a better reason why file access would fail, since the authentication appears to be working okay.

[Pierre Bilodeau]

Thanks Harry for the reply. Instead of fooling around with kernel parameters, I instead reduced the open file requirements in Samba from 10000 to 500, which will probably be sufficient for centuries!

Keith,

I assigned the guest account to "smbnull", since this account has been created by the Samba installation anyway. It has positive UID and GID (101/101).
I also remove the bml and ms1 userids from the admin users list, and then restarted the smbd and nmbd processed.

You know what? Everything now works perfectly. No more errors!

Thanks a million!