similar to: Authenticating a user in a Windows 2000 domain

Hi, I'm just using samba for few weeks and i'm triing to migrate all NT4 SAM base to Samba Linux. I'm working with Red Hat enterprise Linux ES 4.0 updated, openldap 2.2.13-4, samba samba-3.0.10-1.4E.2 and i've followed IDEALX migration procedure with smbldap-tools-0.9.3-1. Every configuration seems to be clean but not ;o))))) I'm using cleartext password in slapd.conf and

[I saw this question once in the list archives, but no answer, so I'll repeat as it is my current problem.] Samba version 2.0.7, Solaris 8 Solaris box is a member of domain A. Domain A's PDC trusts domains B and C, can authenticate passwords of users in those domains. Domain B has an NT4 PDC. Domain C has a Win2000 PDC. Password authentication works on the Solaris box for domain B

When I attempt to authenticate a user from another domain, I am seeing some strange issues. My winbindd.log shows that I am indeed already trusting the other domain. (I am a member of the na.uis.unisys.com domain.) However, when I try to gain access to a share where the username EU\INBLR-AUTH1 has access, I get prompted for a username and password over and over. Obviously, it can't

Ok try set the profiles folder on 777 And add : valid users = %u @"Domain Administrators" greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens Jim Seymour > Verzonden: dinsdag 26 juli 2016 16:32 > Aan: samba at lists.samba.org > Onderwerp: [Samba] NT4-Style Auth & Roaming Profiles Only? > > Hi

Samba Version: 3.0.0 Linux Version: Redhat 8 Kernel: 2.4.18-19.8.0smp Kerberos: Mit 1.3.1 Windows Version: 2003 running in mixed mode (though we will be switching to native mode soon) The system was initially set up to hit the NT4 Domain and was authenticating to the domain. The NT 4 domain was upgraded to 2003 running in mixed mode. The Samba server could still authenticate to the domain with

Hi folks, Can anyone shed light on this issue? I haven't heard from you guys. Is there anything else I could do to expedite resolution of this issue? I've read the WHATSNEW.txt and reviewed the release notes. I am not sure if I've fully grasped what needs to be done. Can someone point me in the right direction? ~Doug -----Original Message----- From: Doug Sampson

Since version 3.0.23b, I have been having trouble getting Windows & OSX users to access an NT domain member server running FreeBSD 5.4. It is now at 3.0.23c (installed this morning the 5th). root@aries:/usr/local/lib# net rpc user Password: Could not connect to server 127.0.0.1 Connection failed: NT_STATUS_NO_LOGON_SERVERS root@aries:/usr/local/lib# net rpc user Password: Could not connect

On Tue, 26 Jul 2016 13:40:59 -0500 Dale Schroeder <dale at BriannasSaladDressing.com> wrote: [snip] > > Sorry Rowland, but the break happened before the badlock patches when > Debian jumped from 4.1.x to 4.3.x, skipping 4.2.x altogether. [snip] > > Jim, currently at Debian 4.4.5. If you search this list, you will > find others who have had the same thing happen. To my

I've got a samba 3 ads domain member server that is not able to authenticate users in trusted domains of the ADS domain of which it is a member. Windows 2000 ADS PDC A trusts a Windows NT-4 domain B and a Windows 2000 ADS domain C Solaris 9 Samba 3.0.6 member server of ADS domain A If I use getent passwd on the Solaris 9 server, I get all the users in Domain A and B , but no in Domain C,

Hi There, Tried a Samba AD. Didn't work out. Please do not suggest. Thanks! Here's what we have: Ubuntu Linux 14.04.4 LTS Samba 4.3.9-Ubuntu Using OpenLDAP for authentication Using nscd to speed things up *Not* running winbind *Not* running Kerberos The problem is the company purchased a product that, *despite* the vendor being told "We don't have

"Gerald (Jerry) Carter" <jerry@samba.org> wrote in message news:<zwyd.1Tn.5@gated-at.bofh.it>... > The Samba Team is proud to announce the availability of the > first official release of the Samba 3.0 code base. > > Major new features: > - ------------------- > > 1) Active Directory support. Samba 3.0 is now able to > join a ADS realm as a

On Tue, 26 Jul 2016 12:37:51 -0500 Dale Schroeder <dale at BriannasSaladDressing.com> wrote: [snip] > > Jim, > > This may be your problem: Samba 4.3.9 > > Upgrading my NT4 domain from 4.2.x to 4.3.x and beyond broke it, and > no combination of configuration parameters could put it back together > again. > > I wish you better luck. Yikes! Thanks for

Hi, I have recently installed samba 3.0.14a on an AIX 5.2.0.6 server. I have joined the AIX server to a NT4 domain called ESC. When I do a wbinfo -u I get the users of the domain. I then setup a share "psoft" that I want to be "read only" to everybody but 5 users. Those 5 users I've added to the "write list" of that share. I also setup the "force

I read everywhere about migrating an NT4 domain, but nowhere says you can do the same with a Windows 2000 (NOT mixed mode) domain... This client does NOT currently use AD for anything special (GPO, etc). Is this possible? Advised? -- Best regards, Charles

We have a samba 3.0.7 server on RHEL-3 (rain) joined as a domain member (security = domain) to a win2k pdc (clouds) for the domain DOM. We have several unix users and two Win-only users. The unix users have matching AD accounts on the win2k, but the Win-only users do not have unix accounts (and we want to keep it that way). So, it seemed that winbind would be the best way to bridge the gap: 1.

Hi Jonathan, Yep, samba sends the domain name as well as the username to the domain controller, and what I think happens is the NT controller sees that the domainname passed is NOT his domain, checks his list of trusted domains, doesn't find it, and says sayonara buddy... I am assuming that 'SATURN' is the netbios name of the win2k client machine? I'm not real clear on how this

Hello, I've got a linux box running smbd & nmbd versions 2.0.6 with security = DOMAIN, and an NT4 box as the password server. The sole domain controlled by that NT4 box is named "MSOE". All is well with win98 clients. However, Win2k clients that are not part of an NT domain, but simply belong to a "workgroup" named "MSOE", are unable to authenticate. The

Mathias, What you say is true in theory, but after Debian went from 4.1 to 4.3, my NT4 domain no longer works. The initial error was no logon server available. I've asked if anyone has a working NT4 domain on 4.3, and no one has replied that they do; therefore, I assume that there are none. Additionally, there were specific changes indicated for NT4 domains in the 4.2 release notes,

Hi, I'm trying to build a samba server that shall substitue one of our NT4 servers but I'm having some problems with setting up the local user account: The NT4 server was member of a ressource domain (R1) and also had a local user account named "bcd" which is needed for a boot-cd. Normal users authenticated through the master domains M1 and M2 which has all the necessary trusts

Hi all, I have had the unfortunate joy of upgrading my PDC to Windows Server 2003 and active directory, I also upgraded to samba 3.0.0 on a debian testing box. Before I was running a happy little environment with Windows NT4 and Samba 2.2.8 with winbind using the "winbind use default domain = yes". Migration went smooth, switch to security = ADS and joined the directory. Everything was