search for: somedom

...ran into a strange permission problem with deleted folders. The newly created folders in the recycle folder have the wrong permission. The deleted file(s) itself has the correct group (rw) permissions. The shares correct permissions: getfacl Papierkorb/ # file: Papierkorb/ # owner: root # group: somedom\\domain\040users user::rwx user:root:rwx group::rwx group:somedom\\domain\040users:rwx mask::rwx other::--- default:user::rwx default:user:root:rwx default:group::--- default:group:somedom\\domain\040users:rwx default:mask::rwx default:other::--- The subfolder that 'vfs modules' created in...

...testing how to add a member server for file server services. We were able to get the server to join the domain and also idmapping works mostly as expected. If we use getent group everything works as expected and we get the correct group with the correct GID: root at fileserv2:~# getent group SOMEDOM\\stas SOMEDOM\stas:x:10165: We can use getent passwd and wbinfo -i fine for all our ldap created users and get the correct UID/GID if we are using the config: idmap config SOMEDOM:unix_primary_group = yes root at fileserv2:~# getent passwd SOMEDOM\\test.zweimal SOMEDOM\test.zweimal:*:10409:10000...

Setup a DC using 4.0.3 - all appears to go fine... Setup a second DC and everything works fine to here...but I'm not sure if replication is actually working or not. Here's what I get from ./samba-tool drs showrepl I've also done. [./samba-tool drs kcc -Uadministrator dc2.samba.somedom.local] in an attempt to fix the replication problem. (or what I think is a problem.) [The outbound neighbors data seems hinky... and searches on similar cases don't seem to return much useful data.] --- Default-First-Site-Name\DC1 DSA Options: 0x00000001 DSA object GUID: b895f491-759f-4c72-a0...

Hello. I'm trying to perform a classic upgrade from Samba 3.6.6 with LDAP backend on Debian to 4.1.6 on Ubuntu on a new machine. The samba-tools creates the following *smb.con*f: *# cat /etc/samba/smb.conf** *[global] workgroup = SOMEDOM realm = somedom.local netbios name = SOMEDOM server role = member server passdb backend = samba_dsdb server services = s3fs, rpc, nbt, wrepl, ldap, cldap, kdc, drepl, winbind, ntp_signd, kcc, dnsupdate idmap_ldb:use rfc2307 = yes But if I run: *# sed...

Maybe this is a stupid idea, but what we are doing here is using just the domain name for all sorts of services, i.e. LDAP. So instead of pointing a client to dc1.somedom.contoso.com or dc2.somedom.contoso.com, we point them to somedom.contoso.com which is then resolved to both and the client can pick. Best regards Johannes Am Mo., 23. Nov. 2020 um 17:02 Uhr schrieb Rowland penny via samba < samba at lists.samba.org>: > On 23/11/2020 15:47, Sven Wick via...

...pid 15374) Issue occurs on all tested machines, with different account names, on (at least) two differrent DC. Access is fine from smbclient no matter if I use IP, domain FQDN or alternate FQDN. smb.conf snipped (sysvol & netlogon are default provisioned ones) [global] workgroup = SOMEDOM realm = somedom.fdqdn netbios name = SOMEDC server string = AD DC SOMEDC server role = active directory domain controller idmap_ldb:use rfc2307 = yes interfaces = someIP/24 bind interfaces only = Yes template shell = /bin/fa...

...ies on files, I can see that both "full control" and "modify" are off. Even if I force them by going to the file properties, I can't get the modify flag to stick. Any ideas? I'm running out of them... Thanks my smb.conf: [global] security = ADS workgroup = SOMEDOM realm = SOMEDOM.LOCAL username map = /usr/local/samba/etc/user.map log file = /var/log/samba/%m.log log level = 2 server role = member server idmap config * : backend = tdb idmap config * : range = 3000-7999 # winbind nss info = template #...

...tested machines, with different account names, on > (at least) two differrent DC. Access is fine from smbclient no matter if > I use IP, domain FQDN or alternate FQDN. > > smb.conf snipped (sysvol & netlogon are default provisioned ones) > > [global] > workgroup = SOMEDOM > realm = somedom.fdqdn > netbios name = SOMEDC > server string = AD DC SOMEDC > server role = active directory domain controller > > idmap_ldb:use rfc2307 = yes > > interfaces = someIP/24 > bind interf...

