search for: ohprsstorag

...redentials of other domain users (actual users). I probably shouldn't have used that account in the first place, but I did. Is there a way around this or do I have create a new domain account for this purpose? Problem #2: In one of the SQL Server scripts, I have: SET @NetworkPath = '\\OHPRSstorage\Backups\SQLServerBackup\' which used to work before I changed OHPRSstorage (the Samba file server) to be a domain member and do AD authentication. This script is run as SQL Server user 'sa', which likely has no authorization to access the NetworkPath. I'm not even sure what userID...

...ADUC, I tried to remove a domain member using: > samba-tool group removemembers "Domain Computers" MARKA\$ Removed members from group Domain Computers As shown, it say it "Removed members", but ... > samba-tool group listmembers "Domain Computers" : LABRAT$ : OHPRSSTORAGE$ MARKA$ : COMMON$ : listmembers still shows the computer as a member of "Domain Computers". What's up with this? Samba Version 4.8.2 THX --Mark

I am running Samba 4.4.16 on an AD/DC server. I have several Linux domain members. Occasionally (not every day) I get a message in the samba log like this one: [2018/03/05 17:57:31.690032, 2] authentication for user [HPRS/OHPRSSTORAGE$] FAILED with error NT_STATUS_WRONG_PASSWORD I understand when I get such a message when a user enters the wrong password, but OHPRSSTORAGE is a domain member computer hostname. I get this sort of message occasionally for all the Linux domain members, but never for the Windows domain members....

...users to also map/mount this share, possibly via the "Classic" 'security = user' mechanism. Can this be done? That is, can both mechanisms be accomodated somehow? THX --Mark Below is the current smb.conf with 'security = ADS' and various idmaps. [global] netbios name = OHPRSSTORAGE # workgroup = NT-Domain-Name or Workgroup-Name, eg: LINUX2 # workgroup = WORKGROUP # server string is the equivalent of the NT Description field server string = HPRS NAS server domain master = no prefered master = no realm = HPRS.LOCAL workgroup = HPRS usershare allow guests = Yes usersha...

...S (comes back blank), but I can do so on the AD/DC: getent passwd Administrator HPRS\administrator:*:0:10000:Administrator:/home/HPRS/administrator:/bin/bash Is there some setting in the NAS smb.conf that will fix this? Here is my smb.conf on the NAS: # Global parameters [global] netbios name = OHPRSSTORAGE server string = HPRS NAS server domain master = no prefered master = no realm = HPRS.LOCAL workgroup = HPRS usershare allow guests = Yes usershare max shares = 10 security = ADS template shell = /bin/bash max log size = 10000 load printers = no printing = bsd printcap name = /dev/null disa...

...ere ohprso's UID = 1001 I've seen the smb.conf setting: !<server user> = <client user> but I'm not sure that's appropriate in this case. Is there such a mechanism for AD authenticated clients? Thanks --Mark my AD Authenticating smb.conf: [global] netbios name = OHPRSSTORAGE server string = HPRS NAS server domain master = no prefered master = no realm = HPRS.LOCAL workgroup = HPRS usershare allow guests = Yes # Do I need this? usershare max shares = 10 security = ADS template shell = /bin/bash max log size = 10000 load printers = no printing = bsd prin...

...gt; HPRS\administrator:*:0:10000:Administrator:/home/HPRS/administrator:/bin/bash > > > > Is there some setting in the NAS smb.conf that will fix this? > > > > Here is my smb.conf on the NAS: > > > > # Global parameters > > [global] > > netbios name = OHPRSSTORAGE > > > > server string = HPRS NAS server > > > > domain master = no > > prefered master = no > > > > realm = HPRS.LOCAL > > workgroup = HPRS > > usershare allow guests = Yes > > usershare max shares = 10 > > security = ADS > &...

...r is a Linux server webserver.hprs.local has address 192.168.0.3 >From the Linux webserver: $ host mail # mail is the Linux Samba4 domain controller mail.hprs.local has address 192.168.0.2 $ host dennis # dennis is a Windows 7 workstation DENNIS.hprs.local has address 192.168.0.57 $ host OHPRSstorage $ this is the Linux NAS RAID OHPRSstorage.hprs.local has address 192.168.0.5 Is there something in my posted configs that leads to to believe there is a problem with Linux hosts in this setup? "and what about the reverse zone ?" I do have the reverse zones configured. See the 'sn...

...dentials and not require the user to enter ID/PW on the Map Network Drive dialog. Is this possible? If so, I know how to make the Linux file-sharing host a domain member. What would I have to do to get Samba to authenticate the user's domain credentials? My smb.conf: [global] netbios name = OHPRSSTORAGE workgroup = WORKGROUP server string = HPRS NAS server domain master = no prefered master = no security = user map to guest = Bad User hosts allow = 192.168.0. 127. load printers = no printcap name = /dev/null printing = bsd disable spoolss = yes guest account = nevermind lo...

