similar to: NT_STATUS_LOGON_FAILURE

Greetings, Do you guys know what normally causes this? - Google has a lot of instances of the issue but no resolutions. I'm running FBSD 5.4 with the latest samba. Here's the command and the associated error: insomniac# cupsaddsmb -U root -a -v Password for root required to access 10.0.0.1 via SAMBA: Running command: rpcclient 10.0.0.1 -N -U'root%password' -c 'setdriver

how about redirecting the smbpasswd file to the older version (assuming you have one) using smbpasswd file = /file/path/smbpasswd , I replaced my copy of smbpasswd for 3.09 with a 2.216 and the smbpasswd command stopped working, (no new entry added to the smbpasswd file), but when i used that it worked again "Izo" <I@siol.net> wrote in message news:41B8004E.8050807@siol.net...

Trying to log into my samba server for the first time and I get this failure: [janos@cherubino ~]$ smbclient -L cherubino -d 3 lp_load: refreshing parameters Initialising global parameters params.c:pm_process() - Processing configuration file "/usr/local/etc/smb.conf" Processing section "[global]" added interface ip=10.61.70.2 bcast=10.61.70.255 nmask=255.255.255.0 added

I just hope that this time I get heard since obviously nobody reads news://linux.samba ... Platform: SuSE-9.1, kernel-2.6.5, samba-3.0.4 I have recently upgraded from 3.0.2a to 3.0.4 and I have just noticed that using the same smb.conf as with previous version, the system just does not work anymore for me ! Furthermore, smbpasswd utility appears to be dropped ! Afterwards, I have noticed

Hello, all. I'm running into an issue connecting from my PowerMac G4 running Yellow Dog 4.0.1 to our server, which is a dual AMD running Fedora Core 2. The server is running samba version 3.0.10-1.fc2, and the g4 is running samba version 3.0.10-1.ydl.1. I can connect from the g4 anonymously to a share point on localhost: smbclient //localhost/dathan I can connect from the server to the

hi to everyone, my name is Daniel and I'm currently trying to upload the driver for a printer in a company's network. The printer in question is a Kyocera Mita FS-C5016N, but actually that's not my problem. My problem is that I'm not able to execute RPC calls on my laptop,. I've successfully added the PostScript driver (with cupsaddsmb) to the Samba share "print$",

When I try to connect to a NT share I get this: 19788: session setup failed: ERRDOS - ERRnoaccess (Access denied.) SMB connection failed My command is: mount -t smbfs -o username=xxx,password=xxx //DBSERVER/myshare$ /tmp/backup The above command works on other machines. Please help. Here is my debug info: INFO: Current debug levels: all: True/10 tdb: False/0 printdrivers: False/0

Hello, I am trying to set up samba on this host and testing it locally is giving me headaches right away. tom at hversa:~:~$ smbclient -L localhost -U% Domain=[WORKGROUP] OS=[Unix] Server=[Samba 3.4.8] Sharename Type Comment --------- ---- ------- homes Disk Home Directories print$ Disk Printer Drivers

On 04/10/15 17:43, Norberto Bensa wrote: > Hello, > > I've followed two or three articles on how to configure samba 4 as a > member server. One of these articles is from the samba wiki: > https://wiki.samba.org/index.php/Setup_a_Samba_AD_Member_Server > > The server joins, but it cannot authenticate users. I don't care about > nss, winbind, etc. unless it is REALLY

I'm trying to set up our test box here. Identical versions and setup to our devel box. It is part of the domain (has already been joined). And there was a problem with the secrets.tdb file (corrupted or whatever). winbindd.log: --- [2004/10/20 08:33:46, 1] nsswitch/winbindd_util.c:add_trusted_domain(166) Added domain XXXXXXXX XXXXXXXXX S-1-5-21-1645522239-1202660629-725345543

I recently upgraded my PDC's and BDC's to 3.0.14a but my member servers are still running 3.0.10. Today users complained that the couldn't logon to the member server. When I try to run a wbinfo -u I get: Error looking up domain users Here's the log.windbindd: 2005/05/31 11:06:26, 4] param/loadparm.c:lp_load(3933) pm_process() returned Yes [2005/05/31 11:06:26, 3]

Nope. Do I need to? For now I only want to authenticate Windows boxes. *nix boxes later. Thanks. 2015-10-04 14:11 GMT-03:00 Rowland Penny <rowlandpenny241155 at gmail.com>: > On 04/10/15 17:43, Norberto Bensa wrote: >> >> Hello, >> >> I've followed two or three articles on how to configure samba 4 as a >> member server. One of these articles is from

Since upgrading from CentOS 4.3 to CentOS 5 the smbclient tar commands seem to be broken. The version on 4.3 was 3.0.10 I believe, while on 5 it is 3.0.23c-2. Here's what happens. Running the command: $ /usr/bin/smbclient \\\\host.domain.com\\backup -A /tmp/ntcredentials works fine. It connects no problem. But: $ /usr/bin/smbclient \\\\host.domain.com\\backup -A /tmp/ntcredentials -Tc

Hello, I've followed two or three articles on how to configure samba 4 as a member server. One of these articles is from the samba wiki: https://wiki.samba.org/index.php/Setup_a_Samba_AD_Member_Server The server joins, but it cannot authenticate users. I don't care about nss, winbind, etc. unless it is REALLY necessary. All I want is to use this server as a file server for workstations

Hi all, this is probably VFAQ, but I never found a working solution. I have a standalone samba server running samba ver. 3. In the network, we have heimdal kerberos used to authenticate users for pop3,imap,web-based applications etc. Now I would like to make the samba communicating with kerberos kdc so there will no longer be users in smbpasswd with separate passwords outside of kerberos. I

I've tried everything I can think of, but still cannot connect to a Windows 2000 share using smbclient. I know the shared directory is set up OK because I can get to it with another Windows box. My smbclient command line should be OK because the same syntax works on another Linux box at work (running a slightly older version of smbclient) to a similarly setup Windows box. This is what I get

I'm a Samba-3 newbie (all my previous experience is with Samba-2), and that may by the crux of the problem. Samba 3.0.14a-2 came bundled with Fedora Core. Since this server will be taking over the functions of the Samba-2, I copied the smb.conf file over and simply changed the netbios name. It uses a domain security model, and that has not changed. Also, using the rpc net command, I

Hi everyone, this one is giving me headaches for a while now and I could not get anything useful from the usual sources. So maybe someone on this list can give me any ideas: There is a samba server Version 3.0.22 on Ubuntu Dapper see below for configuration details) and it is configured to authenticate against a Windows 2000 Server Ver. 5.0.2.195 preped for ADS 2003 and

Hi all! I have a problem setting ACLs on a remote file on a Windows XP Pro SP2 box. I issue the following command: smbcacls -a 'ACL:BBI-DEV\beakid:ALLOWED/0/0x00100116' -U 'BBI-DEV \Admin' //BBI-DEV/Data /Niva.txt And I get this response from debug level 3. Password: Connecting to host=BBI-DEV Connecting to 192.168.1.124 at port 445 Doing spnego session setup (blob

Hi all! I have a problem setting ACLs on a remote file on a Windows XP Pro SP2 box. I issue the following command: smbcacls -a 'ACL:BBI-DEV\beakid:ALLOWED/0/0x00100116' -U 'BBI-DEV \Admin' //BBI-DEV/Data /Niva.txt And I get this response from debug level 3. Password: Connecting to host=BBI-DEV Connecting to 192.168.1.124 at port 445 Doing spnego session setup (blob