similar to: CONNECTION_REFUSED

Hi More info: The log.smbd shows the following lines when tryied to login as Administrator ---------------------------------------------------------------------------------------------------------------- [2016/05/11 08:09:36.411968, 2] ../source3/param/loadparm.c:2686(lp_do_section) Processing section "[netlogon]" [2016/05/11 08:09:36.412108, 2]

On 02/14/2018 07:46 PM, Rowland Penny via samba wrote: > On Wed, 14 Feb 2018 19:05:34 +0100 > Arne Zachlod via samba <samba at lists.samba.org> wrote: > >> Hello, >> >> I have a problem with my samba installation I can not get my head >> around, maybe some of you have a good idea about what is going on. >> >> I have a file share called

Hi sorry to bother, but all of a sudden after a fresh install of samba with the regular smb4.conf it keeps on failing when users try to authenticate: smbclient -U MyUser \\\\MyServerName\\MyShare MyPassword session setup failed: NT_STATUS_UNSUCCESSFUL [...] check_ntlm_password: authentication for user [MyUser] -> [MyUser] -> [MyUser] succeeded [2014/05/02 10:29:40.930648, 3]

Hai Stefan, Can you try the following. Reboot the server, then reboot the pc, then login with the not working user. When/If that works, then login and login with the other users try then. And, i bet you checked it, but must ask, time in sync? Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Stefan G. Weichinger

On Wed, 14 Feb 2018 20:43:20 +0100 Arne Zachlod via samba <samba at lists.samba.org> wrote: > > > If you run 'smbclient -L adfs02.int.becit.de -U > > brokenuser at int.domain' on 'adfs02', does this work > > no, same error: > root at adfs02:~# smbclient -L adfs02.int.domain -U brokenuser at int.domain > Enter brokenuser at int.domain's

[2017/07/11 10:28:51.553290, 3] ../source3/auth/auth.c:249(auth_check_ntlm_password) check_ntlm_password: winbind authentication for user [mueller] succeeded [2017/07/11 10:28:51.553324, 2] ../source3/auth/auth.c:305(auth_check_ntlm_password) check_ntlm_password: authentication for user [mueller] -> [mueller] -> [mueller] succeeded [2017/07/11 10:28:51.553493, 1]

Hello, I need to do a classic migration on a machine which has until now been running samba as an old NT4-style PDC. I made a copy of that machine in a VM to test the process. Until now, things don't work quite right. I was following the classic upgrade howto from wiki.samba.org. I was using the method with internal DNS. Classicupgrade itself ran without errors, I followed the steps after

On Sun, 7 May 2017 09:04:25 -0500 Michael Schwager via samba <samba at lists.samba.org> wrote: > Hello, > I cannot access a remote drive using Windows or smbclient; my > authentication appears successful according to the samba log file, but > `getpwuid` fails. The server (remote) is running CentOS 7.2 and Samba > 4.2.3. The client is CentOS 7.2 and smbclient 4.2.3. The

Hello, I cannot access a remote drive using Windows or smbclient; my authentication appears successful according to the samba log file, but `getpwuid` fails. The server (remote) is running CentOS 7.2 and Samba 4.2.3. The client is CentOS 7.2 and smbclient 4.2.3. The logfile shows: [2017/05/06 22:57:48.729284, 2] ../source3/auth/auth.c:305(auth_check_ntlm_password) check_ntlm_password:

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 all, Still looking for the best way to achieve consistent GID/UID mapping on Linux servers/clients, in heterogeneous environment (Linux, Windows, CIFS, NFS). Current problems with UID/GID resolution prevents from using Samba4 in environment with backups (where data may be restored on another server) and mixed Linux/Windows workstations. Just recently installed fresh Samba 4.1.0 on the server

On Tue, 11 Jul 2017 10:36:08 +0200 "Stefan G. Weichinger via samba" <samba at lists.samba.org> wrote: > > [2017/07/11 10:28:51.553290, 3] > ../source3/auth/auth.c:249(auth_check_ntlm_password) > check_ntlm_password: winbind authentication for user [mueller] > succeeded [2017/07/11 10:28:51.553324, 2] > ../source3/auth/auth.c:305(auth_check_ntlm_password)

Hi Rowland, Thanks for the reply. I did as you suggested and did not see any change in my system behavior. I put everything back the way it was. Then I noticed that I have an identical system (so I think) right next to it, on the same rack, connected to the same switch, with the same OS and hardware, and it is working 100%. Fundamentally, I cannot su to my user "developer_prod" as the

samba-4.6.8 on both DC and DM. 3 users were created as suggested: DC # samba-tool user create kamleitnerl Le26xxx --nis-domain=arbeitsgruppe --unix-home=/home/kamleitnerl --uid-number=10070 --login-shell=/bin/false --gid-number=100 this user can login to a Windows PC, but not access/connect shares. log for the PC's IP: [2017/09/25 15:45:10.522051, 1]

Hello all, I have really strange problem with Samba 4.1.0 - regarding only one user - Administrator. There are 2 servers: NAS (which is DC) and CHEETAH (Which is domain member). Have spent long time in efforts to sync UID/GID across servers (these are used both from Linux over NFS and from Windows) - and finally wrote the scripts to make all users/groups (even including the builtin one, like

Hello. I'm in need of some help to shed some light on a strange problem. The box is running Samba 4.1.7 on FreeBSD 9.2/amd64 and I suspect (though I'm not sure) all troubles started after the upgrade from 4.1.6. The setup is quite simple: no AD, no LDAP, only one server. A command as simple as "smbclient -U user //SERVER/SHARE", if fired up several times in a row on the

Following the wiki replication guide precisely I got to this step. [root at smb4-2 ~ (master)]# rsync -XAavz --delete-after smb4-1.brockley.harte-lyne.ca:/var/db/samba4/sysvol/ /var/db/samba4/sysvol/ receiving file list ... done ./ brockley.harte-lyne.ca/ . . . brockley.harte-lyne.ca/scripts/ sent 142 bytes received 1,683 bytes 3,650.00 bytes/sec total size is 182 speedup is 0.10 [root at

Greetings; I have been trying to set Samba on the latest release of Fedora to share some files on my office network. Here is my smbd.conf file: #======================= Global Settings ===================================== [global] workgroup = Maison server string = Linux netbios name = Linux encrypt passwords = yes wins support = yes [data] path = /data browseable = yes

Every 10 minutes, my samba 4.0.9 (active directory domain controller) is logging messages like these :- 2014-01-07T14:26:09.896260+11:00 gumbo samba[5198]: /usr/sbin/samba_dnsupdate: ; Communication with 127.0.1.1#53 failed: operation canceled 2014-01-07T14:26:09.896281+11:00 gumbo samba[5198]: /usr/sbin/samba_dnsupdate: could not talk to any default name server 2014-01-07T14:26:09.917096+11:00

I have a shorewall 2.0.14 running on a single interface machine (nwww in the log below) that is attempting to be well screwed down. The policy file reads:- #SOURCE DEST POLICY LOG LEVEL LIMIT:BURST fw net DROP info net all DROP info # The FOLLOWING POLICY MUST BE LAST all all