Internal domain name same as external domain - DNS issues!!
-
@Dashrender said:
That's true, didn't think of that, but there's expense if you spin up a VM, plus I have no idea how to get a secure connection back to your office.
Yes, not free, but you can spin it down whenever.
Any normal VPN option works. IPSec, OpenVPN, Pertino, ZeroTier...
-
@scottalanmiller said:
@Our-Tech-Team said:
I've never used or worked with Samba so dont know anything about it. The AD I thought was great for them as they want to have more 'control' over users, add more security to the network and manage permissions on folders much better. I'm familiar with AD so thought it would suit them well.
Samba is just as much AD as Microsoft's DC is. Both are AD, just one is done from an open source project and one from Microsoft. It's not that Samba is not AD as well.
Samba is NOT AD. AD is a complete architecture including LDAP, DNS, and various other items. Samba functions in the old "Domain Controller" method, a single list of usernames and passwords in which to authenticate against. In AD, there is no DC, there are Global Catalogs. Domain controller emulation, a part of the FSMO roles, is not necessary to run and is only there for backwards compatibility. In an AD environment, Samba can function as a PDC emulator, but it cannot hold other GC roles, so it becomes kind of useless.
To the end user, they are functionally the same. To the admin, they are very different.
-
@PSX_Defector said:
Samba is NOT AD. AD is a complete architecture including LDAP, DNS, and various other items. Samba functions in the old "Domain Controller" method, a single list of usernames and passwords in which to authenticate against. In AD, there is no DC, there are Global Catalogs. Domain controller emulation, a part of the FSMO roles, is not necessary to run and is only there for backwards compatibility. In an AD environment, Samba can function as a PDC emulator, but it cannot hold other GC roles, so it becomes kind of useless.
To the end user, they are functionally the same. To the admin, they are very different.
Are you thinking of Samba from long ago before AD was implemented? Samba used to be that way, but Windows used to be that way too. Samba is full AD and has been for quite a long time now. LDAP, Kerberos, DNS, all there. (DNS is handled externally, of course, just like on Windows.)
-
Here is information on how to get the FSMO roles moved between Samba servers.
https://wiki.samba.org/index.php/Transfering_/_seizing_FSMO_roles
I assure you, Samba is full AD.
-
@scottalanmiller said:
@PSX_Defector said:
Samba is NOT AD. AD is a complete architecture including LDAP, DNS, and various other items. Samba functions in the old "Domain Controller" method, a single list of usernames and passwords in which to authenticate against. In AD, there is no DC, there are Global Catalogs. Domain controller emulation, a part of the FSMO roles, is not necessary to run and is only there for backwards compatibility. In an AD environment, Samba can function as a PDC emulator, but it cannot hold other GC roles, so it becomes kind of useless.
To the end user, they are functionally the same. To the admin, they are very different.
Are you thinking of Samba from long ago before AD was implemented? Samba used to be that way, but Windows used to be that way too. Samba is full AD and has been for quite a long time now. LDAP, Kerberos, DNS, all there. (DNS is handled externally, of course, just like on Windows.)
Yes, I know what 4 introduced, but it's still not functionally AD. It can be put in as a member controller, but god help you if you try to move FSMO roles to it. At best, it can be considered pseudo-Active Directory. If you only have Samba controllers, hell it might work. Never tried it by itself with multiple controllers functioning like AD. Although I can't imagine it is that indifferent than standard LDAP. I just know better than to mix the types together.
-
@PSX_Defector said:
If you only have Samba controllers, hell it might work.
that's the normal way to use it. Mixing it in would just be weird. Lots of companies run on just it, it works great from what I hear. I've never heard of a shop that had issues after moving to it. It's full AD with all the bells and whistles. You can even manage it from Windows and GPOs work great too.
-
As far as I know FSMO roles (operations masters) are a windows only thing, and aren't even needed for LDAP, Group Policy/File replication, NTP sync, etc. It's something Microsoft put on top of it.
-
@Jason said:
As far as I know FSMO roles (operations masters) are a windows only thing, and aren't even needed for LDAP, Group Policy/File replication, NTP sync, etc. It's something Microsoft put on top of it.
I believe that that is true. But Samba replicated them too.
-
@scottalanmiller said:
@Jason said:
As far as I know FSMO roles (operations masters) are a windows only thing, and aren't even needed for LDAP, Group Policy/File replication, NTP sync, etc. It's something Microsoft put on top of it.
I believe that that is true. But Samba replicated them too.
if the goal was to manage Windows endpoints, I'm sure the FSMO roles were needed in the implementation for compatibility.
-
@scottalanmiller said:
@PSX_Defector said:
If you only have Samba controllers, hell it might work.
that's the normal way to use it. Mixing it in would just be weird. Lots of companies run on just it, it works great from what I hear. I've never heard of a shop that had issues after moving to it. It's full AD with all the bells and whistles. You can even manage it from Windows and GPOs work great too.
I saw somewhere online someone set up an environment that way and used RSAT from a Windows 7 computer to do GPO and users/computers.
