similar to: Re: Samba 3.0.29 -> 3.0.30 Trust Relationship Failure

Jerry, The patch for 3.0.29 to 3.0.30 is broken; can you fix? James -- Patch Results -- Patch #10 (patch-3.0.29-3.0.30.diffs.gz): + /usr/bin/gzip -d + patch -p1 -s 146 out of 146 hunks FAILED -- saving rejects to file docs/Samba3-ByExample.pdf.rej 8 out of 8 hunks FAILED -- saving rejects to file docs/Samba3-Developers-Guide.pdf.rej 194 out of 194 hunks FAILED -- saving rejects to file

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

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=

Greetings, I have recently upgraded from 3.0.28a to 3.0.30 on a couple of FreeBSD 7.0 servers: one in a Windows 2000 Active Directory environment, and the other in a Windows 2003 Active Directory environment, as member servers. Everything works for a while and then winbindd goes into sulking mode. Re-starting fixes everythng for a little while. I'm guessing I've hit the winbindd bug

Hi! We have a PDC for EEKS domain, running samba 3.2.0 FC9 64 bit, with the following trust relationships: one way trust where EEKS trusts ITL domain which is running Samba 3.0.30 FC8 64 bit two way trust between EEKS and ADEEKS domain which is running Windows Server 2003. Now for a given Windows XP SP2 workstation in EEEKS domain: 1. User logs onto ITL domain through the trust relationship and

Hello all, I did a fresh compile of 3.0.30, deploy'd it to a couple of servers, and then would get the following errors in my logs: pam_winbind(sshd): pam_winbind_request: write to socket failed! This would happen about 5 minutes after restarted smbd, nmbd, and winbindd. For the 1st 5 minutes every seems to work fine, then after that I can't login with my AD credentials anymore. After

I am trying to join a machine to one domain using the credentials from another.. Yes .. I do have the privileges :-) kinit works. It used to work (3.0.28a) .... but with later revs I get this sort of error. Bit irritating, as I have to ask somebody with admin privs to do it for me ... root at curric4182-07:/home/peter# net ads join -U e2052982 at ADMIN4182.INTERNAL Enter e2052982 at

I am trying to establish 2 way trust relationship between samba domain and Win2008 AD domain. The trust relationship is established and even verified by both side, but when I try to access samba resources from win2008 domain, it prompts for username and password. However, I can access the win2008 resources from the samba domain without the prompting of username and password. My win2008 is

After upgrading to samba-3.0.30 on domain member servers using NT4 as PDC and running winbind users can no longer access the shares, they get prompted for passwords (which shouldn't happen) yet still cannot connect. Dropping back to 3.0.28a works (even after adding the recent security patch) fine. What can I provide to get this fixed? Thank you, -- Chris

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================== ~ "You have an amazing capacity for self-deception. ~ How do you do that?" ~ --Number Six (spoken to Baltar) ~ "BSG" (2003)

Hi all, I'd have a question: is it possible for a Samba3 server acting as PDC (or AD) for clients win95-98, NT to establish a trust relationship with an Active Directory Win2k working in Native Mode? The aim is to give some old Clients access to some servers belonging a modern AD domain. I made some tests but could not get through. I'm doubtful this may work at all at the status of the

Hi, In trying to establish a trust relationship between a samba server (linux trusting domain) and WINNT (trusted domain, asnt01), an error occurred when the following command was executed, any suggestions please ?? bash> net rpc trustdom establish asnt01 >Password: >Could not connect to server ASNT1 >[2004/11/03 17:43:37, 0] rpc_parse/parse_prs.c:prs_mem_get(530) > prs_mem_get:

Hi all, Not less than 3 months ago we had our Solaris 9 samba server working happily. This is with samba 3.0.24 without ads support. The pertinent sections of the smb.conf file follow: [global] # workgroup = NT-Domain-Name or Workgroup-Name, eg: MIDEARTH workgroup = mydomain security = domain We created the machine trust acount on the server than used > net rpc join -U

Hiii Were you able to resolve the issue. Thanks for the reply.... -Sreejith

Hi, Is it possible to configure Windows 2003 Standard Server to have a domain trust relationship with a Samba PDC enabled with LDAP ? If so how ? regards shann ----------------------------------------------------------- Sign up and get your 30GB webmail at www.30gigs.com now!

Hello All, Is it possible for a domain server to be trusting of a PDC on another subnet? I have 2 domains, foo and bar. I have set up a trust account for bar on foo and net rpc trustdom list produces: Trusted domains list: none Trusting domains list: FOO S-1-5-21-194374591-1744372652-1779375073 which seems OK. I then issue: net rpc trustdom establish BAR on FOOs Samba

Hi All, I?m trying to make stable a bidirectional trust relationship on the wan. I tried many things and before I change the branch samba to a BDC of main office PDC I guess anything else can help me. Does winbind can help to keep the trust relationship stable over a wan connection? Or the better way to use it is with a single domain and lots of BDCs? Thank?s everybody, Gustavo

Hi there, I'm using an inter-domain trust relationship (DOM-B trusted, DOM-A trusting, COMP-A=DOM-A computer member). It works as expected (ish), DOM-B users can logon onto DOM-A computers. I'd like to know if it is possible to force login scripts and ntconfig.pol to be read from the DOM-A pdc server, rather than from the DOM-B one ? My setup includes a samba trusted domain and several

Hi, I have a domain using LDAP backend, and recently we've managed to establish a trust relation with another domain in our network, which uses a pure NT4 server. After that, some accounts from the trusted domain started being created in our base. The user created doesn't have the same attributes as a valid user (he doesn't have sambaSamAccount, for example). But for auditing

Hi, I'm using SAMBA 3.0 alpha19 to try the trust relationship between an NT 4.0 domain and the samba domain. The command I used was "net rpc trusdom", but it did'nt work, also the other "net" commands worked bad ( Segmentation Fault or return -1 ecc.). Could you kindly to tell me how to do to set the trust relationship with the SAMBA 3.0, or if there is any docs for