similar to: NT PDC and SAMBA file server

Greetings: I'm having a couple of problems that I can't seem to resolve (even after searching the Samba archives). 1) When selecting "Shared Directories" from within NT Server Manager, I get the following error: "The Remote Procedure Call Failed" 2) When setting the scope to \\servername with "User Manager for Domains," the scope gets set to domain (the

Dear all, I'm trying to set up Samba as a PDC, and try as I might I can't get that magical "Welcome to the DOMAIN domain" message. V. frustrating! I'm running 2.0.3. I've run through all the DIAGNOSE.txt messages without problems and can access all the shares fine. I've set everything up as in the NT domain FAQ, but still I can't get my box to be part of that

I have been working on loggin onto my linux server from my win2K box and get this error in the log.smb file passdb/smbpassfile.c:trust_password_lock(119) trust_password_lock: cannot open file /etc/NEFF.LINUX.mac - Error was no such file or directory passdb/smbpasssfile.c:trust_get_passwd(288) domain_client_validate: unable to open the machine account password file for machine LINUX in domain Neff

Hi! We're using Samba as PDC, and recently had a strange crash on the system (none of the NT-machines authenticated anymore). I re-created the user database and passwords on the server (TurboLinux 2.2.14-5, with Samba 2.0.6 & 2.1alpha for auth.) and also re-newed the profiles making 'em local on the NT-workstations. Sometimes when the NT-PC gets rebooted, I can't authenticate it

I was looking through my logs this morning and noticed this error. Looks like it's been happening quite a bit on my home network of win 98 boxes. I looked through some of the last months' archives but didn't see anything... apologies in advance if i missed it.... here are the errors: [2000/12/30 15:54:28, 0] passdb/smbpassfile.c:get_trust_account_password(202)

i changed ip to my server and then i cant connect anymore using _NT authentication this the error i got from the log file: [root@server samba]# tail -f log.luca [1999/08/27 19:07:05, 0] passdb/smbpassfile.c:trust_get_passwd(294) domain_client_validate: unable to read the machine account password for machine SERVER in domain SATORI. [1999/08/27 19:07:05, 1] smbd/password.c:pass_check_smb(528)

Sorry to be posting another question, but my learning curve is starting to flatten some now. What am I missing here? > temp _ name[reis==toupper(location[order(Vgrablow2)][N])] > temp [1] "Lawton" > paste(temp,g) [1] "Lawton" # WHERE IS THE SECOND ELEMENT? > g [1] 0.29 > a _ "Lawton" > paste(a,g) [1] "Lawton 0.29"

Using Samba v2.0.10 on a RedHat v7.1 box, I see that the Win98 clients on our network are making sporatic requests for user "nobody" (as shown below). Anyone know what's going on here? My network has both Linux and Win98 clients, but only the Win98 clients are showing this behavior. Both the Linux and Win98 clients access the same shared drives, but only the Win98 clients use

Hello everyone, we try to use a server running linux in an NT-domain and get the error message given in the subject-line. More details from the logfile and smb.conf are given below. Can anyone give us a hint what the problem is? (Of course...) The problem is very urgent for us. Thanks a lot in advance. Helmut Rickel ================= smb.conf ======================== [global]

Thanks to all that replied : Gerald W. Carter, Levent ... Actually, I'd already done what had been suggested ... socket address = 10.10.10.5 interfaces = 10.10.10.5/24 It appears to working now... I think my problems were two-fold : 1. I made separate locks directories : /var/samba1/locks /var/samba2/locks and specified them in the smb1.conf & smb2.conf

This is the list of problems I had with samba-2.0.6 so far. Can anyone tell me if he can reproduce them and if he considers them as problems? 2.0.6 on linux 2.2.13 or 2.0.33 1) sighup/log reopening doesn't always work: connections that are already active keep logging to the old logs; logrotate rotates/zip the logs and samba stops logging completely till restart. 2) Localized chars. I have

We are seeing erratic behaviour from Samba for connecting Unix drives to an NT terminal Server. Samba version 2.0.6 Solaris 2.6 NT Server 4.0 Terminal Server Edition with service pack 4 running WinCenter NIS Logon Utility. The NT server is not part of a domain and uses the WinCenter Logon Utility to authenticate username and passwords from my Unix NIS server. Samba is set up for server level

Hello, I'm having a problem configuring samba (2.0.5a) on a Linux system using NIS+ as the password system. Samba complains that it cannot find the smbpasswd file, which is not surprising as I'm not using one. I tried 'smb password file = passwd.org_dir' that sort of worked, except that it creates a directory called passwd.org_dir from whatever directory I ran the smbd from.

The problem: Strangely, the PDC rejects user password challenges from Samba. The user account gets locked. After unlocking the account, everything is back to normal. This happens several times a day to different users and from different Samba servers. All Samba servers have the same [global] configuration. Is this a Samba problem? Is samba perhaps not passing along the correct password? If I add

Hi, Recently i moved from samba 2.0.5a to Samba 2.0.6 on 4 machines. Samba 2.0.5a ran quite smooth except for oplocking problems, so i decided to upgrade. I compiled both releases myself and used the same ./configure options both times (but i compiled on different machines: v 2.0.5a was compiled on a HP 9000/715/50, 2.0.6 was compiled on a HP 9000/800/K360) I used binutils 2.9.1 and gcc 2.8.1 on

I have been running RedHat 5.2 and Samba 2.0.3 for the past week or so. My network is made up of NT servers and 95/98 clients. So far Samba has been running beautifully - I can use my Samba shares just like they are NT shares. My only problem is from time to time my Win98 machine "goes to sleep" and asks me for either a password or an IPC$ password. Generally this happens after a

Paul Whittaker <paul.whittaker <at> drisq.com> writes: > > > Hi Arnaud, > Great to hear this is an isolated case; hopefully it means we've > found a bug we can help solve. > On 27/11/12 22:50, Arnaud Quette wrote:please send the log here, in compressed form. > are the photos taken with a still cam? > please put

/var/log/maillog showed this Oct 19 13:25:41 ns1 postfix/smtpd[1298]: 7599A2C19C6: client=unknown[127.0.0.1] Oct 19 13:25:41 ns1 postfix/cleanup[1085]: 7599A2C19C6: message-id=<edc55a9b-eb49-3945-dc60-0e1d51a78e97 at nbmlaw.co.uk> Oct 19 13:25:41 ns1 postfix/qmgr[1059]: 7599A2C19C6: from=<matthew.broadhead at nbmlaw.co.uk>, size=3190, nrcpt=1 (queue active) Oct 19 13:25:41 ns1

Op 10/20/2016 om 7:38 PM schreef Matthew Broadhead: > do i need to provide more information? > It still doesn't make sense to me. I do notice that the version you're using is ancient (dated 26-09-2013), which may well the problem. Do have the ability to upgrade? Regards, Stephan. > On 19/10/2016 14:49, Matthew Broadhead wrote: >> /var/log/maillog showed this >>

are there any instructions or tests i can make to check the sieve configuration? or does the magic all happen internally and there are no settings to change? On 21/10/2016 10:22, Matthew Broadhead wrote: > the server is using CentOS 7 and that is the package that comes > through yum. everything is up to date. i am hesitant to install a > new package manually as that could cause