search for: client_specific_logging

...fore? Is there a log file I can look at to >> determine >> what is going wrong in the protocol negotiation? >> >> Thanks! >> >> --Bill >> > You can enable client specific logging and see if it turns up anything. > > https://wiki.samba.org/index.php/Client_specific_logging > > Access a share and review the logs. > > Is this Windows 7 workstation accessing the new member server and > displaying NT1 or the old one? > > Can you run on both member servers and report? > > testparm -v |grep "client ipc max protocol" and testparm -v |gre...

Hi, I recently migrated from samba3 to samba4. On the samba3 server I had a "printer" that converted pcl6 to pdf. I tried to make a similar printer in samba4, but it's not working. Not working means the printed document is nowhere to be found. This is the section in smb.conf : [papyrusPDF] comment = Papyrus-to-PDF printer path = /var/spool/samba # guest ok = Yes

2015-06-29 9:39 GMT+02:00 Koenraad Lelong <samba.k.lelong at ace-electronics.be >: > Hi, > > I'm still trying, with no success. > Is the following example still valid : > https://wiki.samba.org/index.php/Virtual_PDF_Printer > > It dates from 19 August 2014, so I expect it should work with samba4, > although it's not working for me. > > I tried logging

Hi All, I just setup a new server and added it to my domain last week and it has been working well. We are running a NT4-style Samba PDC for our domain controller. This server is running the CentOS packages for Samba 4.2.10-6 as a domain member. My issue is that I have one Windows 7 workstation that will only auto-negotiate to the NT1 protocol. If I run smbstatus, all of my other workstations use

...gt; look at logfiles and say "Oh, well, *this* is what's you're doing > wrong" or "Ah! The code's broken because of <this>", or whatever. > > Regards, > Jim Are you by chance using client specific logging on Samba? https://wiki.samba.org/index.php/Client_specific_logging Do the windows logs display anything relevant? -- -James

...he error already happens before samba tries to do anything like GetNCChanges? (since the error above seems to appear in rpc_parse) Or do I need to setup other logging for GetNCChanges errors? (and if yes: how do I do that?) (this is how I acheved the log above: https://wiki.samba.org/index.php/Client_specific_logging Best, MJ

...to >>> determine >>> what is going wrong in the protocol negotiation? >>> >>> Thanks! >>> >>> --Bill >>> >> You can enable client specific logging and see if it turns up anything. >> >> https://wiki.samba.org/index.php/Client_specific_logging >> >> Access a share and review the logs. >> >> Is this Windows 7 workstation accessing the new member server and >> displaying NT1 or the old one? >> >> Can you run on both member servers and report? >> >> testparm -v |grep "client ipc max...

...note you need to add the debug packages) > > Rowland Thanks for the prompt reply. When you say debug packages which do you mean? I can't see any with 'debug' in the name on the apt.van-belle.nl repo. I've enabled level 10 debug logging as per https://wiki.samba.org/index.php/Client_specific_logging (though I didn't configure it per client) and generated a log file of 1GB in 15 minutes. The local shared drive (hosted on a QNAP domain member) started to become unable to authenticate users (I think due to system load on the domain controller). I may need to run this for a couple of days to c...

...oot root 22905810 Oct 6 08:43 log.172.16.232.30 -rw-r--r-- 1 root root 705 Oct 6 08:39 log.172.16.232.97 Created sym link to debug file ln -s /usr/local/samba/etc/smb.conf.client-debug /usr/local/samba/etc/smb.conf.client-172.16.232.30 Followed the wiki at https://wiki.samba.org/index.php/Client_specific_logging pdc1:~# /usr/local/samba/sbin/samba -V Version 4.3.0 Ubuntu 12.04 [global] workgroup = SAMBA realm = SAMBA.LOCAL netbios name = PDC1 server role = active directory domain controller dns forwarder = 8.8.8.8 idmap_ldb:use rfc2307 = Yes log...

