[Samba] fcntl_lock: lock failed at offset 0 count 1 op 13 type 0 (Resource temporarily unavailable)

2007-11-14 Thread Phil Burrow

Samba 3.0.26a, two different RHEL4 boxes and a Fedora 2 box.

I'm seeing this message whenever I do anything to nmbd with smbcontrol, 
for example smbcontrol reload-config or smbcontrol debug.


[EMAIL PROTECTED] samba]# smbcontrol nmbd reload-config
params.c:pm_process() - Processing configuration file 
"/etc/samba/smb_all.conf"

Processing section "[homes]"
Processing section "[netlogon]"
Processing section "[profiles]"
Processing section "[print$]"
fcntl_lock: lock failed at offset 0 count 1 op 13 type 0 (Resource 
temporarily unavailable)

Registered MSG_REQ_POOL_USAGE
Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED

It does not come up for smbd. I have noticed this message in the winbind 
logs an awful lot:


[2007/11/14 11:33:17, 3] libsmb/namequery.c:get_dc_list(1489)
  get_dc_list: preferred server list: ", *"
[2007/11/14 11:33:17, 3] lib/util.c:fcntl_lock(2004)
  fcntl_lock: lock failed at offset 0 count 1 op 13 type 0 (Resource 
temporarily unavailable)


I have quoted the previous line because that always precedes the 
fcntl_lock one.


My users have reported locking up of their XP machines when accessing 
Samba shares since I upgraded to 3.0.26a, so my first point of interest 
was to resolve any error messages. This being one of them.


Any pointers on this gratefully received!

Phil


--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba


Re: [Samba] wbinfo -u - do I need to worry?

2007-11-13 Thread Phil Burrow

Dale Schroeder wrote:

Phil,

Lots of group mapping and ldap changes in 3.0.23.  I don't do ldap, so I 
can't tell  you whether or not you need to worry.

You can probably figure it out at:
http://us4.samba.org/samba/docs/man/Samba-HOWTO-Collection/ChangeNotes.html#id343762 


and
http://us4.samba.org/samba/history/samba-3.0.25.html

Dale


Thanks Dale, that link was a great help.

--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba


[Samba] wbinfo -u - do I need to worry?

2007-11-12 Thread Phil Burrow

Hi all,

Will keep this brief :-) Just trying to clear some things up regarding 
winbind.


wbinfo -u returns "Error looking up domain users". I'm only using 
winbind for ntlm_auth which works fine. I'm not using AD or any Windows 
server-based domain. Samba only. There don't seem to be any obvious 
errors in the winbind log. Do I need to worry about that error? Should 
it list my full user list?


I've recently upgraded to 3.0.26a from 3.0.14 and noticed Samba has 
added a couple of extra groups on my LDAP server: sambaSID=S-1-5-32-544 
and sambaSID=S-1-5-32-545. One has displayName:Administrators and one 
has displayName:Users. These two groups are the only ones that appear 
when I do wbinfo -g. What are these and do I need to worry about them?


wbinfo -D seems to work, wbinfo -t seems to work.

Cheers,

Phil

--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba


Re: [Samba] Help cleaning up domain SID mess...

2007-07-30 Thread Phil Burrow

Bjoern Tore Sund wrote:

> No Windows here, this is the cifs disk server for 800 Linux clients.
> None of which are members of the domain in any meaningful way.  I just
> want all the servers to authenticate against the same LDAP server, the
> domain is irrelevant for functionality.  Hmmm.  Which means that I might
> just get away with setting the same SID on all four domains and leave it
> at that... ?
>
> -BT

Makes sense if thats all you need and theres no Windows stuff to break, 
yep :) Sorry for being presumptuous about your setup!


You would need to remove three of the sambaDomainName entries if you 
only want a single domain though, and ensure that the only one present 
is sambaDomainName=UNIX.


When you do net getlocalsid, it should be looking up the details for the 
domain you specified in smb.conf (UNIX) in your LDAP directory. Check 
your logs, see if it's happening and see what questions it's asking your 
LDAP server, that way you can see where it's getting its unusual SID 
information from and why it may not be setting the SID like it should.


