similar to: Joining NT domain]

Hi, I am running samba-3.0.25rc3 in Tru64 5.1B. I compiled Samba source with --with-winbind switch. My goal of setting up Samba is to allow existing windows user login this Tru64 server without further asking password if they have alraedy logged in windows, yet with additional user control by adding a line "valid users = ..." in each directory section, that way Samba won't allow

I am sorry logs are bad formatted I am trying again and hope it will be better. Otherwise lokk at link bellow or tell me how to send logs correctly. Mirek 21.12.2018 v 13:19 Miroslav Geisselreiter: > Originally I posted this question at CentOS forum 20.12.2018. > https://www.centos.org/forums/viewtopic.php?f=48&t=69193 > > Hi all, > > I am not able to mount samba shares

Originally I posted this question at CentOS forum 20.12.2018. https://www.centos.org/forums/viewtopic.php?f=48&t=69193 Hi all, I am not able to mount samba shares after upgrading CentOS 7.5 to 7.6. I have been searching and trying to configure samba and winbind but no success. I find a lot of manuals and help pages about setting samba and winbind for machine acting as AD DC member but

Except that everything isn't fine, because I can't login to the samba domain as a PCNL/NT4 user or vice versa. -------- Forwarded Message -------- > From: Volker Lendecke <Volker.Lendecke@SerNet.DE> > Reply-To: Volker.Lendecke@SerNet.DE > To: Damian Lock (SSCI) <Damian.Lock@ssci.com> > Cc: samba@lists.samba.org > Subject: Re: [Samba] Samba 3.x and PCNetLink

Hi. We're trying to upgrade an old NT domain to AD. It's our second upgrade, and while the first was successfull this one has raised some issues for existing Windows 7 clients. If we disconnect the computer from the domain and join it back to the new S4 AD it works. Existing clients throws this error in Samba: Kerberos: AS-REQ b1rd42nbtmp648$@NT4DOMAIN from ipv4:10.0.0.42:49472 for krbt

Thank you Gordon for this tip but it does not solve my problem. From smb.conf: workgroup = NT4DOMAIN netbios name = NT4MEMBER I am able to connect to smb share from linux client: smbclient //NT4MEMBER/share1 -U NT4MEMBER\\user1 but from windows machine it is not possible. Correct command from linux client should be smbclient //NT4MEMBER/share1 -U NT4DOMAIN\\user1 (user is from NT4DOMAIN, not

# wbinfo --ping-dc checking the NETLOGON for domain[NT4DOMAIN] dc connection to "nt4member.intranet.xx" succeeded Here is debug log from winbind: [15833]: request interface version (version = 30) [15833]: request location of privileged pipe [15833]: request interface version (version = 30) [15833]: request misc info [15833]: request netbios name [15833]: request domain name [15833]:

Dne 5.1.2019 v 0:46 Gordon Messmer napsal(a): > On 1/3/19 11:46 PM, Miroslav Geisselreiter wrote: >> >> Previously I deleted all files from /var/lib/samba, than set ldap >> admin password: >> smbpasswd -W >> Than I re-join DC, it did not help. > > > Shame.? I'm not really sure what else to try, beyond my previous > suggestion that it doesn't

Hi everyone, I did a test migration from Samba3 to Samba4. So far everything works fine. Great work! Thanks to Samba team. I want to share my experience with you and look for your comments. My existing servers: 1. Samba 3.4.5(compiled) server: domain logon + file sharing + printer sharing ( 300 users + 200 win7) 2. 5 samba3 file servers(using the same ldap backend, so uid and gid are

Hi all, I'm trying to migrate NT PDC server to Samba PDC. and now i use samba 3.0.0beta2. I looks the migration steps from samba-howto-collection.pdf or in http://us2.samba.org/samba/ftp/cvs_current/docs/htmldocs/nt4migration.html, and it's not works well. The step is : ******** The approximate migration process is described below. " You will have an NT4 PDC that has the users,

I dowloaded from samba.org samba-3.0alpha24.. I refered http://samba.org/~jht/NT4migration/Samba-HOWTO-Collection.pdf chapter 31 it also mentioned in the how chapter 31 that it is a rough explanation but i decided to follow this and started doing things as i explaned below i looked google and samba mailing lists i did'nt see anything related to my problem anywhere Trying to Migrate from

Dne 4.1.2019 v 1:32 Gordon Messmer napsal(a): > On 1/3/19 6:09 AM, Miroslav Geisselreiter wrote: >> Yes, I add this host with command: >> net rpc join MEMBER -S NT4LIKEDOMAINSERVER -U root > > > I don't have any NT4-style domains handy to test with, so I can't be > very specific.? Your logs seem to indicate that Samba believes itself > to be the best DC for

Hello I am running a net work with a NT4PDC a NT4 BDC and attent to add samba BDC. I am following the brief section 28 of the Samba-Howto collection for samba head/3.0. * Adding the samba server as a BDC from NT server manager seems OK * Getting, recording domain sid is ok (see below) > rpcclient NT4PDC -U Administrator password: > lsaquery domain IMAGERIE has sid blablabla > net

Hello all, I've got a weird problem with a fresh install of Samba from the FreeBSD ports collection (btw. the BSD-box is also a fresh 4.7 Stable install). Configured Samba 2.2.7a - without cups - with winbind - with winbind-auth - with audit so far, the installation seemed to work fine... Then I copied the libnss_winbind.so to /usr/lib and softlinked it to /usr/local/lib as well as to the

On 12/31/18 12:03 AM, Miroslav Geisselreiter wrote: > > This command is not working after upgrade. Logs say something about > crap domain: > set_dc_type_and_flags_connect: DC for domain NT4DOMAIN claimed it was > a DC for domain NT4MEMBER, refusing to initialize What do you get from "wbinfo --ping-dc"?

On 1/1/19 12:21 AM, Miroslav Geisselreiter wrote: > # wbinfo --ping-dc > checking the NETLOGON for domain[NT4DOMAIN] dc connection to > "nt4member.intranet.xx" succeeded Well, the host where you ran that command thinks that "nt4member" is the DC.? Do you see anything in your configuration file that might indicate why?? You haven't given us enough information

I am running samba 3.0.4 using ldap and I am having a wierd problem. I am trying to setup a one way trust with an NT4 PDC. The NT4 PDC is the trusted domain and the samba pdc is the trusting. I setup the password on the nt4 machine in the trusting field. When I go to the samba pdc and type in "net rpc trustdom establish NT4PDC" it prompts for the password. After I type it in it

Hi, I am trying a test of migrating a NT4 Domain to Samba 3 Beta 3 configured to use LDAP on Redhat 8. Is this possible? Details ------- I previously had Beta 2 on LDAP running as it's own domain controller without problem and could create users (in LDAP) with smbpasswd -a. XP clients could join and login OK. Now I have flushed that setup and have loaded Beta 3 configured to use LDAP,

I am trying to establish a domain trust between a Samba 3.024 domain and a PC Netlink 2.0 domain. Currently, we are using PC Netlink as our primary Windows file server and "NT4" domain controller. (Lets say that the domain is called LEGACY and the domain controller LX1) Windows 2003 servers are unable to join a PC Netlink domain (even with the SignOrSeal option disabled.) For

I am running a samba pdc on host "debianpdc" for domain "linuxdom" and have set "allow trusted domains = yes" in my [global] smb.conf file... now how do I specify which domains to trust? I would like to trust an NT4 domain "nt4dom" run by the host "nt4pdc" on the same network.