Hi, I have a setup with 2 DCs which works just fine. Since we have some legacy systems which can't deal with 2 DNS Names I used ctdb to manage a floating IP (in addition to the fixed IPs) between the DCs which works great also. But then the replication breaks for some parts (Users still were replicated) because the floating IP was added to the internal DNS zone and one of the DC tried to

.../dev/VolumeGroup/SomeVolume'/> <target dev='hda' bus='ide'/> <address type='drive' controller='0' bus='0' unit='0'/> </disk> changing the center line to <source dev='/dev/drbd/by-res/SomeDom'/> (or /dev/drbdN - to which that's a symlink), then I get # virsh start sql error: Failed to start domain SomeDom error: unable to open disk path /dev/drbd/by-res/SomeDom: Wrong medium type If this were a normal file system, setting up DRBD with it, then remounting it through t...

...(pid 15374) Issue occurs on all tested machines, with different account names, on (at least) two differrent DC. Access is fine from smbclient no matter if I use IP, domain FQDN or alternate FQDN. smb.conf snipped (sysvol & netlogon are default provisioned ones) [global] workgroup = SOMEDOM realm = somedom.fdqdn netbios name = SOMEDC server string = AD DC SOMEDC server role = active directory domain controller idmap_ldb:use rfc2307 = yes interfaces = someIP/24 bind interfaces only = Yes template shell = /bin/fa...

# Global parameters [global] interfaces = bond0 log file = /var/log/samba/%m.log log level = 5 auth:5 winbind:8 printcap name = /dev/null realm = SOMEDOM.AT security = ADS username map = /etc/samba/user.map winbind refresh tickets = Yes winbind use default domain = Yes workgroup = ARBEITSGRUPPE idmap config arbeitsgruppe:unix_nss_info = yes idmap config arbeitsgruppe:range = 10000-9999999 idmap config arbeitsgruppe:backend = ad idmap config...

...r DC's a master under Samba4 might be a good thing to know, before I have an emergency where I need to do it. --- PS: I did one more search and got this article. https://lists.samba.org/archive/samba/2012-April/167012.html Is it really as easy as [./samba-tool fsmo transfer --role=all --realm=SOMEDOM.COM ... ] ? Again, something more formal might be nice. I'd be glad to author it on the Wiki if someone can walk me through the proper steps. [I don't want to document it if I'm not sure I'm doing it right.] TIA -Greg

...tested machines, with different account names, on >(at least) two differrent DC. Access is fine from smbclient no >matter if >I use IP, domain FQDN or alternate FQDN. > >smb.conf snipped (sysvol & netlogon are default provisioned ones) > >[global] > workgroup = SOMEDOM > realm = somedom.fdqdn > netbios name = SOMEDC > server string = AD DC SOMEDC > server role = active directory domain controller > > idmap_ldb:use rfc2307 = yes > > interfaces = someIP/24 > bind interfaces only = Ye...

...ification lots of hundreds times a day.... but suddenly runs into trouble .. here the logs ... (please take care..., I?m a newbie ;-) Dec 18 10:25:05 server dovecot: pop3-login: Disconnected: Inactivity: method=PLAIN, rip=91.9.201.219, lip=83.154.61.77 Dec 18 10:25:07 server deliver(user.yxz at somedom.de): User request from dovecot-auth timed out Dec 18 10:25:07 server postfix/pipe[22156]: 63861180062A7: to=<user.yxz at somedom.de>, relay=dovecot, delay=60, status=deferred (temporary failure) Dec 18 10:33:09 server dovecot: auth(default): ssha_verify(info at mydom.de): invalid SSHA base6...

> we point them to somedom.contoso.com which is then > resolved to both and the client can pick I want to avoid Round-Robin DNS > You cannot use CTDB with AD DCs You can. /etc/ctdb/nodes 192.168.30.11 192.168.30.12 /etc/ctdb/public_addresses 192.168.30.10/24 ens18 /etc/ctdb/events/legacy/20.samba-ad.script #!...

Hi Stefan, > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Stefan G. Weichinger via samba > Verzonden: dinsdag 19 februari 2019 10:43 > Aan: samba at lists.samba.org > Onderwerp: Re: [Samba] Debian 9.8 and vanbelle-repos > > Am 18.02.19 um 08:38 schrieb L.P.H. van Belle via samba: > > Goood morning Stefan, ( and