search for: uusers

Hi, I?ve got the following problem: When accessing a share on a Samba server from Win2000 or Windows XP this fails. The access is denied. All the shares are visible within ...\Network Neighbourhood\Workgroup\Chs-server.chs.\share1 ...\Network Neighbourhood\Workgroup\Chs-server.chs.\share2 ... ...\Network Neighbourhood\Workgroup\Chs-server.chs.\Drucker und Faxdienste Besides this I see the

Hi! I have MS domain, based on MS Windows 2000 Server. I successfully joined my samba box (Linux 2.5.53, Samba 2.2.4) to domain via smbpasswd -j DOMAIN -r DC -Uuser%pwd. So when I try to open Samba box via network neighbornhood I got pop-up window with inputs of username and password, I tape valid values and got this popup again. In samba log I see this: [2003/02/12 09:27:58, 0]

Ok folks, here goes: We have an old NT4 machine that we wish to replace as the PDC on our network. In it's place, we've got a dual xeon box with Mandrake LE2005 and Samba 3.0.13-2 and I'm currently trying to draw the accounts over with vampire. I'm using tdbsam as a backend. I've been through several readme's and howto's and have created all the UNIX accounts,

I'm trying to get a backup system going. I've got a script that will grab all the files I need, but there are several gigs. The command line i'm using now is: smbclient file://server/share XXXXX -Uuser -Tc /usr/tmp/share.tar /var/log* /usr/home* etc... This is taking too long for all of the servers. What is the exact syntax so I can backup changed/updated files in relation to the

Try adding these to your smb.conf after the 'set printing = bsd' and restart your daemons load printers = No disable spoolss = Yes show add printer wizard = No btw, be sure to remove the quotes from the lines (i.e. set "printing=bsd" should read: set printing = bsd not set "printing=bsd" (you probably knew that already) Are your Windows clients trying to print

Hi, As I recall, 3.0.25a creates it's OWN krb5.conf file based on info it gets back from the DC to try to handle site stuff (so it uses the 'nearest' kdc, etc). I forget exactly how this mech. works, but if the kdc returned with the site info (which subsequently gets built into samba's personal 'krb5.conf' file) is down, or replication is off, your kinit would work,

I have a simple peer to peer setup with security = user. I only have two machines, one Vista and one Linux. I have two shares, one is the tmp folder and I enabled public access, the other is a user owned folder with read, write and execute permissions. I can see my Samba shares from my Vista machine and I can access the tmp folder, but I can't log on to the user protected one. I have encrypted

On 10/15/2019 6:03 AM, Giulio via samba wrote: > On Mon, Oct 14, 2019 at 9:41 PM gw1500 via samba <samba at lists.samba.org> wrote: > >> Thanks. I tried the workaround but it was no help. I'm a little fuzzy on >> how to add a Windows user/pwd. I THINK I'm supposed to create the file: > I understand you want to access a windows printer from Linux, and you > are

Hello, I am working on RHEL4 update 5, using SAMBA 3.0.26a. I am trying to configure SAMBA as a domain member in a Win2K domain. I am using Kerberos authneticiaon (Security = ADS). I am getting an error when I am trying to join the domain (this is the output I get from running ?net ads join ?Uuser%password ?d10?: [2008/07/15 12:11:51.347873, 1, pid=5304]

On 10/14/2019 1:54 PM, Giulio via samba wrote: > On Mon, Oct 14, 2019 at 5:55 PM gw1500 via samba <samba at lists.samba.org> wrote: >> I am running CentOS 7 with Samba version 4.9.1. I have a Windows shared >> printer that I cannot set up but I am not sure if this is a CentOS issue >> smbclient -L dap001 -N >> Unable to initialize messaging context >>

A Redhat 6.0 linux server with Samba 2.0.6, Windows 95/98 clients. By accident I just discovered a surprising and quite disappointing password problem on our Samba network. If a user on our network has a non-empty Windows password, he is forced to supply his password to log in to the network and gain writing privilegies -- as expected. However, if the user has an empty Windows password, he is

Release Announcements ===================== This is the third release candidate of Samba 4.1. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.1 will be the next version of the Samba suite and includes all the technology found in both the Samba4

Release Announcements ===================== This is the third release candidate of Samba 4.1. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.1 will be the next version of the Samba suite and includes all the technology found in both the Samba4

Release Announcements ===================== This is the fourth release candidate of Samba 4.1. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.1 will be the next version of the Samba suite and includes all the technology found in both the Samba4

Release Announcements ===================== This is the fourth release candidate of Samba 4.1. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.1 will be the next version of the Samba suite and includes all the technology found in both the Samba4

================================================================== "Insanity: doing the same thing over and over again and expecting different results." Albert Einstein ================================================================== Release Announcements --------------------- This is is the first stable release of Samba 4.1. Samba 4.1 will be the next version

================================================================== "Insanity: doing the same thing over and over again and expecting different results." Albert Einstein ================================================================== Release Announcements --------------------- This is is the first stable release of Samba 4.1. Samba 4.1 will be the next version

================================================================== "Insanity: doing the same thing over and over again and expecting different results." Albert Einstein ================================================================== Release Announcements --------------------- This is is the first stable release of Samba 4.1. Samba 4.1 will be the next version

On 24.06.2019 8:21, Aki Tuomi wrote: > On 22.6.2019 22.00, Reio Remma via dovecot wrote: >> Hello! >> >> I finally took the time and spent two days to set up replication for >> my server and now I have a question or two. >> >> I initially set noreplicate userdb field to 1 for all but a test user, >> but I could still see in the logs that all mailboxes

hi all, I am experiencing an issue where a samba server is version 4.6.* and in smb.conf appears: unix charset = ISO-8859-15 if a client is version 4.5, no problem. If a client is version 4.6, smbclient fails: /opt/samba/bin/smbclient -Uuser%pass -L localhost -d10 [...] smb_signing_sign_pdu: sent SMB signature of [0000] 42 53 52 53 50 59 4C 20 BSRSPYL