Prev: [Samba] PDC: System SID missing / inconsistent with domain SID
Next: [Samba] Samba 3.3.12/3.4.7/3.5.2 on "ancient" server stops responding/dies
From: Wikked one on 29 Apr 2010 09:20
got a tricky task set out for me. Were
using CentOS 4.8 as a Samba Domain Controller (3.0.33) yes I know its
ancient,but its solid. I need to update this to a version that will support
Windows7 work stations using domain security. Im pretty sure I can bring the
Samba versions up to 3.3.12 (Ill be performing the task on a virtual machine
as a test) but heres my question. In the past concerning a domain controller Ive
noticed that it takes a substaintial period of time for the domain to recognize
the freshly built domain controller. Is
there something that I can do to decrease this time?
The New Busy is not the old busy. Search, chat and e-mail from your inbox.
To unsubscribe from this list go to the following URL and read the