similar to: FW: WinXP joining a samba PDC

On 19/10/2019 20:18, Alex Moen via samba wrote: > Running CentOS Linux release 7.7.1908. Have Samba running as our > fileserver on our (mostly) Windows network.?? Ran my "normal" yum > updates today, and Samba was upgraded (last updates were on > 8/10/2019).? I was on 4.8.3 before; now it's 4.9.1: > > ??? Updated samba-4.8.3-6.el7_6.x86_64 @updates > ???

On 10/19/19 2:57 PM, Rowland penny via samba wrote: > On 19/10/2019 20:18, Alex Moen via samba wrote: >> Running CentOS Linux release 7.7.1908. Have Samba running as our fileserver on our (mostly) Windows network.?? Ran my "normal" yum updates today, and Samba was upgraded (last updates were on 8/10/2019).? I was on 4.8.3 before; now it's 4.9.1: >> >> ??? Updated

Running CentOS Linux release 7.7.1908. Have Samba running as our fileserver on our (mostly) Windows network. Ran my "normal" yum updates today, and Samba was upgraded (last updates were on 8/10/2019). I was on 4.8.3 before; now it's 4.9.1: Updated samba-4.8.3-6.el7_6.x86_64 @updates Updated samba-client-4.8.3-6.el7_6.x86_64

I am running it to a problem adding a WinXP Computer to my samba PDC. It is coming up with an error about the trust accounts. I have tried the registry patch with no success. Any suggestions? Kevin

Skipped content of type multipart/alternative-------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 5105 bytes Desc: not available Url : http://lists.samba.org/archive/samba/attachments/20020509/3678dd89/attachment.gif

Hi! I am seeing other users with the same problem as I have. My samba also fails to add machine accounts. It seems to me if it didn't even try. If I use some other script (pdbedit, smbldap-tools) than smbpasswd it manages to add the account but still fails to authenticate within the same session. If I try again the machine account exists and authentication goes ok. server:~# smbpasswd -a -m

I hope this doc below helps out. But from what I have seen it looks like you created the machines accounts but did not create the smbpasswd for the machine accounts. See docs below Machine accounts: the manual approach As noted, Samba will not allow you to add an entry to the smbpasswd file (user or machine) unless there is a existing UNIX account for that user. So the first step is to create an

/etc/fstab: //machine_name/SAN /mnt/SAN cifs defaults 0 0 [root at machine_name SAN]# mount -a Password: mount error 13 = Permission denied Problem is there is no password to the smb server. Why am I getting a password prompt when the share has full RW access and all access is granted on the share? Note, though the share is fully visable and accessable and writeable by just browsing the

Version 0.1-0 of a new package `ffmanova' is now available on CRAN. Comments, suggestions, etc. are welcome. Please use the email address ffmanova (at) mevik.net. The package implements 50-50 MANOVA (Langsrud, 2002) with p-value adjustment based on rotation testing (Langsrud, 2005). The 50-50 MANOVA method is a modified variant of classical MANOVA made to handle several highly correlated

Version 0.1-0 of a new package `ffmanova' is now available on CRAN. Comments, suggestions, etc. are welcome. Please use the email address ffmanova (at) mevik.net. The package implements 50-50 MANOVA (Langsrud, 2002) with p-value adjustment based on rotation testing (Langsrud, 2005). The 50-50 MANOVA method is a modified variant of classical MANOVA made to handle several highly correlated

OK? So, I have posted on the Centos list, comp.security.ssh, and Linux Forums, and no one seems to have heard of this issue or even have any advice for me. So, I am going to take a shot with the Samba list, since this is related. I have a Centos 6.2 server freshly updated. It is authenticating against an openldap server, and I am having an issue with the hashing algorithms being used by various

There is OBVIOUSLY something wrong somewhere. EITHER a WHOLE bunch of us are stupider than we thought, the documentation left off a step, or there is something SO blatently obvious that we are ALL staring it in the face and missing it inches in front of our faces. This is exactly what I've had, (BUT I *D*I*D* have it running ok ...) and I STILL havent figured it out yet,... Subject:

Kristyan (and all) I just searched the samba website, and I couldnt find any reference to spnego except for a slide show (samba-lwny.ag ) that I can't open. ANYWAY. since I can't find any reference to the spnego parameter, could someone explain what it is, what it does, and HOW it can help us "stupid" people? It doesnt seem to be a parameter I've come across before..

Hello, [ please Cc: me, I'm not subscribed here. ] we were bitten by another rsync bug of the same nature as was discussed in http://lists.samba.org/pipermail/rsync/2002-May/007399.html alexm@rack8:~$ rsync -az -e ssh rack6.domain.ru:/etc/passwd /var/tmp/forbiden-dir/ mkstemp .passwd.oPlFQm failed: Permission denied alexm@rack8:~$ echo $? 0 So our scripts wreak havoc. However, patch

Hi, I've compiled the SAMBA 3.0 alpha18 with all default options and installed well. Then I would join my NT 4.0 machine using the following steps (manual, not On the fly): # useradd -g groupid -d /dev/null -c "comment" -s /bin/false -m machine_name$ # passwd -l machine_name$ # smbpasswd -a -m machine_name$ after that I tried to join my NT4.0 to the Samba PDC, but it failed

On Tuesday 11. September 2007 02:54:19 David K. Gasaway wrote: > On 11 Sep 2007 at 2:17, Daniel Aleksandersen wrote: > (BTW, you replied to me personally .. just in case that wasn't > intentional) Oh yes, sorry about that. > > On Tuesday 11. September 2007 02:11:01 David K. Gasaway wrote: > > > This things are easily solved with vorbis comments ... Provided you >

Centos 6 Samba 3 smbldap-tools installed. LDAP directory not on local host. Example user LDIF: dn: uid=testuser at mydomain.com,ou=mydomain,o=ndtc mailHost: mailserver.mydomain.com loginShell: /bin/bash gidNumber: 500 uidNumber: 53112 uid: testuser at mydomain.com sn: user cn: test user mail: testuser at mydomain.com homeDirectory: /cust/mydomain/users/testuser gecos: test user,,662-6123

When Samba joins to AD, net creates 'Computer' object in target AD. Object 'Computer' has attributes operatingSystem and operatingSystemVersion, which automatically setup in properly value, when native Windows join to AD. I offer a patch to utils/net_ads.c to do similar way - set up operatingSystem to "Samba" and operatingSystemVersion to Samba version, when Samba

Dear Michael, I just have the same problem you have with samba 2.2.3a on a Suse 8.0 machine and win xp pro. Besides I performed all the steps below. >From my postings I learned that the prob might have something to do with a wrong mapping in smbusers file. It seems to me that the workstation account is mapped to user nobody. Up to now I was not able to solve the prob. Do you have any ideas

Not related to joining W2K clients to a domain but the "net" command refuses to work if there is a problem in smb.conf. Even if you run testparm and nothing is wrong. I don't kno if it's the order or whitespaces that causes it to not work. I"ve had to swap out smb.conf several times because I couldn't find the problem why the "net" command wouldn't run.