All links are from Google" Mac join NT Domain"…
I read them before post the link ?!?
About the *nix way, it’s about share. thank to highlight this point, it’s important.
I was imagining that with the NethServer AD, it was the same thing, but perhaps it’s not
AD is a M$ implementation of ldap/kerberos (and dns/ntp): in linux’s world, you can have it via samba4 (not available in NS)
NT style domain is quite different… no ldap or kerberos…
so, if you try to join a mac/windows client to an AD domain using NS, you won’t be able to do it and likely won’t find anything on server side, since the client is failing to find the suitable services.
@zamboni, it seem that there a misunderstood somewhere.
The situation is the below:
There a Nethserver instance with the AD service running on it.
There’s windows stations that connect without problems. @Paulo_Rodrigues want a Mac join the AD service.
On a NethServer Instance, the AD service work like a PDC, a NT Domain.
A Mac can connect to a NT domain without lot of problem.
no, there’s a NT style DC running, service provided by samba.
there’s NO AD running on NS, full stop
are you sure? any link? (a recent one, please)
OSX supports AD domains, and Apple dropped support to samba (OSX don’t use samba anymore to provide smb shares, but it relies on a proprietary smb daemon)
I might be wrong, and I’d like you to tell OP the exact steps to join your mac to a NS domain…
using the onboard utilities DON’T work, because OSX expect to deal with an AD server.