similar to: receive_smb_raw_talloc failed for client - cannot get to shares

Hi, I have deployed a new file server (Samba version 4.6.2, CentOS 7) which is running as a member of an AD domain (The DCs are both Windows server 2012, forest and domain level is 2012 as well). I'm using the AD backend to store SID/UID mappings. So everything is working fine except for one specific user on one specific workstation (Windows 10) who can only access the file server with

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

Hi Trying to set up a one way trust between a 2008 Active Directory domain and a Samba 3.5.9 server which is configured as a PDC. There is already an existing trust between AD and an NT4 domain so AD has been configured to support NTLM authentication (see below for full details). With no domain trust, using smbclient either anonymously or with a valid user on the DC (e.g. Administrator)

Hello, I deleted some GPOs via ADUC. After that I also deleted the folder for each GPO. I do not know if that was correct to do! :( Now when I run the samba-tool command ntacl sysvolreset, the following error occurs. root at DC1:~# samba-tool ntacl sysvolreset *open: error=2 (No such file or directory)* ERROR(runtime): uncaught exception - (-1073741823, 'Undetermined error') File

Been using Samba since the early days and it's always worked terrifically. Install it from RPM or apt or yum, make a few tweaks to the smb.conf and I'm off and running without fail. So to run into a situation where I'm getting denied has really stumped me. I dialed up logging to try and get a peek into what's failing and things start falling apart around NT_STATUS_ACCESS_DENIED

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 have a Samba4 File Server on Debian 10 I am not being able to assign permissions on shares to groups that already have the Unix attribute set. Groups without the Unix attribute are working OK. My two DC are Samba4 (migrated of the Windows 2008 Server) and my current File Servers are Windows 2008 Server. I followed "Setting up a Share Using Windows ACLs" tutorial (

hi, now i did some tests with the "auth methods" option. "auth methods = sam, sam_ignoredomain, unix, winbind, wbc, trustdomain, ntdomain, guest" -> RDP works -> smbclient -k does not work "auth methods = sam, sam_ignoredomain, unix, winbind, wbc, trustdomain, ntdomain, guest, samba4" -> RDP hangs an the welcome-scrren -> smbclient -k works fine

Hello all, I have compiled a Samba 3.0.10 in a Solaris 9 box with OpenLDAP 2.2.17. The options i've compiled with are the following: ./configure --prefix=/opt/samba3 --without-readline --enable-shared=yes --enable-static=yes --with-acl-support --with-smbwrapper --with-sys-quotas=no --without-winbind --with-ldapsam This Samba is PDC of a windows mixed environment (95/98/XP). Sometimes a user

Hi, I try to install my linux as PDC. I followed the samba project documentation and some other doc. My samba is 3.0.0 alpha2.4 My smb.conf is with the user securrity, domain logons etc... Just like it should be I added the computername with the "$" sign Added the computername in smbpasswd but when i try to connect with my win2000 workstation i get "unknown user name or bad

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

New Polices created Denver policy is 1684 Atlanta Policy is 1441 IP address added 10.80.13.163 - this is allowed only to ATM services Jason Prouty CCT Manager Network Engineering 303-928-1588 Desk 720-412-1942 Cell ----- Original Message ----- From: "Davide Ianni via samba" <samba at lists.samba.org> To: samba at lists.samba.org Sent: Tuesday, January 16, 2018

Rowland, I solved this problem by removing old entries as you mentioned. Now the problem is that I lost access to my fileserver. I do not know why. If there is a problem with GPO. :( log: [2017/06/07 20:26:50.620631, 3] ../source3/smbd/oplock.c:1301(init_oplocks) init_oplocks: initializing messages. [2017/06/07 20:26:50.620835, 3] ../source3/smbd/process.c:1957(process_smb) Transaction 0

I am having the problem explained in the thread subject: samba 4.2 RDP problem The problem is when signing in a domain user via RDP. The authentications works but the machine hangs on the Welcome screen. In the samba log the last thing I see is: rpc command: WINREG_OPENHKLM As mentioned in that thread, changing the auth to: auth methods = sam, sam_ignoredomain, unix, winbind, wbc,

Hello, I have domain NAVIDOM. There is also a fileserver that has joined the domain (both file server and DC are samba 4.6.0). If I try to connect as NAVIDOM\Administrator, I cannot access the file server (from Linux and Windows): [root at dc var]# smbclient -U Administrator -L fileserv Enter NAVIDOM\Administrator's password: session setup failed: NT_STATUS_ACCESS_DENIED I can do it as

We have been running Samba 2.2.x for some time without problems. Servers are Solaris 2.7 and RH Linux. Clients are a mix of WinNTsp4 and Win2K. Server setting is for plaintext (un-encryted passwords). On upgrading the Samba server to 3.0.0, (smb.conf file unchanged): All WinNt clients fail to authenticare. Win2k clients authenticate correctly. On reverting back to Samba 2.2.x, all cleints

Hello. Laptop with windows 7 pro 32 bits (192.168.130.66) does not respond to nmblookup. But from the Laptop with windows 7 (192.168.130.66), using explorer.exe I can browse the content of the public ressource on the serveur //serveur-linux/publique I have update the windows 7 registry but it does not help. HKLM\SYSTEM\CCS\Services\LanmanWorkstation\Parameters DWORD DomainCompatibilityMode 1

PLEASE!! can somebody help me? I need much these! ----- Original Message ----- From: "Henrique" <henrique@astuto.com.br> To: "Samba Samba" <samba@lists.samba.org> Sent: Monday, June 21, 2004 3:35 PM Subject: Error C000019B > Hi everyone! im having problems with Samba 3.0.4 > > My PDC is samba+openldap+nss+pam+smbldaptools > > All work fine (posix

Hi, My configuration: 1 server with Samba4 as a DC (dc01) 1 server with Samba4 as a file/print server DC seems to work fine. file server is connected to DC using this howto https://wiki.samba.org/index.php/Samba/Domain_Member smbd, nmbd, winbindd is running on file/print server. Bu when I try with a windows client (a windows 2003 server) to connect to file server. client ask for a user

Hi Harry, sadmin and tadmin are both admin logins. I was trying to domain join with both. sadmin is in ldap The olcdbindex.ldif gave this error SASL/EXTERNAL authentication started SASL username: gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth SASL SSF: 0 modifying entry "olcDatabase={1}hdb,cn=config" ldap_modify: Other (e.g., implementation specific) error (80) additional