similar to: string_to_sid: SI is not in a valid format

Rowland, Sorry for the personal reply: my email default is set to reply to the sender only. Removing all the lines from smb.conf you suggested didn't resolve the issue, still getting the same messages in the log. I'll have to put back: winbind enum users = yes winbind enum groups = yes because without these lines commands: getent passwd getent group return only local passwd and group

First, can you please keep this onlist. On Thu, 28 Dec 2017 20:36:19 -0500 Matt Savin <matt at tegers.com> wrote: > Rowland, > > Thank you for your reply. Below is a global part of the smb.conf file: > > [global] > workgroup = DOMAINNAME > security = ads > realm = DOMAINNAME.LOCAL > kerberos method = secrets and keytab > kerberos encryption types =

On Thu Dec 14 19:27:29 2023 Matt Savin <matt at tegers.com> wrote: > > Hello Mark, > > When joining the domain, did you specify domain name as hprs.locl, or hprs > only? Please try to specify hprs.locl. > > BR, > Matt Matt - yes I did specify hprs.locl. I just tried it again and it failed again. This time I opened the "Detail" box which says:

We have a Samba-4.3 AD-DC hosted on a FreeBSD-10.3 system. We have just discovered that for some reason our domain workstations are not synchronising their time with the AD-DC. We have not altered the default GPO nor have we created a special GPO to handle time services. I have been working on several of the domain clients and I cannot seem to get them to source from the Samba server. I have

I think I see some heavy weather ahead of me: http://technet.microsoft.com/en-ca/library/dn303411.aspx specifically w.r.t. Server 2012 r2 (with which I will have to soon(ish) wrestle): > Features Removed or Deprecated in Windows Server 2012 R2 >... > RSAT: Identity management for Unix/NIS > > The Server for Network Information Service (NIS) Tools option of > Remote Server

Hello, after an update from Samba 2.2.12 to 3.0.22 and running the daemons 2-3 days my Samba Server freeze the whole Server. First the clients get connection problems, timing out to access the shares and then some minutes later the whole Server freeze, i can't even logon on the console. Only a cold reset is possible. I convert all files from latin-1 to a UTF-8 and then from UTF-8 to ISO-8859-1

I'm continuously getting this message - it fills all of my logs... How can I fix this, or stop winbind from logging to syslog? Thanks! Nolan Jul 1 21:10:09 mgprisvr winbindd[2395]: [2006/07/01 21:10:09, 0] lib/util_sid.c:string_to_sid(285) Jul 1 21:10:09 mgprisvr winbindd[2395]: string_to_sid: Sid S-0-0 is not in a valid format. Jul 1 21:10:10 mgprisvr winbindd[2395]: [2006/07/01

Hello! I posted before, figured I'd try again and provide more information in the original post. I'm running samba-3.0.22-1.fc5, joined to a W2K3 domain. All features appear to work - I've been running it this way for a month. This message appears not to actually affect anything, and it occurs every 30 seconds or so. I'll be happy to post my configs, if necessary. This set

I'm running Winbind 3.0.33 with FreeRadius for windows authentication. Has anyone found a solution to these error messages in the samba.log? [root@pr01 log]# tail samba.log [2009/03/12 09:28:33, 0] lib/util_sid.c:string_to_sid(242) string_to_sid: Sid S-0-0 is not in a valid format. [2009/03/12 09:33:33, 0] lib/util_sid.c:string_to_sid(242) string_to_sid: Sid S-0-0 is not in a valid

I'm not quite sure why this is happening, I used to be able to connect perfectly fine to my share. Then I updated and rebooted and now I'm greeted with this message, and a login prompt where my credentials are never accepted. [http] comment = HTTPD Server path = /srv/http writable = no public = no browsable = no valid users = frostyfrog write list = frostyfrog force user =

Hi all, I've installed samba (Sernet 3.6.22 on CentOS 6) on a NATed system and now I'm not able to connect or write to my shares. The message in the log says: [2014/03/06 09:45:38.849457, 3, pid=48264, effective(0, 0), real(0, 0)] ../libcli/security/dom_sid.c:208(dom_sid_parse_endp) string_to_sid: SID @smc_cc is not in a valid format [2014/03/06 09:45:38.850510, 3, pid=48264,

Hi, I do get a lot of „string_to_sid: SID .... is not in a valid format“ in our samba 4.6.x Logs. What might be wrong or what might I check. Users can login to the domain and we don’t see any problem on the user / client side … Thanks for suggestion and hints . Regards . Götz

I have FreeBSD 5.3 running on an Sun Ultra 10. I installed Samba 3.03, from patching SWAT now says version 3.07. I am having an issue printing from Windows through Samba to Savin copiers (model 9935DPE and 9945DPE) when downloading the Windows drivers directly from the [print$] share. When I print a test page, the orientation of the lettering is correct but the letters are gibberish. The

I have a CentOS 5 box that is joined to a genuine Windows domain controller and users can easily log into that box with their AD credentials. I configured the Linux box' native config files (smb.conf, krb conf files, etc) instead of using a third-party app. Logins work fine. I visit the smb.conf file to try and create an smb share of a mounted volume, and I get prompted for credentials.

Hi, I came across the problem with rsync-2.5.5 on Cygwin/Win2K while rsyncing with filenames which have 'strange' (non latin-1) characters in filenames. The problem is that filenames on Windows system are coded (in our case) in codepage 852, while server (Linux system) has filename coding according to ISO-8859-2. This two are not fully compatible, causing rsync to simply skip copying some

I've been struggling for almost 2 weeks to get Samba working on two new servers. When I try to open a Samba share from a Windows 2003 computer, I always get a logon challenge. I always get the following lot message [2008/11/13 16:05:06, 3] lib/util_sid.c:string_to_sid(228) string_to_sid: Sid MYDOMAIN\mygroup does not start with 'S-'. [2008/11/13 16:05:06, 2]

Hi, I don't want to have to downgrade my samba server to disable spoolss. I'm running 2.2.3. (I assume I don't need 2.2.3a since it just fixed an overwrite bug). When I use "disable spoolss = no", I can access my printer \\server\savin just fine. When I use "disable spoolss = yes", I can see my printer (savin) in \\server, but when I access it, I get:

31.01.2023 08:55, Matt Savin via samba ?????: > In group policies use DNS aliases, then you'll need to change only DNS > entries for these aliases to point to a new host(s). I'd say don't use simple dns aliases (cnames) in a DC, but use SPNs instead (see samba-tool spn). This will manage CNAMEs too, and also manages the KRB tickets and proper autentication of the server to the

On 21/05/2020 21:04, Matt Savin wrote: > I think you can continue to use '128' (good for load balancing, > otherwise 255 is fine). I had the same issue, following dhcpd.conf > entries fixed it (the last entry is important): > > one-lease-per-client? true; > deny ? ? ? ? ? ? ? ? ? ? ? ?? duplicates; > ignore-client-uids ? ?? true; > > And it's not a bug,

Hi, I have a problem. I upgraded from samba 2.0.7 to 2.2.3 recently, and one of my 2 printers have driver issues. Whenever I print to SAVIN 2545, I get binary and hieroglyphics, so I assumed that it's driver-related. I can print to our HP8100 just fine. Some machines were still configured with: "\\server\savin", LAN Manager Printer These machines STILL print fine. However, if