similar to: Problems with Trust Relationship

I have one server windows2000 mixed mode with active directory and samba 3.0 PDC. This is my smb.conf [global] workgroup = TESTIPLANET netbios name = TEST server string = DOMINIO TEST interfaces = 10.10.6.158 bind interfaces only = yes preferred master = Yes domain master = Yes wins support = Yes domain logons = yes

I am running Samba ver 3.0.37 on Solaris 10 (sparc) as a PDC with LDAP for the backend for both samba and unix accounts. Assume the samba SMBPDC is called "PDC." I have also set up a trust with an Windows domain- lets call it WINDOMAIN- (the PDC for the Windows domain is Win 2003 but is in mixed mode for backwards compat.) The SAMBA domain trusts the WINDOWS domain, not not vice

I'm attempting to set up a 2-way NT4-style trust between samba 3.0.1-2 (from source rpm on redhat 7.2) and Windows 2003 running active directory. The AD server (SANDMAN) trust of my Samba domain works fine, but when I try to use the Samba trust of the AD server I get the following error: [2004/02/04 15:52:34, 3] rpc_client/cli_pipe.c:rpc_api_pipe(462) Bind NACK received on pipe c009!

Hello good people, I am fighting with following issue: our users are complaining about very slow/delayed displaying of main folders during accessing server using \\dns.name.of.server (using \\IP or \\netbios_name is it with same slowness). But once they are authenticated, displaying contents of (sub-)folders are getting normal. Once the user hit "enter" key on

Hi all. I'm trying to share a printer out via samba, and it's suddenly stopped working. Samba says it's connecting to the DC, but then returning NT_STATUS_NO_SUCH_USER. It wasn't doing this earlier today. I haven't changed anything in the top half of the smb.conf file ... only the print-related stuff. Any ideas? The log is saying: [2007/05/21 11:40:26, 3]

Hi All, I noticed slow performance when make file copy from server to client. From client to server it is OK. Also I tried mount locally on localhost - same results. Here is my smb.conf --------------------------------------------------------------------------------------------------------------------------------------------------- [global] # 1. Server Naming Options: # workgroup =

Hi, I'm trying to connect to a Samba Domain Member, but I always end up with the same strange error. The PDC (authenticating againt LDAP) and the server itself (Lobo) are Samba 3.0.2a-1 (Debian). I first tried to connect from my Windows client. It gave me the following error: "\\Lobo is not accessible. The specified network name is no longer available." When connecting via

I recently upgraded my PDC's and BDC's to 3.0.14a but my member servers are still running 3.0.10. Today users complained that the couldn't logon to the member server. When I try to run a wbinfo -u I get: Error looking up domain users Here's the log.windbindd: 2005/05/31 11:06:26, 4] param/loadparm.c:lp_load(3933) pm_process() returned Yes [2005/05/31 11:06:26, 3]

Hi all, I'm trying to make samba authenticate to my Active Directory Domain. I already configured and tested Kerberos5 and joined my machine to my domain with no problems, getent passwd and group give me the correct output also wbinfo give a good output too, and I can logon using my domain user to SSH and to my server console, so I assume my Kerberos config is correct. Also I

I am in the process of upgrading Samba from version 3.0.1 to 3.0.14a. The AIX team applied maintenance that sent the samba processes into some sort of loop which was impacting the machines. We were able to upgrade one of the unix servers with no issues but I cannot get the other one to work. We have 3 unix machines with samba that are working properly within this domain (the other 2 are still

Hi I have the following question: Joining Win200x as ADS/DOMAIN, I see no problems for windows users to get authenticated even if they don't have local accounts. However, with the same samba (3.06) joining NT4 SP6 domain I see that only users that also have entry in /etc/passwd are been authenticated. I followed winbindd traces and saw that there is no problem communicating with

I have four samba servers connecting into a samba PDC (using ldapsam as password backend) and all of the servers get the "transport end point not connected" error. I've looked in the groups but cannot find anything that helps. I've tried to set my oplocks=no and other similar settings but nothing seems to help. The only thing that seems to limit excessive sleeping smbd

> I am having problems getting security=domain to work properly with > Samba 3.0.11 (this seems to be the recommended configuration for the > application which I use - ClearCase) > > We are running on a Solaris 10 server. > > We created a machine account for the server and then ran the command > to join the domain : > net rpc join -S domain_controller -U user%pass

Hi, After upgrading one of my samba servers from ubuntu jaunty (3.3.2) to karmic (3.4.0) I cannot access the shares any more. The server (FINTLEWOODLEWIX) is set up to check authentication via a PDC (IO), which is also running 3.4.0 (and has been before). Guest access is allowed so that any users without a local unix account will be granted read access. Valid users are allowed read/write. After

I've got no responce to my mail with subject 'samba 3.0.7 cannot join NT4 domain', so I dug deeper. I also read carefully these docs: swat/help/Samba-HOWTO-Collection/domain-member.html swat/help/Samba-HOWTO-Collection/winbind.html This is what I observe: 1.I srtart from clean state: PDC has no HUNTER machine account (chkd with L0phtcrack) HUNTER has empty var/{lock,private} samba

My original post didn't seem to work properly - so I am trying again ... I am having problems getting security=domain to work properly with Samba 3.0.11 (this seems to be the recommended configuration for the application which I use - ClearCase) We are running on a Solaris 10 server. We created a machine account for the server and then ran the command to join the domain : net rpc join -S

On our AIX 5.2 system we have Samba 3.0.4 and 3.0.21b. The smb.conf files are identical for both versions. The 3.0.4 version runs fine, but with 3.0.21b, we get errors like the following when trying to run smbclient: [2006/02/28 22:03:05, 0] rpc_client/cli_pipe.c:cli_rpc_pipe_open_schannel(2641) cli_rpc_pipe_open_schannel: failed to get schannel session key from server FD0 00XSFED01 for

Hi, I have two servers, servera (DOMAINA) and serverb (DOMAINB). I have made a trust between this domain. But I try logon computer from domaina as user for domainb, the log in serverb wrotes me that a authentication was succeded: [2004/10/12 17:19:19, 3] rpc_server/srv_netlog_nt.c:_net_sam_logon(620) SAM Logon (Network). Domain:[DOMAINB]. User:[bronasek@\\XP1] Requested Domain:[DOMAINB]

Packet send failed to 62.101.92.90(137) ERRNO=Network is unreachable [2004/05/03 10:27:45, 0] nmbd/nmbd_packets.c:reply_netbios_packet(975) Hi list, once again looking for some good advice. I apologize for the long email and for the mistakes I could have done. I'm running Samba 3.0.2-6.3E on White box linux 3.0 kernel 2.4.21-4.EL (clone of Red Hat EL 3.0), the environment is a Win 2k ADS

Good afternoon. I cannot seem to get my test samba (domain member) server to use a windows 2003 PDC, SJMEMDC40. Are there any outstanding issues with a win2003 PDC and a samba domain member server? Her are my errors: [2006/08/16 16:40:46, 0] rpc_client/cli_pipe.c:get_schannel_session_key(2443) get_schannel_session_key: could not fetch trust account password for domain 'CBT'