e of 100-199 and the other child
domain with a range of 200-299
The expectation we have is it should behave the same as samba 3.2. We
only want domain users mapped to their appropriate/specified idmaps
"buckets" as it was before in 3.2 with our config.
Thanks,
A Sam
I was able to get this to work with groupedit. But I had to change the
group ids in ldap.
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
I used smbgroupedit and it makes the mappings, but I still get:
[2002/12/02 12:28:13, 2] auth/auth.c:check_ntlm_password(261)
check_password: authentication for user [test1] -> [test1] -> [test1]
suceeded
[2002/12/02 12:28:13, 0] rpc_server/srv_util.c:get_domain_user_groups(342)
get_domain_us
When I login as a user I get this in the logs:
[2002/12/02 11:02:01, 0] rpc_server/srv_util.c:get_domain_user_groups(342)
get_domain_user_groups: primary gid of user [test1] is not a Domain
group !
get_domain_user_groups: You should fix it, NT doesn't like that
However in ldap I have that use
Thank you that did work, however I still have to make two attempts to join
the domain. It most likely a conflict between the logic of the script and
samba though. Are there any other accounts with specific rids I need to
know about? Does the guest account have to have any special rights?
Here is
I got the login to work now, but I think I may have founda bug. When the
script added the machine account it gave it an RID of 3002, but when samba
goes looking for it it searches for RID 501. I modified the RID to 501 in
ldap and the logins work. Can someone explain this behavior to me?
--
T
Well I installed a21 and I was able to add a machine account. The first
time it comes back bad password, then the second attempt it works. But
now when i restart and try to login it says it cant find the computer
account. Am I missing something(yes i have signorseal)? Here is the log
from the l
More logs, this time from smbpasswd. Although smbpasswd shouldnt be used,
it does only error on machine accounts, not user accounts.
Furthermore when using pam_ldap version, I can not get a machine on to the
domain at all. Even If I create the machine account myself, i get
"parameter is incorrec
Perhaps this logging will help?
2002/11/26 16:08:45, 10] passdb/pdb_get_set.c:pdb_set_init_flags(493)
element 17 -> now SET
[2002/11/26 16:08:45, 10] passdb/pdb_get_set.c:pdb_set_init_flags(493)
element 18 -> now SET
[2002/11/26 16:08:45, 10] passdb/pdb_get_set.c:pdb_set_init_flags(493)
elem
I just noticed that when I try to add a machine, its acctflags get set to
[DW ]. Also pwdmustchange seems to get cut in half as well. What
would cause samba to make these changes? If the add machine script runs
twice it just says user exists, it doesnt modify anything. So it has to be
samba.
Has anyone had any luck adding machine accounts from w2k to a samba 3.0
pdc? I posted the issue last week, as I noticed others were encountering
the same problem. The weird thing is I had it working on a box before.
But this time I'm using pam_ldap to avoid local unix accounts, and it
wont work.
Just use smbpasswd.
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
Im trying to add a w2k machine to a samba pdc. This is the output of my
logs:
[2002/11/22 11:01:17, 2] passdb/pdb_ldap.c:ldapsam_open_connection(267)
ldap_open_connection: connection opened
[2002/11/22 11:01:17, 2] passdb/pdb_ldap.c:ldapsam_connect_system(419)
ldap_connect_system: succesful c
I was trying things to get it to work, thats why i had security=server. I
set it back to user, didnt work. Then I tried again and it mysteriously
worked.
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
Here is my config.
[global]
workgroup = TESTDOMAIN
netbios name = TEST
null passwords = Yes
passdb backend = ldapsam:ldap://localhost
log file = /usr/local/samba/logs
add user script = /usr/sbin/useradd -d /dev/null -g 503 -s
/bin/false -M %u
I too am getting this error with samba alpha 20. I am using an ldap
backend also.
I have the add machine script also. It will take the admin password,
create the machine account, then come back with parameter is incorrect.
On Wed, Oct 09, 2002 at 10:31:16PM -0700, Hesham S. Ahmed wrote:
> Has a
16 matches
Mail list logo
