similar to: Samba authentication/authorization via LDAP

I'm working on upgrading a Samba server from Version 2.2.8a to Version 3.0.4. One of the things I've noticed is that the samba.schema has changed. I'll admit that I haven't done an exhaustive search yet, but in looking over the documentation I haven't seen any mention of anything that needs to be done to migrate an existing directory to the new schema. Are there any tools

I'd like a bit of a Sanity Check to make sure I understand the process. We are setting up filesharing on a Linux server via Samba (3.0.2). We would like to give the users personal space (home directories), but we don't want to add them as Linux users (no entries in /etc/passwd). The users are defined in an LDAP directory. If I understand it correctly, in order to do this we will need

Hello all. What are the implications of changing the domain name for a PDC? If I understand correctly, the SID is based on the domain name, so if the domain name (workgroup) setting in smb.conf is changed, will that mean that a new SID will be generated? If so, then I assume that all user/group SIDs will have to be updated. If the domain name is changed, can I just state that this is an

All - I am in the process of writing my own "add machine script" to use with Samba 3.0.20a and our OpenLDAP setup. For the most part it seems to work fine. If I run the script from the command line, I can see that the entry has been added to LDAP. If I then go to the Windows machine and tell it to join the domain, after giving it the Admin login and password it connects up with no

Hello all - I'm having a bit of a problem that I'm sure is being caused by my missing some trivial detail. But I haven't been able to find it, and I'm not even sure how I would construct the search to find relevant info in the archives. Here is the setup. I have Samba 3.0.20a running as a PDC against a LDAP back end. For the most part everything works fine. Users that are

We have a customer system running Slackware Linux (kernel 2.4.25) and Samba. The customer was running Samba 2.2.8 but we recently upgraded them to Samba 3.0.13. The customer has a FileMaker database on a public share. Before the upgrade, the customer was able to have multiple concurrent access to the database. After the upgrade, only the first user to access the database was successful.

Is there a trick to append an additional directory level onto the defauly behavior of a [homes] share looking in /etc/passwd to find the users Linux home dir? It would offer a bit of protection if Windows clients ended up in say the WinHome directory within their Linux home directory when logging in from Windows so they are not tempted to tamper with their desktop settings files for Linux from

So I have a freebsd machine setup, and it has 2 nick's in it. One is a REAL IP, and pulls in internet, the other is a a nat'ed nick, with samba running on it for the machines behind the firewall. Anyone know what to toss into my smb.conf to not let my outside nick xmit smbd/nmbd ? No one can connect via that interface, but people/viruses/whatever are still trying. Thanks! C.

Hello -- Our existing Unix system has more than 500 users. The system currently uses OpenLDAP to authenticate users. We just added dozens of PCs running Windows to the network. We are going to set up the existing Unix server as a samba PDC server such that the users can log onto either their Unix account or Windows account. It seems a good idea to allow the users have the same password for

On 09/10/15 20:57, Tovey, Mark wrote: > No joy. I added winbind to the passwd, shadow, and group lines and it is still not working. I also switched back to ad instead of rid (I deleted the Samba database files in /var/lib/samba and rejoined the domain when I switched), and still the same. If the account exists locally I can authenticate against AD and map the share. No local account

On Wed, Sep 18, 2019, 2:39 PM Steven Wu <stevenwu at apple.com> wrote: > > > On Sep 18, 2019, at 10:24 AM, Steven Wu <stevenwu at apple.com> wrote: > > Hi Dwight > > Thanks for the feedback. For the issue you reported, there has been few > reviews trying to tweak the -mllvm option when using legacy LTO interfaces > (myself included) but it never got enough

Hi, dat1<- read.table(text=" Restaurant owner purchase_date ??????????? 23 Chuck 3/4/2011 ??????????? 23 Chuck 3/4/2011 ??????????? 23 Chuck 3/4/2011 ??????????? 23 Chuck 3/4/2011 ??????????? 23 Bob??????? 1/1/2013 ??????????? 23 Bob??????? 1/1/2013 ??????????? 23 Bob???????? 1/1/2013 ??????????? 15 Hazel 4/11/2010 ??????????? 15 Hazel 4/11/2010 ??????????? 15 Hazel 4/11/2010 ???????????

I downloaded the source code for Samba 4.0.0, the same as is distributed with my OS. I applied the patch as described in Bug 9862, compiled and installed the code, and now it works as expected. Having the user account in AD only is sufficient, I no longer have to have the account also in the Linux server's passwd file. So indeed, it appears that I have encountered the "map to guest =

Hi Dwight Thanks for the feedback. For the issue you reported, there has been few reviews trying to tweak the -mllvm option when using legacy LTO interfaces (myself included) but it never got enough traction to moving forward. Note how -tailcallopt is implemented as a -mllvm flag means that it is a debug option and probably not well tested. The option is also not stable which means it can be

On 09/10/15 18:54, Tovey, Mark wrote: > > Got it. I changed that section as follows: > > idmap config *:backend = tdb > > idmap config *:range = 5000-29999 > > idmap config DEVELOPMENT:backend = ad > > idmap config DEVELOPMENT:schema_mode = rfc2307 > > idmap config DEVELOPMENT:range = 30000-99999 > > It did

No joy. I added winbind to the passwd, shadow, and group lines and it is still not working. I also switched back to ad instead of rid (I deleted the Samba database files in /var/lib/samba and rejoined the domain when I switched), and still the same. If the account exists locally I can authenticate against AD and map the share. No local account and it fails. -Mark

Dear All, I've seen the PRINTER_DRIVER.txt doc on getting the PRINTER$ share set up to automatically add printer drivers to Win95 clients. It explicitly says that the procedure described does not work for NT4.0 clients. I can't find any other documentation on setting up a PRINTER$ share suitable for NT4.0 or NT2000 clients either in the distribution (2.0.5a) or the web site. Is this

Hola, gracias por la respuesta. Yo también puedo descargar el fichero pero no lo carga de forma correcta: > drive_download(" https://drive.google.com/file/d/1iN7rT-W8WoXsdBpKzxcatFx7nGPWNkuz/view?usp=sharing ", + overwrite = TRUE, verbose = TRUE) File downloaded: * restaurant.RData Saved locally as: * restaurant.RData > restaurant <-

I cant join NT2000 to domain But i can't browse samba shares at all! If i try net use ... - it's work But when i try to browse a samba server iv'e always got error... -------------- next part -------------- HTML attachment scrubbed and removed

hi, I'm having troubles joining a win2k domain with samba 2.2.3a. As you can see below I always get a 'challenge/response password authentication failed' when trying to authenticate(. I searched the mailinglist but can't find a solution. After 3 days of searching i'm still stuck :( I'd appreciate any pointers you could give me. - On the W2k PDC I created a computer