similar to: Samba file sharing with AD authentication doesn't work on some boxes

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

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

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.

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

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

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

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

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

Trying to upgrade from 2.2.3a to 2.2.4 broke our Solaris 8 PDC. We see the following issues: - Compile flag -KPIC is not valid for gcc, does not seem to bread build - Now looks like directory /usr/spool/samba is needed, but not created by install - smbclient -L hemlock fails with login problem: [2001/10/16 10:43:28, 0] smbd/password.c:connect_to_domain_password_server(1295)

Good morning, I am posting msgs on the NON OPERATION of WINBIND. GOOD I should say that without I had made any change in the system it started to work in an of my facilities. INCREDIBLE but it worked. The problem now is that I tried log in the samba not previously using an user servant in the smbpasswd and him of autentication mistake. But should not WINBIND facilitate that? Do I need to have user

Hello everyone, I am trying to configure a Samba 2.2 server to allow users to mount their home directories (stored on a UNIX filesystem) from Windows after authenticating against a Windows 2000 Domain Controller. The Samba server is 2.2.3a compiled with acl support on Solaris 8. I think I am experiencing some (hopefully) basic configuration issues and can't seem to get it to work. I

Hello! I have a samba fileserver (Debian Woody, Samba 2.2.3a) that I am trying to join into an NT domain (smbpasswd -j ...); the command says that it joined the domain successfully. Then I setup security=domain, workgroup name etc. as outlined in the samba howtos. However whenever I try to access a share on the Samba server I am prompted for a password (even though I already logged in through

Hi ... When trying to migrate from samba3 to samba 4.2.2 I am facing a severe problem that bugs me for hours now. I cannot get a samba 4.2.2 fileserver to work with a samba 4.2.2 PDC as a domain member. My scenario: Samba 3 network. PDC and fileserver where Samba 3.6.25. LDAP backend. We can't move to AD right now so I wanted to move to the current 4.2.2 at least to do this step but to

We are running samba 3.0.7-1.3E.1in an AD domain which is running a PDC emulator. The samba servers are configured with "security = domain" and on some servers the password server is specified while on others we are using *. We very frequently see the following messages in the log files of the servers. "domain_client_validate: Domain password server not available"

I am having a problem with getting samba 2.2.3a to work with our current set up. I used to have samba 2.0.7 working perfectly, but decided to upgrade to try and get Win2k clients to be able to access the shares on the UNIX system hosting samba. When I try and access any of the shares on samba (it doesn't matter who the client is) I get the following messages produced in the log file:

What kind of error is "NT_STATUS_OK"? Logs below: [2003/01/29 15:30:46, 3] libsmb/namequery.c:resolve_lmhosts(768) resolve_lmhosts: Attempting lmhosts lookup for name TESTE011<0x20> [2003/01/29 15:30:46, 3] lib/util_sock.c:open_socket_out(845) Connecting to 192.168.100.1 at port 445 [2003/01/29 15:30:47, 0] rpc_client/cli_netlogon.c:cli_net_auth2(157) cli_net_auth2: Error

All, We were running samba4-4.0.0-68.el6_7.rc4.x86_64 on our CentOS 6 box serving printers and joined to our domain. No issues whatsoever and quite happy. We upgraded to samba4-4.2.10-6.el6_7.x86_64 and have had ongoing issues since it was installed. Everything runs along just fine for a while (an hour or so) and then our logs start filling with [2016/04/13 17:51:21.635283, 0]

I have a win2k domain ... 2 of the client machines are Red Hat (7.3 and 8.0). I set everything up to use the DC to authenticate ID/PW. Everything worked perfectly until a week or so ago ... Samba would automatically create a home folder and the whole nine yards. Now I can see the shares on the Samba machines, but I can't access them ... just prompts for the ID/PW over and over. I can mount

So far we have been working well for a week now. We are using Samba 3.02a on suse 9. Authentication is against an win3k AD. Apart from a Kerberos ticket expiring, (a croned restart fixes this) we have one new problem We found we needed an additional AD server as the primary begun to fail on a regular basis. So we added one. Now this new server grabs the authentication requests before the old one