similar to: Win7 cannot net use z: Samba share

I have just replaced an old FC9 server with a new FC14 server as the old one died. Before it died I was having trouble authenticating connections to it. Now I have the new server running I'm still suffering the same problem. Setting up a user and setting the password gives no errors, but then connections fail complaining about the password. It is very much a virgin vanilla setup. All I

Hi Samba List I have the problem to modify an entry for a user in samba with tdb backend. My OS is OpenSuSE 13.1, Samba 4.1.21. Samba NT'Style, no AD, no LDAP, passdb backend = tdbsam I managed to delete a User in my NIS/passwd File before I deleted it in my Samba tdb. No the problem is, I can't modify the user because he does not exists, but can not add, because he exists. The problem

On 31.05.19 22:07, Andrew Bartlett wrote: > On Fri, 2019-05-31 at 11:40 -0700, Jeremy Allison via samba wrote: >> On Fri, May 31, 2019 at 07:09:44PM +0200, Andreas Reichel wrote: >>>>> When adding me as the user with 'smbpasswd -a andreas', and entering a password, >>>>> no LANMAN hash is generated. The generated smbpasswd entry always contains 32 X

Hi folks I face a problem when creating a samba user, Here is the detail: (1) Phenomenon I have created a linux user q01, Q01, and samba user q01,and then, when I created the samba user Q01,I ran into a problem: I use “smbpasswd –a Q01” to create samba user Q01, command line returned successfully, but in fact the samba user has not been created. I can not query the user with the

On Fri, 2019-05-31 at 11:40 -0700, Jeremy Allison via samba wrote: > On Fri, May 31, 2019 at 07:09:44PM +0200, Andreas Reichel wrote: > > > > When adding me as the user with 'smbpasswd -a andreas', and entering a password, > > > > no LANMAN hash is generated. The generated smbpasswd entry always contains 32 X as the first hash. > > > > > > >

On 12/01/16 13:21, Anton Renner wrote: > Hi Samba List > > I have the problem to modify an entry for a user in samba with tdb backend. > > My OS is OpenSuSE 13.1, Samba 4.1.21. Samba NT'Style, no AD, no LDAP, > passdb backend = tdbsam > > I managed to delete a User in my NIS/passwd File before I > deleted it in my Samba tdb. No the problem is, I can't modify the

hi! is it possible to use a samba server for a backup-to-disk space on a veritas backup system??? my system: debian sarge samba 3.0.14a-3 windows 2003 server with veritas 10.0 sp3 i try to configur veritas to use my share on the debian maschin but i always get the following error message: es konnte kein neuer sicherungsordner erstellt werden. zugriff verweigert translation: backup

Hi Team, I have build samba 4.5.0.on hpux. On running make quick test is failing with below error. I am attaching the logs with log level 10. *Workaround:- *I have implemented workaround by adding all the test users(force_user, smbget_user,user1,user2.......) from useradd command. Is it an expected behavior on hpux ? Note:- I am not sure if this issue to be send to samba-technical mail list.

I have spent days now trying to debug why I can not add machines to the domain. I am using samba 3.0.23c with an openldap backend. I can authenticate fine using smbclient with the administrator account but when I go to add a machine it fails. I have checked the debug logs and know what is happening, I am just not sure why or how to fix it. I am using the idealx scripts to add machines.

Hi all I have samba 3.0.21b with openldap 2.3.19 on Redhat Enterprise Linux 4 ES with Kernel Version 2.6.9-5. i have allready posted this error in bugzilla, bug 3545 i have created 70 groups, (test1-test70), and created a user "nir" and made "nir" member to these 70 groups. >From Windows system it was the same error ""Remote procedure call was

Hello Sorry to ask here, but all googeling doesn't helped. We have several samba domains (samba 3.5.6) with ldap backed and windows 7 clients, which worked fine so far. Know we begin to see that random machines begin to kick out of the domain with the error: _netr_ServerAuthenticate3: netlogon_creds_server_check failed. Rejecting auth request from client MBBUCHHALTUNG04 machine account

freebsd 5.3, samba 3.10 I get this far with LDAP/Samba integrationg. Stuck on creating users/machines with smbpasswd -a (-m) username command. schema files weren't modified, everything else is pretty much at defaults. First the relevant config parts: passdb backend = ldapsam_compat:ldap://localhost/ ldap suffix = dc=company,dc=com ldap machine suffix = ou=Computers ldap user suffix =

I have upgrade the pdc server from debian sarge to etch. After this operation we can't login to the domain (client windows 2000 & XP) smbclient works fine and from a windows local account I can browser the samba directories too (puttin username and password before..) I use tdbsam of course and pdbedit -L let me see all the accounts, it seems to work fine I tried to remove a pc from

I upgrade a samba 3.2.14 to samba 3.6.0 radius server for 802.1x. I discover that ntlm_auth fails for machines accounts with error: No logon workstation trust account Put winbind in debug with winbindd -F -i -d 10 give: accepted socket 24 process_request: request fn INTERFACE_VERSION [20000]: request interface version winbind_client_response_written[20000:INTERFACE_VERSION]: delivered response

I've only got LDAP configured as a passdb type in my smb.conf, but samba appears to be completely ignoring that and creating an /etc/samba/smbpass file (full output of that at the bottom) my smb.conf has: ldap admin dn = "cn=Admin,dc=byramhealthcare,dc=com" ldap ssl = off passdb backend ldapsam:ldap://ldapmaster.byramhealthcare.com ldap delete dn = no ldap user suffix =

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

Hi people: I have a Debian etch stable with the latests updates. When I try to join a computer to the domain I create the machine on the ldap and its created with the following atributes: dn:cn=test$,ou=Machines,dc=domain,dc=org objectClass: top objectClass: inetOrgPerson objectClass: posixAccount uidNumber: 3123 uid: test$ cn: test$ sn: test$ gidNumber: 604 homeDirectory: /dev/null loginShell:

i'm trying to get samba 3.0 alpha 19 runing on OS X 10.2 working as a PDC with Win XP clients using an LDAP passdb backend i've managed to get it so i can connect to shares with smbclient but whenever i try to join one of the XP machine to the domain Windows tells give me the message "the specified network name no longer exists". when i check the logfile the last thing in it is

Im having a strange problem... I have a few users created (few = 100) with gid = to uid. Like this: dlanger:x:1229:1229::/home/dlanger:/bin/false jbranca:x:1230:1230::/home/jbranca:/bin/false cdobenau:x:1231:1231::/home/cdobenau:/bin/false sbarabani:x:1232:1232::/home/sbarabani:/bin/false And i have a the new ones like this: nharrington:x:1233:100::/home/nharrington:/bin/false

I can't really guess the point of your intelligent answer from this. If I have to assume you're surprised, I guess I am too. The cn exists in ldap, with all the attributes that I imported from other databases, the message given by smbpasswd suggests that it either tried to create an entry or update it with sambaaccount attributes ( which it didn't ), neither of which are the expected