Worth noting: The 3.0.x recommendation regarding nscd is that you /do
not run it at all/. Though I think that might only apply when you're
using winbindd, you might want to take a look at your nscd process to
see if it's notably busy. It was on our server, taking up half of one
of the CPUs.
Got it working. I had to restart nscd service. Nscd was not reflecting the
group entries.
Ok, it seems to be an LDAP problem. for some reason linux isnt reading the
ldap groups, even though /etc/nsswitch.conf states groups = files ldap
Here is my problem:
I ran smbldap-groupadd TEST to
Ok, it seems to be an LDAP problem. for some reason linux isnt reading the
ldap groups, even though /etc/nsswitch.conf states groups = files ldap
Here is my problem:
I ran smbldap-groupadd TEST to create the group test. I then ran:
smbldap-groupmod -m gerrym,briang TEST to add gerrym (me) and
This is not a SAMBA isssue but a workstation issue.
Chances are, Windows is trying to connect as whatever user you are logged
into the machine as. Example, if you log in to the machine as user 1,
windows sends user1 as it's authentication information with each
communication. If you have one SMB
[EMAIL PROTECTED] wrote:
I'm doing some research and I'd like to know if there is anyone who has deployed samba as a PDC with more than 50 clients with roaming profiles enabled. Looking to do something similar and I would like to know hardware configs I should choose.
Samba runs on different h/w.
I'm using FreeBSD 4.8 so software install will be quite different and
rather trivial.
My first step involved making sure the DC's were in /etc/hosts with
shortname entries.
Next I installed openldap22, then heimdal-kerberos (found some post
about this being the better/preferred version). When I
--- Scott Wrosch [EMAIL PROTECTED] wrote:
A question I'm sure has been answered before, but
I'm
still relatively new to Samba, and having just
moved,
have not been able to locate any of my Samba
reference
materials.
Anyways, I'm running a small Samba server at work
using RedHat Linux
