I've recently come across the same situation, while migrating a 3.0.33
PDC host to 3.6.9. I had renamed the old host some time ago from LANYARD
to TACS-DC. The old host still functions fine, except for not being able
to get its own SID.
Old DC host:
[root@tacs-dc samba]# net getdomainsid
On 08/26/2013 01:21 PM, Eric Shubert wrote:
I'm guessing that adding a TACS-DC record to the old host would fix the
problem of not being able to get its SID.
This appears to work now.
I'm also guessing that adding a LANYARD record to the new host *might*
make it recognize that it's a domain
Hello,
I recently noticed a problem on our PDC (samba 3.0.32
on SLES 10 SP2) which I kind of know how to solve after
web research but I am unclear about the possible
consequences for our domain and clients.
The situation is this:
Originally samba was set up on this machine to test. Back
then its
