similar to: winbind 3.0.28a not working with nt4 -> windows 2003 trust domain

I have a test environment running Fedora 8 and Samba 3.0.28a on two PDC's and one Domain Member. I have a DOM-A PDC with a ldap backend, running winbind. I have a DOM-B PDC with a ldap backend, running winbind. The two domains have trusts both ways. I also have a domain member called TESTSERVER joined to the DOM-A domain, running winbind. I was running 3.0.28 on TESTSERVER and I could do

I'm starting to see some really weird things happen on a range of Samba-3.0.28a servers installed as "security=ADS" members of a variety of domains. This was working last time I checked (weeks ago), but something's happened. Windows Updates tend to spring to mind more than Samba upgrades as a cause... On all of them, "wbinfo -t" is happy, "net ads

Hello, My name is Shane Drinkwater. If I use Samba 3.0.29/3.0.30 I cannot join to= my NT4 Domain. When running the net command to join I get the following er= ror. [root@testbackup bin]# ./net rpc join -Scsqdomainbackup -UAdministrator Password: [2008/06/05 16:40:35, 0] utils/net_rpc_join.c:net_rpc_join_newstyle(371) Error in domain join verification (credential setup failed): NT_STATUS_AC=

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

My Question: ------------ Is it possible to get 2-way Interdomain Trust relationships working between a Samba domain and an NT4 SP6a domain, while restricting all password hashes to NTLMv2 only? Everything works except the inter-domain trust I'm able to get the NT4 domain to trust the Samba domain, but not the other way around. My System: ---------- I have a perfectly running Samba domain

Hi all, Set-up: Local NT4-RESOURCE domain which the Samba server is a member off. One NT4-ADMIN domain with users accounts and one W2K domain with some other user accounts. A one way trust from NT4-ADMIN to NT4-RESOURCE and a one way trust from W2K to NT4-RESOURCE. Samba version 2.0.7 running on Solaris 2.6. According to the NT admins, the W2K domain is in native mode, but they still use

Hello all, We have Samba (2.2.5) running on three servers, each in a different subnet. One of them is a PDC (domain master = yes). The Samba PDC is also the NIS master. The smbpasswd is replicated using rsync to the other machines that act as Samba BDCs (domain master = no). They are also NIS slave servers. The smbpasswd synchronization takes place automatically every time smbpasswd is updated,

On 31/10/2019 21:58, Vex Mage wrote: > > > > Have you tried 'net rpc trust create'? ? > > See 'net help rpc trust create' for the syntax. > > > When I attempt this I get the following error message > > SAMBAPDC ~# net rpc trust create > otherserver=sambaad.engineering.college.edu > <http://sambaad.engineering.college.edu>

Hello folks, It seems that I am still having the trust issues I encountered with 3.0.28a with 3.0.30. My production servers are running 3.0.28 and that is working very well. Thanks in advance for any help or advice. - Franz Basic setup: Win NT4 PDC domain trusts an AD-mixed mode accounts domain Samba server member of NT4 domain and running winbind for auth When I call id <username> I

Hi, I've noticed a discrepancy between Samba Version 3.0.28a and Version 3.0.24 in relation to Winbind rid idmap and trusted domains behaviour. I have an environment with 2 domains linked via a trust, an Active Directory domain and an NT4 domain. On 3.0.24 the rid backend seems to work fine, but on 3.0.28a it shows OTHERDOMAIN\domain admins instead of the primary domain's domain

If you wanted to follow my steps for setting up a samba PDC in a trusted domain with NT4, please note that there are some corrections. I had a second person follow my steps and we found some problems. First, the link I originally posted as incomplete. It needs a slash at the end. The correct link is: http://www.hilinski.net/samba/ The doc file posted there was corrected today, 11/26/2003 at

Hello! I'm trying to create a two way trust between a Samba DC and a Samba NT4 domain both are 4.10.9. The issue I'm seeing is that while I can establish a one way trust from the NT4 PDC to the DC using the following commands; net rpc trustdom add sambaad thepassword net rpc trustdom establish sambaad I enter the password for PDC$ and the trust is established. When I go into Domains and

Hi I'm trying to set up samba 3.0.9 as domain member server. When I try to join NT4 domain using "net rpc join" it added an account in NT4 domain but in lowercase !! I have to delete it on nt4 and add it again using uppercase letters - then it works. Why?? In smb.conf I have netbios name written in uppercase. I've even tried net -n !! Another problem is that when I try to join

Hello! It seems, that Vista SP1 and Server 2008 cannot join an NT4/Samba-domain. Vista once could join before SP1, if one did some modifications to the system (LAN Manager authentication level, Encryption of secure channel). But these workarounds do not seem to work with SP1 anymore. Microsoft points out that joining NT4-domains with Vista SP1 and Server 2008 is not supported/tested

If I use any of the binary packages for SuSE SLES9 greater than 3.0.7 I can not see some of my NT4 trust domain via winbind. We have 5 regular NT 4 domains that trust each other. Two of them our within our LAN (local subnet), one of these domains the samba machine is within ... security = domain. There's another 5 domains that are setup for our AD enviroment for exchange, mixed mode. Using

greetings folks, i just upgraded to 3.0.28a on a secondary server (not live) and am now unable to connect to my trusted domain. here's the setup: NT4 PDC/BDC for my domain my domain trusts a central domain for the accounts the central domain is running AD in mixed mode my samba servers are members of my domain and use winbind after getting my daemons running, i check with winbind. -

Background: We are migrating from our NT4 domain, to a new Windows2003 Active Directory domain, so our Linux samba server is joined the the NT4 domain where most the users live. But we are now starting to migrate (Using MS built in Migration tool) users from the NT4 domain to the Active Directory. Once the users are migrated they are not able to access shares on samba 3 file server The samba 3

Hi, I want to connect in NT4 PDC domain with my linux box using samba + winbind. I try to connect with Active Directory and it works fine !! Why i can't do the same thing with NT Domain. I've an error 5722 in NT computer like this: The session setup from the computer WORKSTATION NAME failed to authenticate. The name of the account referenced in the security database is WORKSTATION

I presently have a Samba server (3.0.21b) set up as a member server in an NT4 domain (with a real Windows NT4 PDC). We are migrating to an Active Directory domain (with a real Windows 2003 domain controller). We have set up a two-way trust between the old NT4 domain "CLUNKY" and the new ADS domain "SLEEK" (aka sleek.local). The Samba server is a member of the CLUNKY domain

Here's the situation. We've got an old NT4 domain (not a Samba domain in NT 4 mode) which we'll call CRUSTY. There is of course an NT4 PDC and several NT4 BDCs. We have some Linux/Samba file servers (Samba 3.0.1) that are member servers (security = domain) of the NT4 domain. We also have several NT4 BDCs and about 200 workstations of varying vintage (2000, XP) in several