similar to: failover shares

Hi, I have a failover configuration. The domain controller's IP: 10.23.14.150 as dc01 The failover IP is: 10.23.14.155 as dcha I added an A and a CNAME record to the dns for the failover IP. It is working, i can see the shares, but I could not enter to any share as user, as Administrator it works. I tried to add the interface variable (i am not sure this is available in samba4), that

Hai, Samba 4.1.5 I have an old problem with my failover IP/name which is 10.48.16.155/domaincha. The 2 servers IP address and DNS names are 10.48.16.150/domainc01 and 10.48.16.151/domainc02. Domaincha always points to the "active" server so when any of the servers dies my users couldn't see anything, and also i can set up home directories to point the failover address instead of 1

Hi Samba Team, I have done a classic upgrade on my Samba PDC to version 4.8.5 and have also setup a DC member joined to the AD forest. Both DC and member DC are running on CentOS 6.6. I try to shutdown my first AD DC to do a failover test, everything looks fine until when I try to do a ping test to my domain name using my Windows 7 client PC, noticed the ip address it resolved to, is my first AD

Hi guys, I have a domain with Samba 4.0.5 domain controllers and also a failover DRBD shared disk, where the "active" DC controlls the access to the disk. DOMAINC01 - 10.48.16.150 DOMAINC02 - 10.48.16.151 DOMAINCHA - 10.48.16.155 << this would be the failover IP, which works perfectly on Windows XP clients. I can see the shares, just like on DOMAINC01 or DOMAINC02 and if the

(please reply to the list) If the record does not exist, then you have an other problem. Because samba does support this : cat /var/lib/samba/private/named.conf.update /* this file is auto-generated - do not edit */ update-policy { grant INTERNAL.DOMAIN.TLD ms-self * A AAAA; grant Administrator at INTERNAL.DOMAIN.TLD wildcard * A AAAA SRV CNAME; grant

Hi, I tested my failover yesterday and a strange problem came up. While my dc01 was down I could not login on dc02 with any of my local accounts. After dc01 was online again, login was OK. My nsswitch.conf is a "regular" file: passwd: compat winbind group: compat winbind shadow: compat As I read about nsswitch, with this config it should try to authenticate

Hi! We are facing problems with Windows 10 and dynamic DNS. The problem is that samba_dlz prevents AAAA deletion. Can we permit AAAA somehow or fix this? Disabling IPv6 and removing IPv6 driver from interface made no difference whatsoever. This works on Windows 7 just fine. Samba version: 4.1.6-Ubuntu We see the following with wireshark: Domain Name System (query) Transaction ID: 0x8aa4

On 24/07/2020 01:01, Jason Keltz via samba wrote: > Hi Rowland, > > Speaking of senior moment. I just figured out the problem... > > My DC host has its regular name - dc01.example.com and then its AD > name dc01.ad.example.com.? Even though both resolve to the same IP, I > was using dc01.example.com which is apparently a no no because > Kerberos is particular about

; TSIG error with server: tsig verify failure Mayabe update/setup your TSIG key. https://access.redhat.com/documentation/en-us/openshift_enterprise/2/html/puppet_deployment_guide/generating_a_bind_tsig_key Im also wondering why RH is using : '--disable-isc-spnego' Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org]

Hi All thought I'd post my results from following your notes when trying to replicate my Samba PDC onto a Samba BDC as seen here https://wiki.samba.org/index.php/1.0._Configuring_Samba everything seemed to work as described until I got into the 'Initialization LDAP Database' and preloading the edited "preload-differentialdesign.ldif" file, kept getting a failure from

Hai, As I know i could open my shares via domain eg: \\domainc.com\share I have 2 samba 4.1.5 server and one win2003 DC. Succesfully made a clustered filesystem so now both servers (except win2003) can open the shares. My problem is: i succesfully opened the share yesterday, it worked well one time but since that i couldnt open it via \\domain.com\share only via \\dc01\share or \\dc02\share.

Hello Kris, On 13/02/2020 19:28, Kris Lou via samba wrote: > My reverse zones have PTR records. Though I don't have NS records for all > of my DC's. I guess that needs to be manually created. I have NS records for all 2 of my DC's and I just followed the Installation page on the Wiki. > Also, you don't have any CNAMES or domain overrides pointing to a single >

> So you never read this: > https://wiki.samba.org/index.php/Changing_the_DNS_Back_End_of_a_Samba_AD_DC > Which means that you probably never ran the aptly named > 'samba_upgradedns'Of course I ran this. Many times. I'm not stupid, Rowland. At least I can read:D If I've seen that Bind doesn't work, I had to change backend to internal DNS.I carefully read and made

> > I am not using BIND with Samba, just the Internal DNS which is the default. > What do you mean when you say "CNAMES or domain overrides pointing to a > single DC"? > I have DHCP handing out both DNS servers as 192.168.0.218 and > 192.168.0.219 and they both work as nameservers perfectly. This might be a problem down the road. The Samba Internal DNS does NOT

Hi Gurus, I have a simple failover cluster on two SLES 12 SP3 nodes with Samba/winbind for authenticating AD-user access to the shares. The shares are reached through a virtual hostname/IP which differs from the SLES-server itself. The servers uses SSSD for normal SSH-authentication, also against the same Active Domain. Here is the problem - if I get Samba/winbind to work with the virtual

Hi, I had a weird problem this morning. My users and all of the shares are gone. I tried to restart samba but that was not helped, wbinfo -u could not show any user. Restarted bind9 tho..nothing happend. What kind of process could do this? As a last chance I restarted the server..that helped. Regards, Robert

centOs5.5/samba4/named here is a short guide setting it up to work. I added TSIG for bind-master amd bind-slave. Update to samba4 alpha13 added (installing git on CentOs 5.5). If you do this howto right now you will start with samba4 alpha13. You do not need the update section. But you need git for your installation because the rsync-thing is broken!!!!!! First of all do not install the bind

Thanks for the suggestion Rowland, I had already tried that though and both secondary DC's resolve.... host -t CNAME fbce444a-8707-4c69-8066-d75aacfb07f0._msdcs.mydomain.com. fbce444a-8707-4c69-8066-d75aacfb07f0._msdcs.mydomain.com is an alias for dc02.mydomain.com. host -t CNAME 04225dbe-d69c-4ea5-8930-eb8746790180._msdcs.mydomain.com.

My reverse zones have PTR records. Though I don't have NS records for all of my DC's. I guess that needs to be manually created. Also, you don't have any CNAMES or domain overrides pointing to a single DC? Perhaps Bind is pointing to another internal DNS server, and then to a public DNS? ---- Here's a way to test failover from a Windows client: You can switch logon servers

Hi all, Can anyone pleas tell me what would be best practice to use shared storage with virtual machines, especially when it involved high availability / automated failover between 2 XEN servers? i.e. if I setup 2x identical XEN servers, each with say 16GB RAM, 4x 1GB NIC's, etc. Then I need the xen domU's to auto failover between the 2 servers if either goes down (hardware failure /