similar to: Joining Windows 10 Domain Member to Samba AD/DC

Displaying 20 results from an estimated 6000 matches similar to: "Joining Windows 10 Domain Member to Samba AD/DC"

2023 Dec 06
2
Provisioning new AD Domain Controller
On Wed, 06 Dec 2023 09:45:13 -0500 Mark Foley via samba <samba at lists.samba.org> wrote: > I have provisioned a new DC with Samba 4.18.5. This DC is intended to > replace an older one in my AD domain. > > The old/current DC has a number of Group Policies set. Can I "rsync" > /var/lib/samba/sysvol/hprs.local/policies/ to my new >
2023 Dec 19
1
Joining Windows 10 Domain Member to Samba AD/DC
On Tue, 19 Dec 2023 15:46:24 -0500 Mark Foley via samba <samba at lists.samba.org> wrote: > I've moved my new DC from one location to another test location > within the office where it will be deployed. The new test location > connects to subnet 192.168.0.1 rather than 192.168.0 as I used when > doing the initial setup. > > I've been going through the wiki
2023 Dec 15
2
Joining Windows 10 Domain Member to Samba AD/DC
On Fri, 15 Dec 2023 02:36:33 -0500 Mark Foley via samba <samba at lists.samba.org> wrote: > On Thu Dec 14 22:49:33 2023 Mark Foley via samba > <samba at lists.samba.org> wrote: > > > > On Thu Dec 14 19:27:29 2023 Matt Savin <matt at tegers.com> wrote: > > > I do not know who 'Matt Savin' is, but would he please reply to the list and not
2023 Dec 19
1
Joining Windows 10 Domain Member to Samba AD/DC
I've moved my new DC from one location to another test location within the office where it will be deployed. The new test location connects to subnet 192.168.0.1 rather than 192.168.0 as I used when doing the initial setup. I've been going through the wiki verifying zones, rDNS, etc. On the A record test I get: # host -t A dc1.hprs.locl dc1.hprs.locl has address 192.168.0.2
2023 Dec 06
1
Provisioning new AD Domain Controller
I have provisioned a new DC with Samba 4.18.5. This DC is intended to replace an older one in my AD domain. The old/current DC has a number of Group Policies set. Can I "rsync" /var/lib/samba/sysvol/hprs.local/policies/ to my new /var/lib/samba/sysvol/hprs.locl/Policies/ per https://wiki.samba.org/index.php/SysVol_replication_(DFS-R), or will I have to manually create policies in the
2023 Dec 06
1
Provisioning new AD Domain Controller
On Tue Dec 5 05:18:37 2023 Rowland Penny via samba <samba at lists.samba.org> wrote: > > On Sun, 03 Dec 2023 18:10:03 -0500 > Mark Foley via samba <samba at lists.samba.org> wrote: > > > Before attempting to join domain members with my newly provisioned > > AD/DC, there are some difference between this new smb.conf and the > > one from the current DC
2023 Dec 03
1
Provisioning new AD Domain Controller
Before attempting to join domain members with my newly provisioned AD/DC, there are some difference between this new smb.conf and the one from the current DC running Samba 4.8.2. Please advise if I need any of these: [global] server services = s3fs, rpc, nbt, wrepl, ldap, cldap, kdc, drepl,winbind, ntp_signd, kcc, dnsupdate ntlm auth = yes winbind use default domain = yes template shell =
2024 Jan 18
1
Provisioning new AD Domain Controller
On Thu Jan 18 14:11:45 2024 Sonic <sonicsmith at gmail.com> wrote: > > hosts file? stale dns records? I listed my hosts file in my first message: 127.0.0.1 localhost 192.168.1.60 mail.hprs.local mail Since I had provisioned initially with the SAMBA_INTERNAL DNS backend, and therefore Samba manages DNS, I thought perhaps there was a "stale dns", so
2023 Dec 05
1
Provisioning new AD Domain Controller
On Sun, 03 Dec 2023 18:10:03 -0500 Mark Foley via samba <samba at lists.samba.org> wrote: > Before attempting to join domain members with my newly provisioned > AD/DC, there are some difference between this new smb.conf and the > one from the current DC running Samba 4.8.2. Please advise if I need > any of these: > > [global] > server services = s3fs, rpc, nbt, wrepl,
2023 Dec 20
1
Joining Windows 10 Domain Member to Samba AD/DC
On Tue Dec 19 19:30:36 2023 "Samba @ Pegasusnz" <samba at pegasusnz.com> wrote: > > The zone is the domain e.g. hprs.locl > And the name is the name of the item you want to delete e.g. dc1 Thanks! That did it. --Mark > > On 20/12/2023, at 11:32?AM, Mark Foley via samba <samba at lists.samba.org> wrote: > > > > On Tue Dec 19 16:00:39 2023 Rowland
2024 Jan 05
2
Joining Windows 10 Domain Member to Samba AD/DC
On 05.01.2024 1:28, Mark Foley via samba wrote: > I've added a Windows 10 domain member to my Domain. I'm now following the > procedure in https://wiki.samba.org/index.php/Time_Synchronisation#Configuring_Time_Synchronisation_on_a_Windows_Domain_Member. > > I've created the Group Policy for the "Time Sources". This doesn't seem to be > working. This did
2024 Jan 05
3
Joining Windows 10 Domain Member to Samba AD/DC
I've added a Windows 10 domain member to my Domain. I'm now following the procedure in https://wiki.samba.org/index.php/Time_Synchronisation#Configuring_Time_Synchronisation_on_a_Windows_Domain_Member. I've created the Group Policy for the "Time Sources". This doesn't seem to be working. This did work fine with my old 4.8.2 DC, so I know it works in principle. I have
2024 Jan 18
1
Joining Windows 10 Domain Member to Samba AD/DC
On Thu Jan 18 10:52:55 2024 Sonic <sonicsmith at gmail.com> wrote: > > I'm with Luis in thinking that the fault is with the DC and not the > clients. I recently switched from using a GPO to set the time source to > using the "natural" time sync with the DC at one site due to the fact that > I was running the DC in a container which due to age could not run a
2024 Jan 16
3
Joining Windows 10 Domain Member to Samba AD/DC
After trying all the suggestions in the below listed excerpts from this thread, I've taken time since my last posting on January 6th to continue this issue with the Microsoft forum: https://learn.microsoft.com/en-us/answers/questions/1480474/unable-to-time-sync-with-domain-controller?page=1&orderby=helpful&comment=answer-1411748#newest-answer-comment I likewise had no solution
2024 Jan 20
2
Provisioning new AD Domain Controller
On Sat, 20 Jan 2024 15:44:18 -0500 Mark Foley via samba <samba at lists.samba.org> wrote: > After provisioning and testing my new DC offline, I now want to move > it into production. This means changing IPs. > > DC FQDN: mail.hprs.local > > IPs for setup/testing: > > DC: 192.168.1.60 > Gateway: 192.168.1.1 (Netgear router) > DNS: 192.168.1.60
2024 Jan 21
1
Provisioning new AD Domain Controller
On Sat Jan 20 16:28:14 2024 Rowland Penny via samba <samba at lists.samba.org> wrote: > > On Sat, 20 Jan 2024 15:44:18 -0500 > Mark Foley via samba <samba at lists.samba.org> wrote: > > > After provisioning and testing my new DC offline, I now want to move > > it into production. This means changing IPs. > > > > DC FQDN: mail.hprs.local > >
2024 Apr 28
1
Joining Linux Domain Member to Samba DC, issues
I've successfully joined two Linux Domain Members to two different Domains. Now, I'm joining a second Linux host as a Domain Member to a Samba4 (4.18.9) Domain. I'm having some possible issues this time. Issue #1 Reverse Zone On the SambaWiki: https://wiki.samba.org/index.php/Setting_up_Samba_as_a_Domain_Member, under 2.5 Forward Lookup, no problem: # host mail mail.hprs.local has
2019 Mar 04
2
getent not working after installing firewall
On Mon, 4 Mar 2019 17:18:31 +0000 Rowland Penny wrote: > > On Mon, 04 Mar 2019 11:48:00 -0500 > Mark Foley via samba <samba at lists.samba.org> wrote: > > > On Mon, 4 Mar 2019 14:50:38 +0000 Rowland Penny wrote: > > > > > > On Mon, 04 Mar 2019 09:15:12 -0500 > > > Mark Foley via samba <samba at lists.samba.org> wrote: > > > >
2019 Mar 04
4
getent not working after installing firewall
On Mon, 4 Mar 2019 18:31:07 +0000 From: Rowland Penny wrote: > > On Mon, 04 Mar 2019 12:58:17 -0500 > Mark Foley via samba <samba at lists.samba.org> wrote: > > > On Mon, 4 Mar 2019 17:18:31 +0000 Rowland Penny wrote: > > > > > > On Mon, 04 Mar 2019 11:48:00 -0500 > > > Mark Foley via samba <samba at lists.samba.org> wrote: > > >
2024 Apr 28
1
Joining Linux Domain Member to Samba DC, issues
On Sat, 27 Apr 2024 20:38:34 -0400 Mark Foley via samba <samba at lists.samba.org> wrote: > I've successfully joined two Linux Domain Members to two different > Domains. Now, I'm joining a second Linux host as a Domain Member to a > Samba4 (4.18.9) Domain. I'm having some possible issues this time. > > Issue #1 Reverse Zone > > On the SambaWiki: >