i.e. on one of my broken systems that I use for playing about with 
stuff, I just booted to test it and I can see that if I do net 
getlocalsid its looking for:


smbldap_search_domain_info: Query was: dc=mydomain,dc=co,dc=uk, 
(&(objectClass=sambaDomain)(sambaDomainName=MYDOMAINFROMSMB-CONF))


Phil

--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba


Re: [Samba] Help with ldap configuration please

2007-07-30 Thread Phil Burrow

Adam DiCaprio wrote:
> This is on RHE4, I am getting an invalid DN error. Is there a good 
resource
> site for this type of configuration issue? There is a lot of info 
that comes
> up through google but I am having no luck finding anything relevant 
(or that

> seems relevant to me). Thank you in advance and sorry about the newbie
> question.
>
> ldap_connect_system: succesful connection to the LDAP server
> smbldap_search_domain_info: Got no domain info entries for domain
> add_new_domain_info: Adding new domain
> add_new_domain_info: failed to add domain dn=
> sambaDomainName=HFC,dc=hfc,dc=com with: Invalid DN syntax
> invalid DN
> smbldap_search_domain_info: Adding domain info for HFC failed with
> NT_STATUS_UNSUCCESSFUL

Hi Adam,

Do you have a root entry in your LDAP directory for: dc=hfc,dc=com?

If not, you need to add one because Samba wont add it for you. For 
example, this LDIF:


dn:dc=hfc,dc=com
objectClass: dcObject
objectClass: organization
o: hfc
dc: hfc

I would assume that not having this would cause Samba to complain that 
it can't add your domain to the LDAP directory, because you can't add an 
entry below a root that does not exist.


You can't just install OpenLDAP, install Samba, run them both and expect 
it to work. You need to prepare your OpenLDAP setup first! There is a 
script called smbldap-populate which can put a bunch of default entries 
into your LDAP directory. Have a look at:


/usr/share/doc/samba-3.0.X/LDAP/smbldap-tools-0.X/smbldap-populate

(obviously replace the X with your version)

And make sure you read the README and INSTALL and doc/ stuff in that 
directory too. If you don't have the smbldap-tools stuff in your Samba 
directory you can always get the latest version from 
https://gna.org/projects/smbldap-tools/


HTH,

Phil


--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba


Re: [Samba] Help cleaning up domain SID mess...

2007-07-30 Thread Phil Burrow

Bjoern Tore Sund wrote:

>> If you do "net getlocalsid" on each of your SLES machines, the SID
>> that is returned should be the same for all of them if you want them
>> all to be controllers on your domain. If it's not, pick the SID you
>> want - i.e. the sambaSID all your users have in their LDAP records -
>> then "net setlocalsid MYDOMAINSID" on the servers you wish to change
>> to that SID. (NB: On a domain, "net getlocalsid" and "net getlocalsid
>> MYDOMAIN" should return the same.)
>>
>> Then go into your LDAP directory and delete all but one of the
>> sambaDomainName=UNIX entries, and ensure the remaining one has
>> sambaSID set to MYDOMAINSID.
>>
>> That is probably all you need to do.
>
> Thanks a lot.  The last remaining quiestion is then what happens when I
> rename sambaDomainname=ukl-samba to sambaDomainname=unix and proceed
> from there?

This is why you need to test it before doing it ;)

If your intention is to consolidate your 4 domains into one, with a PDC 
and some BDCs then provided the sambaSID in the user records is the same 
as the domain SID then your setup - with your 4 servers each having the 
same SID - should work correctly.


You might need to re-add your client machines to the new domain. I dont 
know if Windows could handle the domain name changing but having the 
same SID.


If you are using roaming profiles or things such as this you might 
encounter Windows complaining if the SID changes, but if you use the 
sambaSID you used already have then it shouldn't do.


Cheers,

Phil

--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba


Re: [Samba] Help cleaning up domain SID mess...

2007-07-29 Thread Phil Burrow

