search for: samba_client

...email, it does not accept liability for any virus that may be contained in it. ******************************************************************** - From a W2K client connecting to a Solaris 9 Samba server I am getting a lot of these messages when running a snoop on the server: samba_server -> samba_client NBT Type=SESSION MESSAGE Length=1456 samba_server -> samba_client NBT Type=Unknown Length=1456 Anybody know what these are or if it's anything to be worried about? Cheers, Simon -----BEGIN PGP SIGNATURE----- Version: PGPsdk version 1.1.1 (C) 1997 Pretty Good Privacy, Inc. iQEVAwUBQAfgj...

...Samba client library, libtdb.so.1 application CSWlibwbclient0 libwbclient0 - Samba client library, libwbclient.so.0 application CSWsamba samba - Tools to access a servers filespace and printers via SMB (server) application CSWsamba-client samba_client - Client binaries for samba Normal 0 false false false EN-GB X-NONE X-NONE MicrosoftInternetExplorer4...

Hi Tim, This is just wild speculation: do You have different versions of Samba (or smbclient) on the corresponding machines? I run the same on all of my machines. I think that Kerberos is supposed to be OK. Also I hear of possible issues with very new versions of SSSD with Samba 4.2.0rcx due to a winbind(d) conflict. But the sad truth is, that I lack the competence to be really helpful.

Thanks for your reply. I had problems when updating from 4.1.16 to 4.1.17. I think it was the samba_client package I found this: http://www.stbsuite.com/support/virtual-training-center/nt-status-errors But not really helpful. Kerberos works so far but I will have a deeper into the logs. Am 27. Februar 2015 23:29:12 MEZ, schrieb Peter Serbe <peter at serbe.ch>: >Hi Tim, > >This is jus...

...nistrator/root to some admin unix group (forgot the details) and have the windows box automatically be added as a machine-user (e..g $freddy in your case) to samba. The relevant part of my smb.conf looks like: [global] workgroup = DOLLAR add user script = /usr/sbin/adduser -n -g machines -c Samba_Client -d /dev/null -s /bin/false %m$ server string = Samba security = user encrypt passwords = yes smb passwd file = /etc/samba/smbpasswd unix password sync = Yes passwd program = /usr/bin/passwd %u passwd chat = *New*password* %n\n *Retype*new*password* %n\n *passwd:*all*authenticat...

...hare/cups/drivers browseable = yes use client driver = yes guest ok = no read only = yes write list = root [tmp] comment = Temporary file space path = /tmp read only = no public = yes Here are the changes in cups log files when trying to print with samba (connecting to the printer with samba_client and then using put/print command) /* tail -f /var/log/cups/* */ ==> access_log <== localhost - - [21/Jan/2009:00:36:26 +0200] "POST / HTTP/1.1" 200 268 Get-Jobs successful-ok localhost - - [21/Jan/2009:00:36:26 +0200] "POST / HTTP/1.1" 200 189 Get-Printer-Attributes succes...