...2_10, as expected. > > Has anyone seen this before? Is there a log file I can look at to determine > what is going wrong in the protocol negotiation? > > Thanks! > > --Bill You can enable client specific logging and see if it turns up anything. https://wiki.samba.org/index.php/Client_specific_logging Access a share and review the logs. Is this Windows 7 workstation accessing the new member server and displaying NT1 or the old one? Can you run on both member servers and report? testparm -v |grep "client ipc max protocol" and testparm -v |grep "client ipc min protocol"...

...file I can look at > to determine > what is going wrong in the protocol negotiation? > > Thanks! > > --Bill > > You can enable client specific logging and see if it turns up > anything. > > https://wiki.samba.org/index.php/Client_specific_logging > > Access a share and review the logs. > > Is this Windows 7 workstation accessing the new member server and > displaying NT1 or the old one? > > Can you run on both member servers and report? > > testparm -v |grep "client ipc max protocol"...

Hi list, Is there a way with Samba 4 AD to log when a user and computer are logged in? What we're looking for is to solve the scenario of students or faculty logging in on a workstation (with their username and password), doing something bad online, and the SysAdmin having to scour through the log files for a specific date and time, and figure out who was logged in at the time of the

...g' in the name on the apt.van-belle.nl > repo. You need the ones that end in '-dbgsym' , see here for an example list: http://apt.van-belle.nl/current-packages-in-buster-samba412-apt.txt > > I've enabled level 10 debug logging as per > https://wiki.samba.org/index.php/Client_specific_logging (though I > didn't configure it per client) and generated a log file of 1GB in 15 > minutes. The local shared drive (hosted on a QNAP domain member) > started to become unable to authenticate users (I think due to system > load on the domain controller). I may need to run this for a...

Hi Ralph Boehme, With "server smb encrypt = no" I can't reproduce the problem. So I don't know how I can deliver you a pcap file with unencrypted network packets. Best regards, Hans van Leeuwen -----Original Message----- From: Ralph Boehme <slow at samba.org> Sent: Tuesday, October 29, 2024 3:47 PM To: Hans van Leeuwen <HansvanLeeuwen at mailstreet.nl> Cc: samba

...what is going wrong in the protocol negotiation? >> >> Thanks! >> >> --Bill >> >> You can enable client specific logging and see if it turns up >> anything. >> >> https://wiki.samba.org/index.php/Client_specific_logging >> >> Access a share and review the logs. >> >> Is this Windows 7 workstation accessing the new member server >> and displaying NT1 or the old one? >> >> Can you run on both member servers and report? >> >>...

Hi Bjorn, I don't know if there are any compile switches they provide more debugging / log options. I guess its easy to modify the start up script so that logging is at a max. Was just an after thought really. I just think binaries for distro's are really important and many thanks. Stuart. PS I never got a reply but with 4.1.6 but with vfs objects = btrfs declared in smb.conf disk

On Sun, 7 Jul 2024 00:55:20 +0100 Jonathan Hunter via samba <samba at lists.samba.org> wrote: > Hi, > > I recently noticed that two separate Windows 11 machines joined to my > domain are not letting me log in to them as a domain user. In the > Windows Security event log I can see 'Audit Failure' - 'An account > failed to log on'. Details shown are:

On 30/06/15 07:46, Koenraad Lelong wrote: > Op 29-06-15 om 23:47 schreef Jack Downes: >> > >> >> Interesting, I don't read that log as not finding the printer, but >> rather not finding the job. I think you're going to want to find out >> where samba thinks it's writing file and validate that anything actually >> goes in there. Turn up the

I'm running a PDC on Samba 3.60. Just freshly upgraded it from Samba 3.028a with the purpose of supporting Windows 7. However though all the existing users and computers are running fine, I'm stumped trying to join a new Windows 7 machine to it. I have applied the DomainCompatibility registry fix. When I try to join a Windows 7 workstation I will get this message : The join operation

Hi, Reading the microsoft troubleshooting guide, it seems that password hash sync issues can be caused by: > The Active Directory account used by Azure AD Connect to communicate > with on-premises Active Directory is not granted Replicate Directory > Changes and Replicate Directory Changes All permissions, which are > required for password synchronization. How to verify existance or