similar to: Samba Share with user and no password

Are there any logs on the client or server at a higher log level? Andrew Bartlett On Wed, 2020-05-20 at 12:39 +1200, Grant Petersen via samba wrote: > I forgot to mention that using the smbclient option > > -A /etc/cred/authfile > > behaves the same way as attempting to manually enter the password on > the command line; failing in 4.12.2 and working in 4.11.0 > >

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 (

On 05.09.19 16:14, Rowland penny via samba wrote: > try adding 'null passwords = yes' to your smb.conf. I have try. but can't connect (NT_STATUS_CONNECTION_RESET). Log append. Config: [global] workgroup = workgroup dns proxy = no log file = /var/log/samba/log.%m max log size = 5000 log level = 3 passdb:5 auth:5 syslog = 0 panic action =

Mandi! Rowland penny via samba In chel di` si favelave... > Even though your users may have the same username in AD as in the NT4-style > domain, they are different users, so a few thoughts. You have 'map to guest > = bad user', so I take it you must have 'guest ok = yes' set in the shares > (you haven't shown us the shares), so try changing 'bad user' to

Hello, I have a strange problem with Samba AD member: It is accessible via \\server or \\server.domain.local But when I try to access it with its IP address, ex. \\10.15.10.1 I get access denied error and prompt for user and pass. Entering username and password with or without DOMAIN\ has no effect. The server is FreeBSD 10.1. It behaves the same way with Samba 4.1.18 and now with Samba 4.2.2

Hello, I am attempting to debug an issue with my Samba configuration. It has been working fine, but we recently updated Samba from 4.6.x to 4.8.3 and are now seeing some issues authenticating. Most of our servers are still working fine after the upgrade, but one server is giving us issues. A little more environment info: The server is running Centos 7.1. Windows clients can connect OK. We are

Hai, The best info is missing. What are the windows event ID errors? What is the right set on the profiles folder? If you layout is : /home/samba/profiles and you shared the folder profiles, then show me getfacl /home/samba/profiles. I see your running, Samba 4.7, are you able to upgrade to 4.9.4? This: ~# cat default-rights-sysvol.acl # file: /var/lib/samba/sysvol # owner: root #

Hi all. I am running Debian jessie server with Samba, which has joined the Active Directory domain. The domain controllers are Windows Server 2012 R2. After I upgraded Samba version from 4.1.17+dfsg-2+deb8u2 to 4.2.10+dfsg-0+deb8u2, I'm facing the problem that I can't access Samba share by NetBIOS Aliases or IP Address. The Samba's NetBIOS name is mysamba, and I can access by

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

Installed Samba 3.0.10 via 'pkgadd' on Solaris 2.6 - previously running Samba 2.2.8. It starts up and SWAT confirms that it is running and I am using the same smb.conf but I am unable to connect to a share via PC. Message "\\s080 is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access

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

Good morning Rowland and samba list ... Rowland Penny wrote on 03.07.2015 18:36:32: > From: Rowland Penny <rowlandpenny241155 at gmail.com> > To: samba at lists.samba.org, > Date: 03.07.2015 18:40 > Subject: Re: [Samba] Migration Samba3 -> Samba4: Accessing domain > member server is not working > Sent by: samba-bounces at lists.samba.org > > On 03/07/15

Hello to the Samba Mailing List, This is my first post, so please, should I commit any faux pas, nudge me in the right direction and I will adjust accordingly. I'm experiencing a complete failure of the PDC in a Samba 4 AD Domain I've deployed for a client. Samba failed a few days ago and I've been unable to resolve the issue on my own. Google searches are leading me in circles,

Hi, I encountered a strange problem...some of my windows machines cannot be joined to an Samba 4.17 AD domain (8 of ~90 clients). These are 7 Win7 clients and one WinXP client. The message I receive in windows is: "Logon failure: unknown user name or bad password". All other Win7 and XP machines could be joined...the same OS image has been used to install both the machines that could be

Hi Davor, thanks for the answer. They were actually part of a NT4 domain called mayweg.net (the new realm name). But I did join workgroup "WORKGROUP" before I tried to join the new domain. If it's possible that they're sending the information the wrong way because they were part of a workgroup named after the new realm, is there any way to clear the old data (apart from a new

Hi Davor, most of the domain accounts were part of an old NT4 domain. I did a classicupgrade. Your theory with the NTUSER.DAT-files seemed so promising, unfortunately that was not it. I created new accounts on an XP machine and a Win7 machine and tried to join with them, but still receive the same error. One of the machines I'm not able to join with, wasn't even part of the domain

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

Hi Davor, I finally found it! After going through https://wiki.samba.org/index.php/Joining_a_Windows_Client_to_a_Domain , I checked the time settings on said clients and they differed from the AD DC too much. This also explains why some clients could join after a while...they synchronised with a NTP server after a day or so and then I was able to join. After that, joining the rest of clients was

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

Hi, Just a moments ago i've sent a message to other user saying that I've a working server with CUPS authentication using AD groups. Well, that authentication is not working anymore and i've not changed anything... The thursday I was configuring the server to allow the management of cups with AD groups and was working perfect. After that i've added some printer alias to samba