similar to: Replace SBS2003 with Samba4

Anastasios, I've done exactly what you want to do, only starting from SBS2008. Our office went down this road in 2014 when we investigated upgrading from SBS2008 only to find that MS replacement, Server Essentials, did not support Exchange. We currently have a "no cloud" policy, so going to Office 365, as you have done, was not an option (and btw, have you not considered Server

On Sun Apr 28 03:42:51 2024 Rowland Penny via samba <samba at lists.samba.org> wrote: > > 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)

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

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: >

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 > >

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 (/etc/resolv.conf) /etc/hosts: 192.168.1.60 mail.hprs.local mail smb.conf, dns forwarder: 192.168.1.1 Production IPs: DC: 192.168.0.2 Gateway:

I've been using bind9 and DHCP on Samba 4.1.0 thru 4.1.17 and Slackware 64 14.1 for many months now in a production environment and it works just fine. There are a few tweaks here and there to get bind/dhcp to play nicely with Samba ... Note, conf file locations are Slackware, but you'll know where the same thing goes in your distro. In the examples below, my Domain IP range is

Thanks for the info, At the moment, I don't have more than 1 DC, but I am planning on doing the bind master/slave thing thing soon using the Linux webserver host. With failover, I don't see why that wouldn't work with multiple DCs (but of course haven't tried yet). In any case, our AD/DC also hosts mail and redirected folders do if it goes down we've got big problem anyway --

I'm trying to figure out the user.group of my domain administrator account. getent gives me: # getent passwd Administrator HPRS\administrator:*:0:100::/home/HPRS/administrator:/bin/false If I chown a file: chown HPRS\\administrator.100 thisfile I get: # ls -l thisfile -rwxrwx---+ 1 root users 68973 2022-08-08 09:12 thisfile If I do the same for normal domain users: # chown

"Ah, but what if you have Unix clients" I do have Unix clients. They work just fine. The Samba AD/DC is the DHCP server. The Windows and Linux clients get their IP addresses and everyone can see all the hosts on the domain. for example: >From the domain controller (host name MAIL) $ host mark # mark is a Windows 7 workstation MARK.hprs.local has address 192.168.0.55 $ host

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

When I took over as the IT guy in September, there were 2 separate locations with different domains each managed by a SBS 2003 machine. The connection between them was an OpenVPN tunnel. The network was fine and one could see 2 domains in the network. Local and Local2 are working names. From a workstation on Local one could see Local2 in the Microsoft Windows Network, and vice versa from Local2

On 08/26/2015 03:50 PM, Rowland Penny wrote: > On 26/08/15 20:39, Robert Moskowitz wrote: >> >> >> On 08/26/2015 03:26 PM, Rowland Penny wrote: >>> On 26/08/15 20:14, Robert Moskowitz wrote: >>>> One of the Centos 7 arm developers built the sernet 4.2 for me to >>>> start testing. >>>> >>>>

I've configured a secondary slave nameserver based on what I consider rather expert advice, but it's not working as expected. I'm trying to determine if I've done something wrong with basic configuration or if there are AD/DC nuances afoot. The main nameserver is the domain Active Directory/Domain Controller running Samba 4.4.16 on Slackware64 14.2. This has been running for a few

If I had time I would be all over this - but IMHO the main problem is that Dovecot != Exchange.? Even in small environments - unless I'm out of date, there's no calendar, tasks or contact lists within Dovecot. Your next best best is to use something like Horde that would allow you to auth via ActiveSync (on Outlook 2013 clients) and manage everything else that the users will want, with

Luis, I had mentioned that I first provisioned a Samba4 DC 10 years ago when migrating from Windows Small Business Server. At that time I did try, Zental and Debian before Slackware. Back then Debian did not work well. I had to install lots of additional packages and things like Microsoft Update and Remote Desktop just wouldn't work. I spent months trying various things. I started over with

Comments interspersed with yours ... --Mark -----Original Message----- > Date: Sun, 06 Sep 2015 20:00:11 -0500 > From: Rick Romero <rick at havokmon.com> > To: dovecot at dovecot.org > Subject: Re: How to "Windows Authenticate" > > Hmm. I would expect to see 'mark at hprs.com'. Whatever your full domain > name is. Full user at domain would be

On Sat, 20 Jan 2024 20:31:31 -0500 Mark Foley via samba <samba at lists.samba.org> wrote: > 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,

Hello, I provisioned an samba AD with the bind_dlz option. So far so good. Followed the samba wiki. I have a DNS for our external access services (website, moodle, etc) and I'm using it as a forwarder to AD but it is not working. In a win7 I configured the AD IP as primary DNS and put it in the domain. When I try to access, for example, "wiki.samba.org" it opens normally, but when

Hi Tim Andrew and Rowland, Thanks for taking the time to look into this. On Fri, 22 Jun 2018, Tim Beale via samba wrote: > Hi Tom, > > The problem here is due to fundamental implementation differences in the > way Windows and Samba store linked attributes. Your DB is likely fine > (no corruptions). That is great to hear! > During replication (i.e. the join), Windows can