similar to: Permission denied but ok?...

I'm running samba4 as an AD DC, built from git (built ~3 days ago), with about ~20 Windows 8 clients. I've noticed a number of errors in the logs, pasted below. That group of errors repeats pretty consistently for a lot of different client machines. [2013/09/08 08:12:14.539679, 2] ../source3/smbd/reply.c:592(reply_special) netbios connect: name1=SERVER-NAME 0x20

So, I have "working" builds of Samba 3.6.10, and 4.0.2 using the traditional build system on AIX, both built with XLC. For historical reasons, we're needing to use 'encrypt passwords = no', so that Samba uses the OS password. The odd thing, is, the 3.6.10 Samba works just fine, but the 4.0.2 doesn't allow connections. Here's the Samba config I'm using on both:

Hello In 2 different subnets I have setup 2 identical samba servers (RH 6.5) as fileservers for windows clients. Each is a member of it's own AD Domain (Windows 2003 Servers). The problem: one of them only is accessible and sharing locally. On the windows-client, trying to mount a share gives this error: C:\Users\testuser>net use y: \\samba_server\topfolder /user:testuser System

Hello I've migrated a samba 3 server to a samba 4 (.all the tests mentioned in this howto are succesfull) .But i can't open a session with a workstation on samba4 domain : approbation problem. The workstation name which can't connect is "admin-pc" Any idea ? *Here are the logs of log.samba * Kerberos: Looking for ENC-TS pa-data -- *admin-pc$@SC* [2012/12/06 12:50:59,

Hi All, One day we upgraded client pc's OS from Windows7 to Windows10, Windows10 clients could not access a samba server. When we re-enabled the SMBv1 protocol on Windows10, Windows10 clients still could not access a samba server. After adding the following [global] settings, Windows10 clients could access a samba server at last.

And this is some Samba logs from a connect where the profile isn't handled properly. Near the end, it looks like Samba resets this connection... (I could be wrong - I know nothing about how to read Samba logs.) --- [2019/01/24 10:36:38.097773, 3] ../lib/util/access.c:361(allow_access) Allowed connection from 10.8.20.60 (10.8.20.60) [2019/01/24 10:36:38.097869, 3]

Hai, Try these settings in global settings. ####### Authentication ####### ## stand alone everything open. security = user guest ok = yes map to guest = bad password add these to the share. guest ok = yes Sets samba open without pasword prompt. I use it at home for my kodi server. Greetz, Louis >-----Oorspronkelijk bericht----- >Van: r.olszewski at ssc-services.de

Hi Gregory, I see few things, start here : from smb.conf remove : map to guest = Bad User This enabled on a domain member or other domain server is really a no go. This makes debugging really hard. interpret_string_addr_internal: getaddrinfo failed for name > freenas.ad.abc.local (flags 1026) [hostname nor servname > provided, or not known] Looks like there are resolving problems.

So you use images!? Are you shure you used different host names for each client. We found using install images will do this confusion some times because windows announced with the image name not with the new one. EDV Daniel M?ller Leitung EDV Tropenklinik Paul-Lechler-Krankenhaus Paul-Lechler-Str. 24 72076 T?bingen Tel.: 07071/206-463, Fax: 07071/206-499 eMail: mueller at tropenklinik.de

Hi, I'm new here and I've got a problem. OK this is evident. Running OpenSuSE 13.1 as SAMBA4-PDC with openLdap-backend. All from SuSE Repos. Works fine except joining a Windows-Client to the domain. This means also no shared-profiles. I'm able to use the shares from the PDC on the windows-clients. User- and group-permissions are working. smb.conf: [global] workgroup = BIH

Timo Altun skrev den 2015-05-19 08:12: > Hi Davor, > > thanks for the answer. They were actually part of a NT4 domain called > mayweg.net <http://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

Hi, this is the first time I've tryed to build a 64 Bit Version with acl's enabled - so I expect I could duplicate this with older versions too... Here's the build info: System: AIX 6100-07-01-1141 Compiler: IBM xlc CC=xlc_r -g CXX=xlC_r CFLAGS=-qmaxmem=-1 -DSYSV -D_AIX -D_AIX32 -D_AIX41 -D_AIX43 -D_AIX51 -D_AIX52 -D_AIX53 -D_AIX61 -D_ALL_SOURCE -DFUNCPROTO=15 -O

I?m not sure if this is related, but there was a regression a while back in handling resource forks in folder icons. It was supposed to be fixed in 4.10.13 but I don?t think it quite works yet and I haven?t had the time to test it further yet. -Perttu > On 30 May 2020, at 21.00, Martin Steiner / 3MF GmbH via samba <samba at lists.samba.org> wrote: > > I changed the configuration

Hello, Came across a crash on samba-server(4.4) RHEL-7.3. (gdb) bt #0 0x00007f8e1e4821d7 in __GI_raise (sig=sig at entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #1 0x00007f8e1e4838c8 in __GI_abort () at abort.c:90 #2 0x00007f8e1fde2c4b in dump_core () at ../source3/lib/dumpcore.c:322 #3 0x00007f8e1fdd6007 in smb_panic_s3 (why=<optimized out>) at ../source3/lib/util.c:814 #4

Hello, I have a centOS 5.5 box acting as as a PDC with samba 3.4.9 and openldap 2.4.22. Then I joined the domain with a centOS box (samba 3.4.17) which hosts the homes and profiles. I have no problem with XP clients. I can join a windows 7 client to my domain but it is unable to load the profile when logging in. See below a level 2 log.smdb from the file server when I log in with a domain

Hello I have an samba server with a public share. It was configured with security=share. Now I have to tight security with setting those flags in the windows client: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\LanmanWorkstation\Parameters] EnablePlainTextPassword=0 EnableSecuritySignature=1 RequireSecuritySignature=1 Since this change the public share is not working anymore. I found

I have tried everything, This is CentOS 6.4 with SELinux DISABLED, Bind version BIND 9.8.2rc1-RedHat-9.8.2-0.17, samba 4.0.6 downloaded as a tar.gz from samba.org -- I have read EVERY maillinglist, IRC Log, how-to on google, tutorial on samba.org, and many many people have had this problem and not once have any of the posters resolved it, so I am now a desperate man reaching out to you with as

I changed the configuration and raised the log level, in my opion samba tries to access the non existent double files. Samba is now probably writing the data in a netatalk compliant way in the extended attributes of the file but is not reading it. new configuration: [Global] min protocol = SMB2 vfs objects = catia fruit streams_xattr fruit:metadata = stream fruit:resource = stream fruit:encoding

On 2015-05-20 09:21, Timo Altun wrote: > 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

I wrote a powershell script on a windows computer to write an ADS on a file on a FreeBSD server with streams_xattr enabled. If it's smaller than 64KB, it succeeds. If it's larger than 64KB, I get an "access denied message" and powershell crashes. FreeBSD actually allows creation of large extended attributes (at least on ZFS volumes). I've personally added ones of up to 3MB in