...t; >> samba-tool group removemembers "Domain Computers" MARKA\$ > Removed members from group Domain Computers > > As shown, it say it "Removed members", but ... > >> samba-tool group listmembers "Domain Computers" > : > LABRAT$ > : > OHPRSSTORAGE$ > MARKA$ > : > COMMON$ > : > > listmembers still shows the computer as a member of "Domain Computers". What's up with this? "Domain Computers" is the primaryGroupID of AD joined computer (515). The computer object is a member not because it is listed in...

...uot;Domain Computers" MARKA\$ > > Removed members from group Domain Computers > > > > As shown, it say it "Removed members", but ... > > > >> samba-tool group listmembers "Domain Computers" > > : > > LABRAT$ > > : > > OHPRSSTORAGE$ > > MARKA$ > > : > > COMMON$ > > : > > > > listmembers still shows the computer as a member of "Domain > Computers". What's up with this? > > "Domain Computers" is the primaryGroupID of AD joined computer (515). > The comp...

...> > getent passwd Administrator > HPRS\administrator:*:0:10000:Administrator:/home/HPRS/administrator:/bin/bash > > Is there some setting in the NAS smb.conf that will fix this? > > Here is my smb.conf on the NAS: > > # Global parameters > [global] > netbios name = OHPRSSTORAGE > > server string = HPRS NAS server > > domain master = no > prefered master = no > > realm = HPRS.LOCAL > workgroup = HPRS > usershare allow guests = Yes > usershare max shares = 10 > security = ADS > template shell = /bin/bash > > max log size = 1000...

...ia > the "Classic" > 'security = user' mechanism. Can this be done? That is, can both > mechanisms be accomodated somehow? > > THX --Mark > > Below is the current smb.conf with 'security = ADS' and various idmaps. > > [global] > netbios name = OHPRSSTORAGE > > # workgroup = NT-Domain-Name or Workgroup-Name, eg: LINUX2 > # workgroup = WORKGROUP > > # server string is the equivalent of the NT Description field > server string = HPRS NAS server > > domain master = no > prefered master = no > > realm = HPRS.LOCAL &g...

...> Removed members from group Domain Computers > > > > > > As shown, it say it "Removed members", but ... > > > > > >> samba-tool group listmembers "Domain Computers" > > > : > > > LABRAT$ > > > : > > > OHPRSSTORAGE$ > > > MARKA$ > > > : > > > COMMON$ > > > : > > > > > > listmembers still shows the computer as a member of "Domain > > Computers". What's up with this? > > > > "Domain Computers" is the primaryGroupI...

...ere ohprso's UID = 1001 I've seen the smb.conf setting: !<server user> = <client user> but I'm not sure that's appropriate in this case. Is there such a mechanism for AD authenticated clients? Thanks --Mark my AD Authenticating smb.conf: [global] netbios name = OHPRSSTORAGE server string = HPRS NAS server domain master = no prefered master = no realm = HPRS.LOCAL workgroup = HPRS usershare allow guests = Yes # Do I need this? usershare max shares = 10 security = ADS template shell = /bin/bash max log size = 10000 load printers = no printing = bsd prin...

>From your Global config I see no IDMAP settings. You need that for Linux to recognize your ad users. See my blog top post for example: Monklinux.blogspot.com Try my configuration, should work perfectly. Soz 4 short reply, typing on phone. Lemme know if it works. Note, pay attention to section under installing samba. On Sep 19, 2017 22:19, "Jamie McParland via samba" <samba at

...:0:10000:Administrator:/home/HPRS/administrator:/bin/bash >>> >>> Is there some setting in the NAS smb.conf that will fix this? >>> >>> Here is my smb.conf on the NAS: >>> >>> # Global parameters >>> [global] >>> netbios name = OHPRSSTORAGE >>> >>> server string = HPRS NAS server >>> >>> domain master = no >>> prefered master = no >>> >>> realm = HPRS.LOCAL >>> workgroup = HPRS >>> usershare allow guests = Yes >>> usershare max shares = 10...

...uot;Domain Computers" MARKA\$ > > Removed members from group Domain Computers > > > > As shown, it say it "Removed members", but ... > > > >> samba-tool group listmembers "Domain Computers" > > : > > LABRAT$ > > : > > OHPRSSTORAGE$ > > MARKA$ > > : > > COMMON$ > > : > > > > listmembers still shows the computer as a member of "Domain Computers". What's up with this? > > "Domain Computers" is the primaryGroupID of AD joined computer (515). > The computer ob...

On Thu, 14 Jun 2018 16:03:35 -0400 Mark Foley via samba <samba at lists.samba.org> wrote: > Nevertheless, 'ls' does give names though I don't seem to have either > libnss-winbind or libpam-winbind files on my AD/DC. I keep forgetting that you use slackware, I suppose it uses something different, but do you have any file like: libnss_winbind.so.2 > > Circling back

I've been using bind9 and DHCP on Samba 4.1.0 thru 4.1.17 and Slackware 64 14.1 for many months now in a production environment and it works just fine. There are a few tweaks here and there to get bind/dhcp to play nicely with Samba ... Note, conf file locations are Slackware, but you'll know where the same thing goes in your distro. In the examples below, my Domain IP range is