Bjørn Tore Sund wrote:
>
> I have four SLES 10 servers working as Samba servers on the same domain
> with an LDAP account backend.  Relevant smb.conf entries are:
> [global]
>workgroup = UNIX
>realm = UNIX.UIB.NO
>server string = ukl-samba
>netbios name = ukl-samba
>security = user
>allow trusted domains = yes
>domain master = yes
>local master = yes
>encrypt passwords = yes
>
>
> Only one of the servers is set as domain and local master, server string
> and netbios name obviously differ while workgroup and realm are set to
> the same.  When I first set them up (smbpasswd -w, etc.) they created
> seperate sambaDomain entries in the LDAP root, with separate SIDs.  the
> sambaDomain entries are named after each server.  The user SIDs we
> simply set to be based on the SID of the first server we set up.

> effectively broken.  On startup, every single user (all 35. of
> them...) would get a line in /var/log/messages:
> ukl-samba smbd[16336]:   User  with invalid SID  in passdb
>
> Nobody could get at the Samba shares until I edited the LDAP tree to
> switch the SIDs between this server and the server with the SID the user
> SIDs were based on.
>
> start.  I was hoping someone here had an answer which saved me the
> trouble of setting up a full test domain with LDAP and Samba-servers...
> Can I just set the same SID on all four domains?  Or delete three of the
> four domains and rename the one with the correct SID to the _domain_
> name in sted of the server name?
>
> Thanks,
>
> Bjørn
>

Hi Bjørn,

From what you mention here it sounds like you have four 
sambaDomainName=UNIX entries (objectClass: sambaDomain) with different 
sambaSID attributes. Effectively 4 different domains, on 4 different 
servers all with the same name.


Users have a sambaSID entry in their LDAP record, and the first portion 
of this needs to be the same as the sambaSID for the *domain* they are 
logging on to. If it's not then it wont work.


In answer to your point at the end, yes you can do this and it is what 
you are "supposed" to do, as far as I know.


If you do "net getlocalsid" on each of your SLES machines, the SID that 
is returned should be the same for all of them if you want them all to 
be controllers on your domain. If it's not, pick the SID you want - i.e. 
the sambaSID all your users have in their LDAP records - then "net 
setlocalsid MYDOMAINSID" on the servers you wish to change to that SID. 
(NB: On a domain, "net getlocalsid" and "net getlocalsid MYDOMAIN" 
should return the same.)


Then go into your LDAP directory and delete all but one of the 
sambaDomainName=UNIX entries, and ensure the remaining one has sambaSID 
set to MYDOMAINSID.


That is probably all you need to do.

HTH,

Phil

--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba


Re: [Samba] New HP Printer Drivers wont upload (samba 3.0.11)

2005-03-15 Thread Phil Burrow
Luca Olivetti wrote:
Phil Burrow wrote:
Is there a fix? Is it just that HP's new drivers don't work with Samba? 

Yes, probably. The only printers that gives me problems here are hp 
printers. Other printers we have here gave me no problem at all.
For a deskjet 5800 I had to use the linux driver (foomatic/hpijs) and 
load the adobe ps driver, its windows driver would upload fine (in samba 
3.0.10, the same error as you with samba 2.2.8) but then give plenty of 
exceptions on the windows client (to the point that I had *no* way to 
access the printer or remove it: I had to do it on the server using 
rpcclient).
I hadn't really noticed any problems with drivers until I came across 
this problem, because most of our printers are relatively old (LJ 4000) 
and the drivers worked. But since we got a couple of Laserjet 4200tn and 
4250tn it's been extremely frustrating.

I did manage to make it take the LJ4200tn driver on a different server 
running 3.0.10, but I did have this exact problem for a while on there. 
I must have just done something by accident and it just worked. That's 
why I thought there may be a trick.

But other drivers do work so I don't think I'm doing anything wrong..
Phil
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba


Re: [Samba] New HP Printer Drivers wont upload (samba 3.0.11)

