similar to: Unable to authenticate against an OS/2 PDC

Okay, I've had some fun there. Let me tell I am no samba pro, so the patch below _should be tested and tested again_ in _your_ environment before doing anything close to putting your patched samba into production. It can possibly break everything. You have been warned. The mail is somehow longish, because sending a quick (and dirty) patch without any explanation seems wrong to me. And

I am trying to get 'net password ...' to work from an OS/2 client to a Samba 3.1.15 server. However, I get an Invalid Password error whenever I run net password. I am certain that I am providing the correct password. With DEBUG_PASSWORD on in the build and tracing set to 100 I ran 'net view \\server' which authenticates correctly and I ran 'net password user oldpass

> nslookup -type=SRV _kerberos._tcp.mycorp.com > > ** server can't find _kerberos._tcp.mycorp.com: NXDOMAIN > As 'hostname -d' is returning 'mycorp.com' it would seem that is the dns domain your computer is in. 'mycorp.com' != 'wgname.ad.mycorp.com' (which appears to be the dns domain of your DC) and Samba does not do subdomains or to put it

I'm running a debug script from this site (Dated 16 Aug 2019, created and maintained by Rowland Penny and Louis van Belle). The script obtains the Linux server DOMAIN by running "hostname -d" which returns "mycorp.com". Next the script runs nslookup -type=SRV _kerberos._tcp.mycorp.com which fails ** server can't find _kerberos._tcp.mycorp.com: NXDOMAIN and the

I got a spam today (from a yahoo server, surprise!) with nothing but a single link. http:// 2927755261/ I separated the http so it would not be a link in your email... suggest not going to it without proper measures. it takes you to a record search site. When I look up this number block here, http://www.ip-adress.com/ip_tracer/2927755261 it comes up with a different ip address... The ip

Hello there, From digging the archive - it looks as if this was discussed here earlier however I could not find a decent solution to my problem. The problem is that I keep seeing the following errors on my nmbd.log: [2003/01/30 09:34:34, 0] nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(358) find_domain_master_name_query_fail: Unable to find the Domain Master Browser name

Hi, I'm trying to setup automatic sync of files over SSH from node2 to node1. node2 is the "server" and node1 is the "client". I have setup rsync like this on the nodes which runs AIX (4.3.3 and 5.1): 1. Installed rsync from Linux Toolbox (rsync-2.5.4-1.aix4.3.ppc.rpm) on both nodes. 2. Added following to both nodes /etc/services file: rsync 873/tcp 3. Added

On 13/10/2017 08:03, Damien Miller wrote: > On Thu, 12 Oct 2017, Michael Felt wrote: > >> On 08/10/2017 23:32, Michael Felt wrote: >>> On 04/10/2017 11:07, Michael Felt wrote: >>>> I do not often use X11 - but when I do I prefer to enable >>>> X11forwarding, and when finished - turn it off. This is preferable, >>>> imho, to having

A few times in the last couple months we have had our production Samba 3.0.14a-1server crash. We did not have detailed logging turned on at the time so the attached output of our log is the best process tracking I can give at the time of the crash. What will happen is our shares will no longer be accessible, and all the smbd processes will be hung. We can ssh to the server and do a restart

Hi all, I encounter a problem when I try to connect a Samba3 server as a BDC on a ASU HP/9000 PDC server. We manage to start the communication between both computers, but it doesn't achieve it. It failed when trying to bind to PIPE\lsarpc. Can anyone give some help please ? Let's note that I can get the SID from net getlocalsid command, and that I can list all share with administrator

Hi Henrik, Am 18.03.2017 um 16:06 schrieb Henrik Johansson via samba: > Old version was 3.5.8 and the new version on the virtual host that does not work is 3.6.25. That's not really a step forward to a supported Samba version. :-) https://wiki.samba.org/index.php/Samba_Release_Planning > # Global parameters > [global] > log file = /var/samba/log/clientlog.%m >

I'm having an issue establishing a trust between a samba/ldap PDC and a windows 2003 Active directory server on a seperate domain. Here is what I've done. I've created a 2 way trust in windows with the samba domain. When I try to verify the outgoing trust from windows I get an access denied message. In samba logs I get " get_md4pw: Workstation CATS$: no account in domain"

Hi, I have setup Samba 3.0(as PDC) with LDAP as the backend. The samba parts(login and share etc.) is now working after some tweaks. The pam_winbind also work as I can authenticate agains winbind. However, the libnss_windbind doesn't work which I have no clue where should I look into trouble. getent passwd or getent group shows none of the samba entries I created. I tried to turn on log to

Hi, I have a problem establishing a interdomain trust to Win2003 SP1 where the Windows domain is the trusted domain. The other direction, the samba domain is trusted by the windows domain, works without problem. When I try to establish the trust from the samba side, I get the following error: # net rpc trustdom establish T18 Could not connect to server JPTEST121 [2005/06/22 11:41:35, 0,

Hi, Samba 3.0.14a Im trying to get Samba to trust a Windows 2003 domain. I have read the samba docs and it wont work es expected.... I have looked through mailing lists and nobody seems to have an answer. Ok so i have created a Two way trust on my Windows Server, then on samba i try to establish a trust but i get an error? Server1:/usr/local/uni-staff/bin # ./net rpc trustdom establish uos

Greetings, I've been having some issues establishing a two way interdomain trust between a samba server and an win2k8 active directory server. I've established a trust password and object and was able to create a trust relationship from the AD server to the samba server but I'm unable to from the Samba server to the AD server. The purpose of this is to enable ADMT to migrate the user

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello All, I'm having an issue creating a two-way trust relationship between my Samba Domain and a Windows 2003 Active Directory Domain. Here is a summary of my environment: Samba 3.0.14a OpenLDAP 2.0.23-7 Debian Woody Active Directory 2003 (running in mixed mode) Windows 2003 The trust works fine from AD -> Samba: [root@samba-1 root]$

I have samba 3 PDC (SAMBA domain with hostname "pevpdc") on CentOS 3.7 (package is named samba-3.0.9-1.3E.7) and I have a w2k3 sp1 domain (W2003 domain with hostname "mailserver"). The last is in mixed mode and is an exchange server and the former is without winbind, using smbpasswd backend and "security = user" in smb.conf. I would like to authenticate mailserver

Folks, Not even a peep. Did I ask the wrong question or am I on the wrong list? I don't mind pointers to more information.... I own both the recent books on Samba 3 and they are very good, but I seem to be missing something. Anyways... Thanks and hope to hear from you soon, Michael J Barber WPTZ/WNNE Computer Services Administrator p 518-561-5555 x563 m 518-572-6639 f 518-561-5940

On Sat, 18 Mar 2017 17:26:11 +0100 Marc Muehlfeld via samba <samba at lists.samba.org> wrote: > Hi Henrik, > > Am 18.03.2017 um 16:06 schrieb Henrik Johansson via samba: > > Old version was 3.5.8 and the new version on the virtual host that > > does not work is 3.6.25. > > That's not really a step forward to a supported Samba version. :-) >