similar to: Unable to contact active directory or verify claim types

I set "server min protocol = SMB2" and "server max protocol = SMB2" . Which then resulted in the Win 2012 R2 server being unable to access the Samba server as \\weirdserver <file://weirdserver> . But I can access via \\weirdserver.mydomain.com <file://weirdserver.mydomain.com> or \\ipaddres <file://ipaddres> . Logs on samba server for that client

I am running several Solaris 11 file servers with samba 4.7.6. This is an AD domain but the domain controllers are Win 2008 R2 and Windows 2012 R2. All users and groups in AD have unix uidNumbers and gidNumbers assigned. On one file server, I am having problems where some users can not access files , via windows, to which they should have access as the group member. For example,

On Wed, 25 Jul 2018 12:14:30 -0400 Gaiseric Vandal <gaiseric.vandal at gmail.com> wrote: > My partial smb.conf and nsswitch.conf is as follows.  FYI the user in > question is able to access directories via ssh so the permissions and > group membership seems correct - at least on the unix level. > > > root at weirdserver:~# getent passwd | grep myname >

Hi, Can I request some suggestions regarding the following? Issue1 In our AD server, we are not seeing the hostname of the machine in smbstatus, it only shows IP. How can we see the hostname? The server can ping/resolve the hosts in question. PID Username COM Machine Protocol Version Encryption Signing

I recently discovered that only the Default Domain Policy is being applied. All other GPOs seem to be ignored. All Sysvol filesystem objects have the right permissions. Both DCs are running Samba 4.4.3 over CentOS 7. There are no related errors in logs or Windows Event Viewer. Other policies did work before. I noticed that the corresponding filesystem objects were lastly placed on users’ desktops

Am 02.11.2016 um 20:32 schrieb Saint Germain via samba: > On Wed, 2 Nov 2016 16:45:31 +0100, Achim Gottinger via samba > <samba at lists.samba.org> wrote : >> Am 02.11.2016 um 15:50 schrieb Saint Germain via samba: >>> On Wed, 2 Nov 2016 14:44:05 +0100, Achim Gottinger via samba >>> <samba at lists.samba.org> wrote : >>>>>>> I just

Am 02.11.2016 um 15:50 schrieb Saint Germain via samba: > On Wed, 2 Nov 2016 14:44:05 +0100, Achim Gottinger via samba > <samba at lists.samba.org> wrote : >>>>> I just tried and when I limit samba to SMB2 connections (in >>>>> smb.conf), Nautilus/gvfs cannot connect (it doesn't even see the >>>>> share). >>>>>

On Thu, Aug 2, 2018 at 11:11 AM, Rowland Penny via samba < samba at lists.samba.org> wrote: > On Thu, 2 Aug 2018 11:02:45 -0400 > pisymbol <pisymbol at gmail.com> wrote: > > > Whoops! Replying to all! > > > > On Thu, Aug 2, 2018 at 10:55 AM, Rowland Penny via samba < > > samba at lists.samba.org> wrote: > > > > > On Thu, 2 Aug 2018

Am 02.11.2016 um 03:05 schrieb Saint Germain via samba: > On Fri, 28 Oct 2016 19:10:12 +0200, Achim Gottinger via samba > <samba at lists.samba.org> wrote : > >> >> Am 28.10.2016 um 08:18 schrieb Saint Germain via samba: >>> On Thu, 27 Oct 2016 17:30:09 -0700, Jeremy Allison <jra at samba.org> >>> wrote : >>> >>>> On Thu, Oct

Am 28.10.2016 um 08:18 schrieb Saint Germain via samba: > On Thu, 27 Oct 2016 17:30:09 -0700, Jeremy Allison <jra at samba.org> > wrote : > >> On Thu, Oct 27, 2016 at 05:22:14PM -0700, Jeremy Allison via samba >> wrote: >>> Looking around inside that source code I also see: >>> >>> do_read (GVfsBackend *backend, >>>

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

[global] workgroup = example realm = example.test netbios name = server1 server role = active directory domain controller log file = /var/log/samba/smbd.log server services = s3fs, rpc, nbt, wrepl, ldap, cldap, kdc, drepl, winbindd, ntp_signd, kcc, dnsupdate domain logons = Yes wins support = Yes security = user preferred master = auto domain master = yes local master = yes unix extensions = no

I have a to a samba server (4.4.16) on built on Solaris 11 samba pkg. It is a member of an Active directory domain. Users, for some time, have been experiencing long (20 -40 second) delays when browsing to, opening and writing a network share on the server. Attempts to do any of those results in a dialogue box being displayed showing: Contacting server: \\<server-name> \share

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

On 08.04.19 16:20, L.P.H. van Belle via samba wrote: > Hai Basti, > > Anything in the windows even logs? > This might be related to smb1 and windows automaticly removing it. smbstatus say that all open connections are SMB2_10 and SMB3_11 the windows log say: german text and errorcode C0000006 > > Or something else. > Can you check with mtr from a windows pc to the

Thank you for answer. Logged in as Guest, then went to Security tab. I see `Everyone', it is given all permissions. Then I went to `Current permissions' tab (I have localized OS at the moment, so probably it is not correct name) and typed in `Everyone' and `Guest' as well: all five permission types are checked. $ smbclient -L 192.168.0.100 -m SMB2     Sharename      

Hi guys I have configured a samba4 ADDC. It working well but users homes share did not display. How can we solve this problem. Please help me.

Whoops! Replying to all! On Thu, Aug 2, 2018 at 10:55 AM, Rowland Penny via samba < samba at lists.samba.org> wrote: > On Thu, 2 Aug 2018 10:43:26 -0400 > pisymbol via samba <samba at lists.samba.org> wrote: > > > Full disclosure: This is an exported share on a QNAP NAS device. > > Even fuller disclosure ;-) > You haven't given us enough info > I can

Hello, Thank you ! I add server min protocol = SMB2_02 to smb.cnf All clients are now using SMB2_10 as minimum protocol version May you indicate me the difference between "client min protocol" and "server min protocol" ? "server min protocol" is to use on a domain member "client min protocol" is to use in which case ? Should I also set client min

Hello, First of all I would like to thank the Samba Project Group for this state of the art software. I would like to thank every body for helping each other out. Please ignore my poor English writing. It is not my native language. Although: I do the best I can. We use Samba for a while now. We started with version 4.0.6 and updated each time. Now we are at version 4.0.9 and we are planning to