similar to: RPC Server unavailable

We'll definitely look into upgrading this, but it's a older, legacy system so we need to see what we can do without breaking it. Returning to the re-adding question, what steps do I need to do to clear the config of the failed peers? Do I just wipe the data directory of the volume, or do I need to clear some other config file/folders as well? Tom Op ma 17 jul. 2017 om 16:39 schreef

I'm currently using the standard Samba 4.5.8 on Debian 9.1, but would like to have spotlight support for Mac users. As far as I can tell, the standard package isn't compiled with spotlight support, so I will need to compile it myself. Is there an easy way to know what the configure string was that was used to compile the packaged version? I simply want to add the --enable-spotlight flag

We had some issues with a volume. The volume is a 3 replica volume with 3 gluster 3.5.7 peers. We are now in a situation where only 1 of the 3 nodes is operational. If we restart the node on one of the other nodes, the entire volume becomes unresponsive. After a lot of trial and error, we have come to the conclusion that we do not wan't to try to rejoin the other 2 nodes in the current form.

That's the way. However I'd like to highlight that you're running a very old gluster release. We are currently with 3.11 release which is STM and the long term support is with 3.10. You should consider to upgrade to atleast 3.10. On Mon, Jul 17, 2017 at 3:25 PM, Tom Cannaerts - INTRACTO < tom.cannaerts at intracto.com> wrote: > We had some issues with a volume. The volume is

I added a peer to a 50GB replica volume and initial replication seems to go rather slow. It's about 50GB but has a lot of small files and a lot of files in the same folder. What would happen if I try to access a file on the new peer? Will it just fail? Will gluster fetch it sealessly from the replication partner? Or will the file just not be there? Thanks, -- Met vriendelijke groeten, Tom

We're using the Debian 8 repository version, which is 4.2.14 Tom Op ma 2 jan. 2017 om 13:15 schreef Rowland Penny via samba < samba at lists.samba.org>: > On Mon, 02 Jan 2017 11:30:44 +0000 > Tom Cannaerts - INTRACTO via samba <samba at lists.samba.org> wrote: > > > We are trying to migrate away from out Windows 2008 R2 server to a > > Samba based DC. At

Hai Tom, Sure, you can apt-get install from that repo. You have 3 options. 1) http://apt.van-belle.nl/ the apt repo. Use it like any apt repo. Info on the site. 2) http://downloads.van-belle.nl/samba4/samba-4.5.3/ and use the installer This is when you want to get packages localy in you network and when you want to keep one version, and/or distribute this internaly. The installer script

We are trying to migrate away from out Windows 2008 R2 server to a Samba based DC. At this point we have both the Windows server as a Samba server as DC in the domain. After a while, we noticed that changes from the Samba server were not replicated to the Windows machine. Further investigation show that there are 2 lingering objects that prevent replication, and it has been for quite a while. The

Do you tnink I can simply apt-get install from that repo to upgrade the current samba? Going down the demote/re-join route, I'm encountering problems demoting the DC: Deactivating inbound replication Asking partner server DC1.mydomain.local to synchronize from us Error while demoting, re-enabling inbound replication ERROR(<class 'samba.drs_utils.drsException'>): Error while

Hai, I have/can recreate a build with this enable, but these would not make it into my repo. (yet) This is because i can not test the spotlight/tracker ( and/or TimeMachine ) settings. So.. There is the link with samba 4.6.7 builded for debian Jessie with spotlight enabled. Not signed, only amd64 arch. https://downloads.van-belle.nl/samba4/samba-spotlight-enabled.tar.gz Included :

On Mon, 02 Jan 2017 11:30:44 +0000 Tom Cannaerts - INTRACTO via samba <samba at lists.samba.org> wrote: > We are trying to migrate away from out Windows 2008 R2 server to a > Samba based DC. At this point we have both the Windows server as a > Samba server as DC in the domain. After a while, we noticed that > changes from the Samba server were not replicated to the Windows >

Hi I have a problem with Samba 2.2.7-3.7.3 on Redhat Linux 7.3. Samba run on this server like a PDC controller. This is the samba.conf # Global parameters [global] workgroup = ONSOFT netbios name = LINUX01 server string = Linux Mail Server encrypt passwords = Yes update encrypted = Yes name resolve order = wins host lmhosts bcast domain

Hi, I have a test environment with Samba4 on Ubuntu 11.04 (alpha15 package), and a little problem around the joining to the domain from my WinXP SP3 machine. I followed the official Samba4 Howto, then my configuration steps was these: - Install smb4 from ubuntu package - setup provisioning, created a testdom.mycorp.local - setup bind9 with gssapi (everything working fine) - test

Try to give your samba server another NetBIOS hostname than localhost and comment out the lines with server services and dcerpc endpoint servers. Check your DNS back end. For now it seems due to your smb.conf that you are not using the samba internal DNS server. It's not a must have, but samba does not provide dns. NetBIOS name should be equal to your DNS hostname. After that restart samba

From what I thought I did, I named the domain avalon.local. That's what the computers will join to. What does the netbios name have to do with the DC? With folder redirection I end up getting a name like \\localhost.avalon.local\Users\blahblah How much chance of messing up things is there if I run the rename script? On 12/22/14 12:22 PM, Rowland Penny wrote: > On 22/12/14 19:05,

On 19/03/15 12:48, Jesper Koivum?ki wrote: >> On 18/03/15 17:56, Jesper Koivum?ki wrote: >>> / Hi, > />>/ > />>/ I'm running a samba 4.2 server on RedHat5 and for some reason I > can't > />>/ seem to logon using the AD Users and Computers -tool. > />>/ > />>/ Whenever I try to connect to the PDC I get the following error:

On Wed, 2016-11-02 at 09:38 -0700, gespi via samba wrote: > Hi, > > Researched the forums before posting but was not able to find > solution to my > issue. Could be a unique problem. > >  GPO's are not being applied to users and computers because 'RPC is > unavailable'. The GPO's were being applied before, but not sure what > happened. Started noticing

I failed to mention this morning I restarted the samba server and that error did not come up once I ran 'Group Policy Update..'. But after a few minutes the RPC error returned. Figure this could be a samba issue as it was working on restart. The client is part to the Domain and able communicate with samba via ping. And i am still able to add additional machines to the Domain regardless of

Hi Team, I have configured and run SAMBA-4.5 AD DC on Itanium HP UX 11iv3. I tried to join the windows server 2008 DC to samba AD I have follwed the steps mentioned in the below link https://wiki.samba.org/index.php/Joining_a_Windows_Server_2008_/_2008_R2_DC_to_a_Samba_AD While i am trying to execute the steps mentioned in section "Joining the Windows Server to the Domain"

On Mon, 12 Jun 2017 06:40:29 -0700 (PDT) davidgs via samba <samba at lists.samba.org> wrote: > I'm new to samba/AD on Linux, so please go easy on me. I've been > trying for a bit to set this up and am having some success and some > not. > > I am running Ubuntu Server 16.04 LTS and Samba > > > As I said, I'm not new to Linux/UNIX, but this whole