similar to: authentication problems sernet-samba

Hai, see the commented. And as extra, disable powersaving on the network card. > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens Lulzim KELMENI > Verzonden: vrijdag 2 oktober 2015 9:00 > Aan: samba > Onderwerp: Re: [Samba] authentication problems sernet-samba > > > > Hello Rowland, > > By "authentication

Hello Rowland, I think avahi-daemon is not installed as standard in ubuntu 14.04.3 LTS Here is in our server : ROOT at SERVER:~# DPKG -L |GREP AVAHI II  LIBAVAHI-CLIENT3:AMD64              0.6.31-4UBUNTU1                  AMD64        AVAHI CLIENT LIBRARY II  LIBAVAHI-COMMON-DATA:AMD64          0.6.31-4UBUNTU1                  AMD64        AVAHI COMMON DATA FILES II 

It this a test environment ? ... dctest.local Dont use .local reserved name of apples mDNS. Remove avahi from your server. Recheck nsswitch.conf so it starts like : passwd: compat winbind ( so if needed change the order ) Recheck you resolv.conf Should be : Search dominname Nameserver IP_DC1 And i you have itunes on your pc, remove it. And try again, this is not a samba

On 01/10/15 09:08, Lulzim KELMENI wrote: > > > Hello, > > We have installed samba4 under Ubuntu 14.04.3 LTS. > > root at server:~# samba -V >> Version > 4.2.3-SerNet-Ubuntu-7.trusty > > Sometimes, we have authentication > problems. > > The only thing we found in log file, when it happend, is > this : > >> [2015/09/28 17:27:06.750675, 3]

New to linux and new to Samba so any direction in troubleshooting would be helpful. Here is what I have so far. Within a half an hour of a reboot of the server my cpu reaches high numbers and becomes slow to respond on all actions. With my limited understanding I have used vmstat to observe the system. I noticed is that the numbers of forks grows from 1-2k to 43k within 30 minutes after reboot. I

Hi, I have a test AD running Samba on Ubuntu that I sometimes poke with Sysinternal's ADExplorer. A few days ago I tried connecting to it, but got a short reply of "The directory service is not available." As it was working earlier, I tried finding the problem. After installing a few older releases, I found that it was working on Ubuntu 17.04, Samba 4.5.8 and stopped working on

On 18/12/14 16:19, Germ van Eck wrote: > Not sure about the high CPU load, but you have the [netlogon] share > twice in your smb.conf. Your first matches mine, have you added the > second yourself? > The second one looks weird with 2 path definitions. > Cj Tibbetts schreef op do 18-12-2014 om 08:59 [-0700]: >> New to linux and new to Samba so any direction in troubleshooting

Hi, i have three problems in my AD. i have three DCs, four samba members and some Mac and Windows clients. first problem After some times my Windows and Mac clients can not login with the account cendentials. So i need to reboot the system and works fine. When the problem exists i got on my DC following log: [2016/03/03 12:39:10.029089, 3] ../lib/ldb-samba/ldb_wrap.c:320(ldb_wrap_connect)

Hi all, James, After following James' suggestions fixing the several dbcheck errors, and having observed things for a few days, I'd like to update this issue, and hope for some new input again. :-) Summary: three DCs, all three running Version 4.5.10-SerNet-Debian-16.wheezy, samba-tool dbcheck --cross-ncs reports no errors, except for two (supposedly innocent) dangling forward links

Hi, We have an issue where an existing Win 10 client is already part of the domain, however it's DNS entry isn't updated, Is this bug related? https://bugzilla.samba.org/show_bug.cgi?id=11520 please see details below Ubuntu: 16.04.01 LTS Samba: Version 4.3.9-Ubuntu Samba Internal DNS 'allow dns updates = nonsecure' is not specified >ipconfig /registerdns Samba-Log: sudo

I wanted to bring attention to some odd behavior which I don't believe is intentional. With Samba running, I can go to a Windows machine on the network (10.0.0.0/24) and see all of the Samba shares by pulling up an Explorer window and going to \\Server1 Everything appears to work as expected. However, if I populate the 'hosts allow' parameter within smb.conf as follows: hosts allow

Hi, We have three DC's, and one of them has been misbehaving a few times lately, stopping to replicate, showing the following error in samba-tool drs showrepl, for all DC partitions: > DC=DomainDnsZones,DC=samba,DC=company,DC=com > Default-First-Site-Name\DC2 via RPC > DSA object GUID: 5e93a102-2963-496a-af16-0c51eebb2e31 > Last attempt @ Wed Nov 11 06:41:21 2015 CET

12.08.2015 15:22, Rowland Penny пишет: > On 12/08/15 12:17, Dmitry MiksIr wrote: > > Hi, I think your kerberos ticket is expiring, but don't really know why. > > As Louis as said, you don't need these lines in krb5.conf: > > ticket_lifetime = 24h > renew_lifetime = 7d > Ok, i will try to remove. Lets see. > You also don't need these lines in smb.conf:

Hi , Thank you for your input. I have had tried all of the escape characters you have have tested with but I have had no luck with them. I am curious to know which versions of net have you been tested with? I do agree that the best practice for this is to remove "-" from the beginning of the object name, However, seeing that it can be created that way allowed, I would like to find a

We have 3 ADCs based on Samba-4.7.4 (compiled from source,internal DNS)/ CentOS7: dcdo1,dcnh1 and dcge1. dcge1 holds all FSMO roles. The 3 ADCs are on different locations connected via IPSec based VPN. No traffic is filtered out. All 3 ADCs replicate fine except dcdo1 -->dcnh1. Symptom: [root at dcdo1 ~]# samba-tool drs replicate dcnh1.ad.kdu.com dcdo1.ad.kdu.com dc=ad,dc=kdu,dc=com

Hi all, Sernet Samba 4.2.2 as Active Directory on Debian 7.8. No other DC. I can't log in with on Windows systems (Windows 7) when samAccountName are longer than 20 characters. This seems to be a LAN MAN or NT4 limitation which should not happen on AD domain. Any idea what could leads my to that limitation? I can log in using administrator account or any other having a short (enough)

Thank you Rowland!! Sorry about my ignorance. I guess I tried many different things and polluted the smb.conf file. I've removed every single line you mentioned off my smb.conf. Still the problem persists: MYDOMAIN\Administrator (S-1-5-21-1965676298-842383976-2353361141-500) is changing password of user2 at MYDOMAIN.org.ar [2017/04/21 12:05:42.233899, 3]

On Wed, 27 Dec 2017 13:00:05 +0100 "Dr. Johannes-Ulrich Menzebach via samba" <samba at lists.samba.org> wrote: > There is additional info in the logs of the source DC (dcdo1, log > level 2, manually triggered another replication): > ==================== > [2017/12/27 12:31:29.695121,  2] >

Hi, I had Samba 4.2.14 working as AD DC with shares. After upgrade to version 4.3.11 AD DC authentication, ADUC, etc, stopped working. Shares still work fine. OS. Oracle Linux 6.x with UEK, uptodate. Samba compiled from source. Upgrade procedure (nothing special): ./configure --enable-selftest make make install Testparm output: # Global parameters [global] workgroup = EXAMPLE realm =

I would like to bump my question 2015-05-27 10:21 GMT+03:00 Krutskikh Ivan <stein.hak at gmail.com>: > Hmm, looks like it's not. I've just set the password for something that > cracklib-check would argue using both ad management tools and at windows > login. Should it work that way or I'm missing something? > > My dc's smb.conf: > > [global] >