In news:01a001c35085$64192db0$(E-Mail Removed),
Shantu Roy <(E-Mail Removed)> posted their concerns
Then Kevin made his reply below:
> Hi all,
> Hope you could help with this issue I am having...
> I am having problems with adding machines to a AD domain.
> The machine I have is win2k+sp4, new install. When
> running dcdiag, it fails on the fsmo check with the error:
> DcGetDcName(PDC_REQUIRED) call failed, error 1355. Also I
> cannot add any new machines to the domain. Looking at the
> AD tree, the machine is registered as a domain
> controller. When doing nslookup queries for srv records,
> they appear correct. I have verified that the info in
> netlogon.dns is the same as the dns info on the AD box. So
> needless to say, I am pulling my hair out. Any ideas
> would be greatly appreciated....
The first DC must *only* point to its own private (not loopback) address
that has File Sharing and Client for Microsoft Networks bound to. Allow
dynamic updates must be "Yes" until all machines are joined to the domain
and have permission to update DNS. Then you can set Allow dynamic updates to
"Secure updates only"
The second DC must point to the first DC for DNS then to itself secondary.
All clients must point only to the DC(s) that has DNS installed
--
Best regards,
Kevin D4 Dad Goodknecht Sr. [MVP]
Hope This Helps
============================
http://www.lonestaramerica.com/
============================
--
When responding to posts, please "Reply to Group" or
"Reply All" via your newsreader so that others may learn
and benefit from your issue
==========================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
==========================================
Keep a back up of your OE settings and folders with
OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
==========================================