similar to: homes in Samba 3.5

>>work. Connecting from a Windows (from XP to 10) I get asked >>for username and password. But even giving those credentials >>no access is granted. The strange thing is that the user name >>is found in the system passwd and the correct home path is >>used. In the logfile (level 10) I see: >> >>smbd/service.c:996(make_connection_snum) >>

Hi all, I'm very close to having a working setup after blundering through a couple of typing errors that cost me several days of my life, with the following config: Samba 3.0.14a as a PDC Suse 9.2 Professional LDAP (eDirectory 8.7.3) passwd backend Idealx scripts Windows XP SP1 I can connect to any of the samba shares just fine using any of the users I've created, from XP and from linux

I'm relatively new to samba I have been experimenting for a week or so, though I have setup several 2000/NT domains and have been using Linux for a couple of years. I'm using Red Hat 9, updated completely via apt. Samba 3.0.9 installed from apt and i am using the stock ldap server that installed with red hat as my back end. I followed the samba.idealx.org guide to get to where I am

On 09/05/16 15:50, Fabian Cenedese wrote: > Hello > > I know that this is about outdated Samba versions, but I have > to stick with those. And after trying now for days without getting > anywhere I'm looking for help from others. > > We used an old Thecus-NAS as fileserver (no domain etc). It uses > a Samba 3.0.26 which works as we want. Now we bought newer >

Hello everyone! After running Samba on several machines for some years, I just came accross a rather strange problem. The short story is that the special user home shares are readable, but not writeable. Here's the long story: The system is a freshly set-up Debian Squeeze, right out of the box. This is the Samba config: -------------------------------- 8<

we are migrating our standalone Samba sever (3.0.14a) on a Solaris 10 box to an RHEL 6.3 box. Testing shows that on Solaris 3.0.14a works with both the OpenLDAP server we are currently using and the IPA2.2 server as LDAP backend. But 3.5.10-125.el6 on a RHEL 6.3 box does not work with either. I can still map a share with 3.5 as owner of the shared directory, but secondary group ownership does

I have a serous problem. I have for some time now tried to get an SAMBA based Domain Controller working. I have tried with OpenLDAP and tdbsam as backend, but I get the same error every time. I wood prefer to use LDAP as my backend. I have read tons of how-to SAMBA + LDAP, but non of the seams to work for my, is there someone that maybe can see what I have done rung in my config.? I have

Hello, i have migrate a Samba (3.0.20b-3.19-1616-SUSE) to debian 9 (4.5.16-Debian). On the old suse users are created with smbpasswd -an foo On Windows (10) users have a User account with also empthy passwords. No AD or NT4-Domain (round about 10 Users) Then I try to connect to the share smbclient -NL \\192.xxx.xxx.xxx work. Connect from Windows to share with no password dosed work. Set a

Hi, I just upgraded one of our samba BDC's (with LDAP back end on solaris 10) from 3.0.23c to 3.0.26a and can no longer mount shares. The error message I'm seeing in the samba logs is [2007/11/15 14:15:26, 1] auth/auth_sam.c:sam_account_ok(172) sam_account_ok: Account for user 'dbb' password must change!. [2007/11/15 14:15:26, 3]

Hello, I?m currently having a problem where a non-root user can?t change his/her own password using smbpasswd command after the password expiration and would like to know how I could solve this problem. Currently, I have a samba server running on CentOS 6.5 with its passdb backend configured to another LDAP server. The samba version I?m currently using is samba-3.6.9-169 which should be the

We've recently started using samba-3.0.23d on Mandriva 2007.0 linux systems and we've noticed a change in behaviour of smbpasswd when a non-root user tries to change their password from "NO PASSWORD". Here's an example smbpasswd entry (all one line): testuser:12345:NO PASSWORDXXXXXXXXXXXXXXXXXXXXX: NO PASSWORDXXXXXXXXXXXXXXXXXXXXX:[NU ]:LCT-00000000: The

Hi, I'm trying to migrate our PDC from samba 2.2.3 on redhat 7.3 to samba 3.0.10 on fedora core 3. We use smbpasswd which I have copied to the new server - all the unix users and groups are yp'd so they're the same on both servers. Everything seems to work fine initially. Most people can log on and get their roaming profile from most machines (they can all log in from their own

I have a Samba server set up to share files within a small network (with 2 clients) and I use OpenLDAP to store user accounts. I have pretty much got everything working (smbclient prints the correct information and I can browse and log into Samba via Nautilus) except I can't get the Vista client to connect to Samba, as it won't even prompt for a username and password it simply pops up

Help! (pretty please :) I'm still having the problem described below with samba-3.0.24. Here's an excerpt from the smbpasswd man page: When run by an ordinary user with no options, smbpasswd will prompt them for their old SMB password and then ask them for their new pass word twice, to ensure that the new password was typed correctly. No passwords will be

Hi, Meanwhile we've come many steps further, and a new issue has risen. In samba4 AD we have a user with: - homeDirectory \\server\username - homeDrive P: - scriptPath logon.bat When this user logs on, logon.bat is executed successfully, but homeDirectory is NOT mounted on P: and in the logs we see: canonicalize_connect_path failed for service username, path /\\server\username It seems

Hi, I'm using samba 3b3 (+ldapsam) and have created a user belonging to two groups : - his primary group is mapped to the "Domain Users" Windows group, - his secondary one is mapped to the "Domain Admins" Windows group. Unfortunately, only the first group seems to be known by Samba, since the user doesn't become a "Domain Admin" at all (but he is a

Hi all, Earlier I emailed the list on some issues I was having with Windows 7, and one of those issues was the trust relationship breaking down after one month. I think I have some more light to shed on this topic. First, some environmental facts I am running Ubuntu Karmic 9.10 with Samba 3.4.0-3ubuntu5.1 I have installed the latest LDAP schema into OpenLDAP 2.4.18-0ubuntu1 I have a working

Hello, I have a problem with a LDAP backed based Samba PDC. Last week, due an hardware problem, I lost my primary LDAP server and PDC. I reinstalled the LDAP server and populated it with the old data, I also reinstalled Samba. The problem is that I can't log in to samba as root (cn=root,dc=info,dc=uvt,dc=ro). All others user accounts ar working except root. Eg.:

Hi all, I'm having a problem with an upgrade of Samba running on a Redhat4 Update 4 system. The default installation provides only 3.0.10 which doesn't include the privilege model or a number of fixes including some in 3.0.21a and 3.0.23 which it looks like we'll need. The system runs in PDC mode with user accounts in an ldap database. On a test system which I'm using to

Hello list, we're trying to use NTLMv2 authentication from Liferay Portal 6.0.5 as specified in http://www.liferay.com/community/wiki/-/wiki/Main/NTLMv2+SSO+Configuration. We've created a machine account for it that looks like that: dn: uid=liferay$,ou=Maquinas,o=global,dc=map,dc=es sambaNTPassword: 76DBDF27BB32912AD61BC369DB8FEBD8 sambaPwdLastSet: 1298373376 sambaAcctFlags: [W]