similar to: Samba AD member and connections from non-AD systems failing

Hi Guys, I have a rebalance that is going so slow it may never end. Particulars on system: 3 nodes 6 bricks, ~55TB about 10%full. The use of data is very active during the day and less so at night. All are CentOS 6.3, x86_64, Gluster 3.2.6 [root at node01 ~]# gluster volume rebalance data01 status rebalance step 2: data migration in progress: rebalanced 1378203 files of size 308570266988

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

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

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 a number of Samba servers on RHEL (Samba 3.0.33) in an AD environment using a mix of Windows 2008 and windows 2008 R2 servers. Configuration file is pretty minimal: [global] workgroup = AVWORLD security = DOMAIN log file = /var/log/samba/samba.log max log size = 500 wins server = 10.50.4.31 dns proxy = no #log level = 10 log level = 3 passdb:5 auth:10

I have been on the web for hours reading email postings about WINDBIND. Here is the scenario. Samba 2.27 on Redhat 8, installed via the redhat RPMs. the first interesting note was that there is no samba-winbind rpm. It is a part of the samba-common.rpm in redhat. I have been using Samba as a file server for quite some time. And 100% of my issues with it stem from permission problems. So I heard

I have one Linux RHEL4 box setup as a PDC and several other Linux RHEL4 samba servers and Windows XP boxes joined to the domain. Ever since upgrading the Linux box to Samba 3 (they are currently running samba-3.0.10) I have problems with the Linux samba clients suddenly dropping out of the domain. Operations suddenly start failing with [2006/09/27 16:03:25, 3]

I'm relatively new to samba I have been experimenting for a week or so, though I have setup several 2000/NT domains and have been using Linux for a couple of years. I'm using Red Hat 9, updated completely via apt. Samba 3.0.9 installed from apt and i am using the stock ldap server that installed with red hat as my back end. I followed the samba.idealx.org guide to get to where I am

I have been running Samba 2.2.8 on a Solaris 8 server with a valid NetBIOS server name on the AD domain. The Samba 2.2.8 configuration was configured for security = domain. Everything was fine until the AD domain controllers were "upgraded" to Windows Server 2003 SP1. User authentication would no longer function with the following error message in the samba 2.2.8 log:

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

Hello, In our environment we've had SAMBA 3.0.21b joined to a Windows 2003 domain forest as a member server (configured with SECURIY = DOMAIN) for couple of years with no problem. Just recently the SAMBA server seems to be loosing connection to the Windows domain controllers. We are able to re-establish the trust (re-join samba server to domain) successfully. However after a few successful

Running Samba mostly on Redhat 5 with version 3.5.4-0.83 Also failed on Debian 3.5.6 and Solaris with a 3.5 version. Logging details here are from Redhat case. We have a similar problem on all Unix/Linux systems using ADS as the backend authentication for samba shares on Unix/Linux. It was working before today and we didn't change anything. Today, any time we try smbclient or a Windows drive

I have been running a Samba PDC with Samba version 3.0.0 on Redhat 7.3 for quite some time. My WinXP Pro SP2 system is part of the domain and everything has been working just peachy. And then, of course, I had to tinker with it. I upgraded the linux box to Whitebox Linux 3.0, a derivative of Redhat Enterprise Linux 3.0. It comes with Samba 3.0.7. After installing and updating everything, I

Hello, Is it really possible that just the user root with the samba password can join workstations into the domain? I have also some other users who are domain administrator, but with this users i can't join any workstations into the domain. This is mor me a important security point, because I want to give some people the acces right to join workstations into domain and only this function.

I am having problems implementing Samba using security=domain against a Windows 2008R2 server. I have been able to successfully join the domain via a net rpc join. Anytime I try to access a share through smbclient I get a NT_STATUS_TRUSTED_RELATIONSHIP_FAILURE but nothing in the logs (on either side) seems to be giving me any leads on where to look. The system is locked down to allow NTLv2

Hello all, I wanted to share with you this announcement for an upcoming workshop on the analysis of neural data to be held this summer at woods hole, MA. The workshop has been extremely productive in the past years and we anticipate another good working group this year. This workshop is applicable for any working in time series analysis whether it involves point processes or sampled continuous

I just hope that this time I get heard since obviously nobody reads news://linux.samba ... Platform: SuSE-9.1, kernel-2.6.5, samba-3.0.4 I have recently upgraded from 3.0.2a to 3.0.4 and I have just noticed that using the same smb.conf as with previous version, the system just does not work anymore for me ! Furthermore, smbpasswd utility appears to be dropped ! Afterwards, I have noticed

Hi. I've got a strange issue here. Some time ago (in march ;) I upgraded my FreeBSD-6.0 Samba 2.2 to 3.0 (currently 3.0.24). After creating groupmaps and doing all the other upgrade tasks, everything seemed to be alright. However, it was not possible to login from some machines (getting error for the wrong password). After disjoining and rejoining domain with these machines, it was possible

Stephanie, Thank you for your help. I tryed what you suggest but no luck.. I get this: root@lnxsrvr2:~# /usr/local/samba/bin/net groupmap add ntgroup="Domain Admins" unixgroup="Domain Admins" rid=512 Can't lookup UNIX group Domain Admins Is there something with initial compiling samba 3.0.0 that would disable this? All the documentation that I've seen makes it look so