similar to: 3.0.3 bug when in > 16 Unix groups

We have a Sun E450 running Solaris 8 and Samba 2.2.8a as our domain controller. We have had no problems with Samba until earlier this week when we have started to get lots of these errors in log.smbd: [2003/08/08 16:29:14, 0] lib/debug.c:(348) Unable to open new log file /home/samba_pearl/var/log.smbd: Too many open file s This has been happening once a day, at the same time some users are not

We have a Windows 2003 server that is a member of a Samba 2.2.8a domain. We can browse to this Samba server through "My Network Places" and map a drive to a share on this server. We also have a number of Samba 3.0.1 servers (running Solaris 8 and Red Hat 7.0). These are member servers of the Samba 2.2.8a domain. Using "My Network Places" on the Windows 2003 server, double

Tried to upgrade our Samba 2.2.8a domain controller (Solaris 8) to Samba 3.0.2a. Compiled using gcc 3.3.2, linked to libiconv-1.8, popt-1.7 and cups-1.1.20. I shut down the Samba 2.2.8a. Removed everything in var/locks. Did a "make install" to install 3.0.2a, then restarted Samba. My smb.conf is basically the same as 2.2.8a with "domain admin group" removed. When I stared

We've got a Windows 2003 server which won't join our Samba domain, it just sits their forever after I give the root password to join. It doesn't give an \ error message or "Welcome to domainxyz" message. It also won't join a workgroup, which is strange. Has anyone else seen this problem? No problems with XPSP2 clients. Not got 2003 SP1 on yet, might try that next.

Just setup a new domain controller running Samba-3.0.20b. Using smbpasswd file (no LDAP). How do I setup a group of users so they become domain administrators? I thought I just typed this: % net groupmap modify ntgroup="Domain Admins" unixgroup=ntadmin I am in group unix ntadmin, but I'm it doesn't seem to work. Michael -- Michael Keightley

Have just upgraded from 3.0.13 to 3.0.20 on our Solaris domain controller. Machine is also print server running CUPS-1.1.23. We have a RICOH network printer that we print to via Samba (the printer seems to have a builtin Windows PC). smbspool is linked to /usr/lib/cups/backend/smb and the appropriate DeviceURI is in /etc/cups/printers.conf. This works fine with 3.0.13, but with 3.0.20 I get this

Just swapped our Solaris SAMBA PDC for a SuSE Linux machine. It's the domain controller as well as print server (via CUPS). It's running SuSE 9.3 with Samba-3.0.20b. The setup is identical to the old Solaris machine, had to re-add all machines to the domain. Has been working OK for 2 days then suddenly some people couldn't print and I can no longer add printers to any XP machine.

We're using Cups and Samba with Adobe Postscript Drivers to print from XP SP2 machines via our Solaris and Linux Domain Controllers. Everything has been working OK, but when I setup an a new printer (identical ppd file to another one), it doesn't download the drivers on XP when I add the printer. This is happening on two domain controllers in different offices. It gives the error when

Upgraded the domain controllers in our 2 sites from 3.0.20 to 3.0.22. The one running Suse Linux is working fine, but the Solaris 8 domain controller doesn't list any XP machines in its browse list (the Firewall is off on the XP machines). Lists Unix machines, 2000 and 2003 machines. This was all working in 3.0.20. Has anything changed? Below the global part of our smb.conf:

Our domain controller is running Samba 2.2.8a on Solaris 8. We have XP laptops. We swap between a builtin network card, docking port and wireless card. All of these have separate IP addresses. If I say, boot up with the wireless card, then remove it and use the builtin network card, the IP address in wins.dat on the server doesn't change. It still has the IP address of the wireless card.

# smbd -Fi -d 2 smbd version 3.5.4-62.fc13 started. Copyright Andrew Tridgell and the Samba Team 1992-2010 uid=0 gid=0 euid=0 egid=0 rlimit_max: rlimit_max (1024) below minimum Windows limit (16384) Registered MSG_REQ_POOL_USAGE Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED rlimit_max: rlimit_max (1024) below minimum Windows limit (16384) Processing section "[homes]" Processing section

I had been running a samba server, the AMAHI F12 distro, that has samba 3.4.9. It ran well enough, but I was planning on replacing it with ClearOS. Well monday night I lost my server harddrive, so now it is crunch time to update/upgrade. I think I have ClearOS configured properly, it is running samba 3.6.10 (Redhat 6.4 based). So far I have tried to add two of my XP systems to the new

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Good Moring list I already possess PDC + LDAP. Today the necessity appeared to possess a BDC, but users in base LDAP would like to legalize all, and mine configuracao follows below: [global] ~ workgroup = AURORA ~ netbios name = fly ~ server string = Marcio(CPD) ~ passdb backend = ldapsam:ldap://121.1.16.245 ~

Hi Folks, I'm trying to run samba on Solaris 9. It works OK when I don't compile in kerberos and ldap, but when with those two compiled in, smbd seems to freeze (nmbd and winbindd are OK). After a bit of investigation I notice something strange in truss: ... /1@1: -> libldap-2.3:ldap_free_urldesc(0x30dfe8, 0x32e048, 0x32dfb8, 0x3 /1@1: ->

Hello, I've just installed samba with ldap on a debian etch. I have a problem when i attempt to create a user with the command smbldap-useradd -a -P -c "toto DUPONT" -u 1001 toto and to log in with it after. I obtain this error : [2008/10/29 17:35:26, 0] passdb/pdb_get_set.c:pdb_get_group_sid(164) pdb_get_group_sid: Failed to find Unix account for toto [2008/10/29 17:35:26, 1]

Hello, Using vampire to migrate accounts from an NT box and found that machine names were not created. Creating account: IT-NT$ Could not create posix account info for 'IT-NT$' Creating account: PDC$ Could not create posix account info for 'PDC$' <snip> And seemingly random user accounts were also not created. Can I make another pass with vampire to retrieve the missed

Hello all, I've added my windows7 client to the domain (samba running as pdc), having applied the registry changes identified here (http://wiki.samba.org/index.php/Windows7). Partial success - domain users can login and see shares etc, BUT: 1 - the registry settings in ntlogon/NTConfig.POL are not applied. Am I right in thinking that windows 7 ignores this policy? And if so I therefore

Hello list, I have a samba 3.5.6 running on a Debian squeeze machine. This box is running since more than a year without any problems. Since a couple of days we have the following problem. One Win7 user doesn't get his user profile any more The log file tells: [2013/03/04 07:43:14.641151, 1] auth/auth_util.c:580(make_server_info_sam) User WIN7MACHINE$ in passdb, but getpwnam() fails!

Hi, I migrated a PDC to use an ldap backend and am having fun with a few last issues.. Existing user accounts and machine accounts were migrated, and existing users can authenticate. Now I've added some new users and none of them can authenticate. e.g. for the user "inktec". The user can login via SSH, but not mount a share: smbclient \\\\server3\\someshare -U=inktec mypassword

Hi, I could use some confirmation on my approach to configuring my BDC. I want the user to be able to access shares on the BDC and have their domain credentials stamped on any files they create. I do not want to add domain users to the /etc/passwd file. At the moment users can authenticate onto the domain but once they try and access a share on the BDC, these XP users get a dialogue box asking