similar to: samba-3 trustdom AD (mixed mode) problem

I sent this out yesterday and im still having this problem, has anyone seen this before? original email: Im having an intermittent problem with samba. Im running samba 3.0.2a on solaris 8 that i downloaded from sunfreeware.com I have my smb.conf setup to get passwords from my active directory server and it usually works fine. I ran a net join command like so to originally join the domain: root#

Im having an intermittent problem with samba. Im running samba 3.0.2a on solaris 8 that i downloaded from sunfreeware.com I have my smb.conf setup to get passwords from my active directory server and it usually works fine. I ran a net join command like so to originally join the domain: root# net join -S WIN2KSERVER -w MYDOMAIN.com -U Administrator Password: Joined domain MYDOMAIN. It will run

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

Hello I'm having some dificulties joining my Samba 3.0alpha (and 2.2.7a) machine to my NT4 domain. Let me tell you what I'm attempting to accomplish. I want to setup the Samba system to authenticate to my NT domain so that I can use NTLM Proxy authentication with SQUID. Through reading the docs, I'm under the impression that in order to allow thre SQUID/Samba setup to auth on

Hey All, I'm having problems with a Trust relationship between our Win 2002 PDC and our Samba PDC. Here are the details: (names have been changed to protect the innocent...!) Win 2002 PDC: WINPDC, IP 1.2.3.4 Client in Windows Domain: CLIENT Samba PDC in Domain TEST: SMBPDC I use Start -> Run -> \\SMBPDC on a machine in our Windows 2000 Domain and got an error saying "\\SMBPDC, A

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

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

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 All, We're going to upgrade our DCs to Windows 2008 R2 native mode soon, so we're facing with the challenge that how to get our samba servers (Solaris 8 & Solaris 10) work with Windows 2008 R2 native mode. I've compiled Samba 3.5.9 with AD support. Then I installed and configured the binaries on my 3 test machines (one Solaris 8 and two Solaris 10). The strange problem is one

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'

Hi. I joined a fileserver system with Samba version 4.5.12-Debian (fileserv) in an Active Directory domain managed by a Samba 4.6.7-Ubuntu installed on another system using "realm discover" and sssd. The Samba fileserver is correctly joined into the domain and I can correctly browse AD users: root at fileserv:/# getent passwd my.user

Hello, and thanks in advance for any assistance. I have a linux machine that I'm trying to join to a windows 2003 sp1 active directory. The specifics are: RHEL5, samba version samba-3.0.23c-2.el5.2.0.2 a firewall between this server and the rest of the world (which includes the DCs), ports are open for kerberos and CIFS inbound and kerberos, CIFS, NTP and UDP oubtound. this machine

hi gurus My samba upgrade woes: - I have to run 2 instances of samba one for dev and one for UAT. both the instances are giving me hard time after the upgrade. One instance keeps giving me following error: - connect_to_domain_password_server: unable to open the domain client session to machine xxxxx.xxxxx.xxxxx.xxxxxxx.COM. Error was : NT_STATUS_CANT_ACCESS_DOMAIN_INFO. [2012/09/04

I have a few RHEL7 boxes, all of them are members in MS Win domain using SSSD. All of these linuxes run Samba for file sharing with the same config. Usually it works nice, but from time to time users cannot map Samba folders, with the following message in the log: [2017/03/07 14:58:27.050493, 0] ../source3/auth/auth_domain.c:121(connect_to_domain_password_server)

SAMBA as a member server in an AD domain Access samba share from any client (e.g. windows 7) using AD domain credential, getting below error message: [ ---------- C:\tools>net use * \\sbdevsvr213.dev.ib.tor.scotiabank.com\fundmgr <file:///\\sbdevsvr213.dev.ib.tor.scotiabank.com\fundmgr> * /user:domainName\un System error 1789 has occurred. The trust relationship between this

Hello, I suggest you start reading here: https://fedorahosted.org/sssd/wiki/Configuring_sssd_with_ad_server and if you want to use winbind and not sssd. read : https://wiki.samba.org/index.php/Setting_up_Samba_as_a_Domain_Member Now i dont use sssd and there is an other mailing list for sssd, ( sssd is not related to samba (yet) but my guesses are.. - your keytab is expiring and not

Situation: OpenSUSE 11.2 server with LDAP for authentication. Authentication status: users CAN login using LDAP using ssh. Additionally, I have kerberos setup and users can get kerberos tokens without any problem. Environment: ADS running on Windows. I do not control the ADS. I had to ask an IT guy to come run a script that does the equivalent of net ads join and a few other things needed for an

Ok guys after reading a ton of documentation etc I have finally got my Linux machine to work in a ADS enviroment. I can actually go on a windows machine type in \\linuxboxname and access shares on my Linux box. First of all I joined the ADS correctly. wbinfo -u and -g show proper values and everything works except my Linux computer does not show up in Network Neighborhood on windows machines.

Samba shares work for windows 7 and Server 2008, but XP and Server 2000 recieve the following error when trying to map samba shares: "The trust relationship between this workstation and the primary domain failed." tail -f /var/log/messages Apr 10 07:38:03 samba01 smbd[23581]:?? connect_to_domain_password_server: unable to open the domain client session to machine ad1.strat.com. Error

I'm a bit puzzled. I am able to map an account without any problem on Samba 2.2.8a (security=domain). However, access fails with Samba 3.0.14a when everything else is the same (same configuration files). Any advice as to the cause of the problems (and its solution) would be appreciated. >From 2.2.8a logs [2005/08/24 14:59:51, 3, pid=7767] smbd/reply.c:(880) Domain=[americase]