Trouble promoting additional Domain Controller in existing domain
i am having trouble promoting an additional DC at one of our sites. the site currently has an existing DC. i have DNS pointing first to the local site DC and secondary to hub location, and tried with both DNS pointing to hub DC. after going through the dcpromo wizard the configuration of AD begins for a few moments then errors out with the following error:
The operation failed because:
Active Direcotry could not create the NTDS Settings object for this domain controller CN=(FQDN of my DC) on the remote domain controller (my existing site DC). Ensure the provided network credentials have sufficient permissions.
"The data area passed to a system call is too small."
Now, of course i immediately thought of my rights. i double-checked for sanity's sake - i am still a Domain Admin (noone changed my rights). Another engineer with Domain Admin tried it as well and got the same issue.
i can't find anything with Google to answer this sufficiently. Any ideas as to what this error is pointing to?
The operation failed because:
Active Direcotry could not create the NTDS Settings object for this domain controller CN=(FQDN of my DC) on the remote domain controller (my existing site DC). Ensure the provided network credentials have sufficient permissions.
"The data area passed to a system call is too small."
Now, of course i immediately thought of my rights. i double-checked for sanity's sake - i am still a Domain Admin (noone changed my rights). Another engineer with Domain Admin tried it as well and got the same issue.
i can't find anything with Google to answer this sufficiently. Any ideas as to what this error is pointing to?
ASKER
yea, the server was already on the domain.
good point on the time possibility, it is set via GPO but i'll check it.
i know DNS is good as i set the A record yesterday and it has successfully replicated to that site since yesterday as there were no failures for replication this morning, so there should be no issue.
i'll check the time and post any errors i see in the logs. back in a few.
good point on the time possibility, it is set via GPO but i'll check it.
i know DNS is good as i set the A record yesterday and it has successfully replicated to that site since yesterday as there were no failures for replication this morning, so there should be no issue.
i'll check the time and post any errors i see in the logs. back in a few.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
found the issue ourselves after discussion in the office. advise given was sound, but in the end evaluated and fixed ourselves. thank you for the attention.
Also comapre the Time zone and Time with the PDC.
Do NSLOOKUP on the server and check if it works.Post if any event in the Server.