2005-03-15 Thread Phil Burrow
Gerald (Jerry) Carter wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Phil Burrow wrote:
| I'm trying to upload the latest Windows XP PCL6
| driver for our Laserjet  4250TN to my Samba 3.0.11
| server. It works, and uploads the driver files,
| but then at the end it produces an error on the
| XP client "the  operation could not
| be completed". The logs on the samba server state:
|
| move_driver_to_download_area: Unable to
|   rename [W32X86/HPC4250C.INI] to [W32X86/3/HPC4250C.INI]
if you send me the driver archive or download URL, I'll
take a look.
Hi Jerry,
Here's the link to the Windows 2000/XP PCL6 driver for the LaserJet 4250TN:
ftp://ftp.hp.com/pub/softlib/software4/COL9171/lj-24660-2/lj4250_4350pcl6win2kxps2003-en.exe
Cheers,
Phil.
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba


[Samba] New HP Printer Drivers wont upload (samba 3.0.11)

2005-03-14 Thread Phil Burrow
Maybe there's a trivial solution to this, but it's confused the hell out 
of me.

I'm trying to upload the latest Windows XP PCL6 driver for our Laserjet 
4250TN to my Samba 3.0.11 server. It works, and uploads the driver 
files, but then at the end it produces an error on the XP client "the 
operation could not be completed". The logs on the samba server state:

move_driver_to_download_area: Unable to rename [W32X86/HPC4250C.INI] to 
[W32X86/3/HPC4250C.INI]

I've tried the PCL5e and PS drivers and I get similar errors. The 
filename it's complaining about does get uploaded, as I spammed 'ls' 
when it was uploading to the server and saw it, but upon error a small 
number of files end up in the W32X86/3/ and the rest of them disappear.

But bizarrely if I try the Laserjet 4000 series PCL6 drivers, they work 
absolutely fine. Fortunately for me this driver is entirely compatible 
with the LJ 4250TN printer. But I'd still like to get the proper driver 
on there if possible.

I've tried:
-Clearing the tdb files.
-printer admin = root, @"Domain Admins" in global instead of printers/print$
-Logging on as different users (but all in printer admin) - it seems 
only Administrator/root has the option to upload a driver as it's greyed 
out even for people in printer admin. I guess this is a recent Microsoft 
restrictware patch and I'll have to plough the registry to change it.

Is any of this a known issue?
Is there a fix? Is it just that HP's new drivers don't work with Samba? 
Out of interest I tried uploading random drivers and some would upload 
and some wouldn't (giving the same error as above if they wouldn't).

Appreciate any guidance!
Thanks
Phil.
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba


[Samba] spoolss_io_r_setprinter/WERR_ACCESS_DENIED on 2.2.7a

2003-01-27 Thread Phil Burrow
I am unable to 'Apply' new drivers to any printers shared on my Samba 2.2.7a
machine from a Windows XP machine. I log in as root, the drivers upload to
print$ without a hitch. But when I click 'Apply' or 'OK' to close the
printer properties dialog box, I get 'Cannot set printer properties. Access
denied'.

The printer is a Hewlett Packard LaserJet 4100TN, the driver is the PCL 6
one from the installer CD that shipped with the printer.

The root user is a printer admin and in the write list for the print$ share.
Here's some level 10:

[2003/01/27 12:20:57, 10] printing/nt_printing.c:get_a_printer(3306)
  get_a_printer: [lj4100tn-2-bl] level 2 returning WERR_OK
  Converting info_2 struct
[2003/01/27 12:20:57, 7]
rpc_parse/parse_spoolss.c:uni_2_asc_printer_info_2(5346)
  Converting from UNICODE to ASCII
  start converting
[2003/01/27 12:20:57, 5] rpc_server/srv_spoolss_nt.c:check_printer_ok(4868)
  check_printer_ok: servername=\\blak_srv printername=\\blak_srv\HP LaserJet
4100 PCL 6 sharename=lj4100tn-2-bl portname=Samba Printer Port drivername=HP
LaserJet 4100 PCL 6 comment=HP LaserJet 4100TN, 2nd Floor location=
[2003/01/27 12:20:57, 5] rpc_parse/parse_prs.c:prs_debug(60)
  00 spoolss_io_r_setprinter
[2003/01/27 12:20:57, 5] rpc_parse/parse_prs.c:prs_werror(647)
   status: WERR_ACCESS_DENIED
[2003/01/27 12:20:57, 5] rpc_server/srv_pipe.c:api_rpcTNP(1218)
  api_rpcTNP: called api_spoolss_rpc successfully


-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba