[Samba] No Mapping between account names and security IDs was done
I had inquired about this in that past and was not given a direct answer. For whatever it is worth, here are my findings, also in response to this thread http://lists.samba.org/archive/samba-ntdom/2001-January/017142.html I just discovered that you should make sure that samba has not generated a new sambaDomainName= entry in LDAP that contains a SID that's different than the one used in your machine and user accounts. Cheers Kristis -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] samba-3.0.0 release won't authenticate
Hello, This is the 3rd time I'm sending the message. I've just upgraded from samba3-alpha23 to samba3.0.0 release. I'm running samba with an LDAP backend and I used the convertSambaAccount conversion script, and now the latest 3.0.0 ldap schema. The problem I have is that no Windows user can authenticate against their home directory, or any other machine. Authentication against the login screen works, but not to any shares. I don't understand how this happens all of the sudden, given that alpha23 had no problems with authentication. Is there anything else I need to know about rids, SIDS, UID/GID mappings? Also, when I try to join a Win2k machine to the domain I get the error: "No mapping between account names and security IDs was done". Do I need to use an "idmap backend" entry in smb.conf ? I tried that and still have the same problem. Authentication just doesn't work. Why ? The smb.conf did not change. Anybody that had similar problems ? Anybody that has a clue why this might be happening? -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Upgrading to samba3.0.0 from samba3-alpha23 --> can no longer authenticate
Hello, I've just upgraded from samba3-alpha23 to samba3.0.0 release. I'm running samba with an LDAP backend and I used the convertSambaAccount conversion script, and now the latest 3.0.0 ldap schema. The problem I have is that no Windows user can authenticate against their home directory, or any other machine. I don't understand how this happens all of the sudden, given that alpha23 had no problems with authentication. Is there anything else I need to know about rids, SIDS, UID/GID mappings? When I try to join a Win2k machine to the domain I get the error: "No mapping between account names and security IDs was done". Do I need to use an "idmap backend" entry in smb.conf ? I tried that and still have the same problem. Authentication just doesn't work. Why ? The smb.conf did not change. Anybody that had similar problems ? -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] write_socket: Error writing 4 bytes to socket 5: ERRNO=Connection reset by peer
Hi Paul, This is another report I came across that indicates this may be a naming service problem, as you mentioned in your bug description: http://www.geocrawler.com/archives/3/151/2002/11/150/10253550/ Perhaps we can compare configs. I'm running bind for DNS and have "wins support = yes" on the samba3 pdc to run a WINS server. I was not pushing down through dhcp a WINS server IP or node type (nor was one hard coded in each client), but I just set that and I'll let you know if that makes a difference. Are you setting a WINS server on each client machine or through dhcp ? On Thu, 2003-07-17 at 14:42, Paul Eggleton wrote: > Hi Kristis, > > Kristis Makris wrote on Friday, 18 July 2003 9:19 a.m.: > > [2003/07/17 12:16:06, 0] lib/util_sock.c:get_socket_addr(900) > > getpeername failed. Error was Transport endpoint is not connected > > [2003/07/17 12:16:06, 0] lib/util_sock.c:write_socket_data(388) > > write_socket_data: write failure. Error = Connection reset by peer > > [2003/07/17 12:16:06, 0] lib/util_sock.c:write_socket(412) > > write_socket: Error writing 4 bytes to socket 16: ERRNO = Connection > > reset by peer [2003/07/17 12:16:06, 0] lib/util_sock.c:send_smb(573) > > Error writing 4 bytes to client. -1. (Connection reset by peer) > https://bugzilla.samba.org/show_bug.cgi?id=232 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] write_socket: Error writing 4 bytes to socket 5: ERRNO =Connection reset by peer
Hello, I originally posted this on samba-technical (http://lists.samba.org/pipermail/samba-technical/2003-July/046076.html), but I just verified that I'm also seeing the same error message with samba-3.0.0beta3. I have not tested if I'm also getting disconnects and Word saving problems that way. But, people using 2.2.7 must have also seen this. Here are some messages I've seen in the logs using samba-3.0.0beta3. [2003/07/17 12:16:06, 0] lib/util_sock.c:get_socket_addr(900) getpeername failed. Error was Transport endpoint is not connected [2003/07/17 12:16:06, 0] lib/util_sock.c:write_socket_data(388) write_socket_data: write failure. Error = Connection reset by peer [2003/07/17 12:16:06, 0] lib/util_sock.c:write_socket(412) write_socket: Error writing 4 bytes to socket 16: ERRNO = Connection reset by peer [2003/07/17 12:16:06, 0] lib/util_sock.c:send_smb(573) Error writing 4 bytes to client. -1. (Connection reset by peer) Anybody else experiencing something similar to this (see original posting) ? Thanks, Kristis -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] smbgroupedit does not honor ldap parameters from smb.conf
Hello, I've been using samba-3alpha22 as a PDC authenticating against LDAP. I am trying to add NT Groups using the smbgroupedit utility. It seems to me that smbgroupedit always looks in /etc/group and does not take into account the ldap configuration options specified in smb.conf. The relevant ldap entries are: passdb backend = ldapsam:ldap://ebola/ ldap suffix="dc=datasoft, dc=com" ldap admin dn = "cn=root, dc=datasoft, dc=com" ldap ssl = off ldap passwd sync = yes ldap trust ids = yes Regardless of whether I have an entry in LDAP that belongs in the posixGroup and/or posixAccount ObjectClasses, it looks like smbgroupedit only consults /etc/group # ./smbgroupedit -a nyNewGroup -t d unix group nyNewGroup doesn't exist! I would also expect that smbgroupedit would try to add new groups in LDAP, if entries for them where not already there. Does anybody know what the status of this utility is ? I have noticed the "add group script", "add user to group script", and "add user script" configuration parameters, and in the examples of those the /usr/local/samba/bin/add_user script is listed, while no such utility is shipped with the samba3-alpha22 source. What is the samba designated utility (if there is one) for adding groups to the *authentication database* that is independent of what that database is (pwdb/LDAP) ? Thanks, Kristis -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
