Hello Ace
First off thank you for responding to my question and providing assitance
When we run into this issue ( randomly) its when we add a new 2008 or 2008
R2 server to the domain, we never add in the domain suffix on the server
prior to adding it to the domain, because once the server becomes a member
server of the domain it *should* get this information once added, so because
of this i dont understand the value of adding this information to the server
before it becomes a member of the domain sounds like a lot of extra steps.
The DNS suffix for my domain is corp.mydomain.com and the domain name is the
same. When we run into this error there is nothing in the event logs that
would indicate the server had an issue joining the domain. All machines are
pointing to internal DNS servers, and no DC are multihomed.
The only thing i can think of is we have setup AD so when a user adds a
server to the domain by default the server gets added to an OU (we set this
up for the help because they add the most machines to the domain) we have a
GPO on this OU that sets DNS suffixes for all machines that are in this OU,
we do this because we have 3 seperate DNS suffixes and we want users to be
able to ping the machine without having to apply the FQDN of the name. So i
am wondering if when the server gets added to the OU its picking up one of
these DNS suffixes and thats what is causing the problem
Post by Ace Fekay [MCT]It's not necessary to post your DCs and AD info. It however, does help us
evaluate your infrastructure to offer a more specific response, but that's
ok.
To answer your question, yes, the Schema needs to be updated to R2 prior
to introducing a 2008 R2 DC, but not a member server.
If the Primary DNS Suffix is different than the domain it is a member or
DC of, then that can be changed in the computer's properties. If it
doesn't hold, then that's an indication that something else is going on.
Are there any event log errors?
Are all machines only using the internal DNS in their NIC properties or
are they using an external, router, or ISP DNS address? Are any DCs
multihomed, more than one IP or have RRAS installed? Is the AD DNS Domain
name a single label name (domain vs domain.something)? If so to any of the
questions, then that is cause of concern and issues can arise.
Ace
Post by SawyerThis is a fresh install of windows 2008 R2 on a member server, the server
in question is pointing to two DNS/AD DNS servers one DC is running
windows 2008 and the other is running windows 2003 sp2, they are both
GC's as well. We have 5 DC all of which are DNS servers, all zones are AD
integrated. The AD domain and forest functional levels are at 2003 native
mode, we have not preped the domain for windows 2008 R2, is this a
requirment before we can add 2008 R2 member servers to the domain? The
2008 R2 version is RTM. I would rather not post my internal companys
netbiosname and FQDN is possible
Thanks again for your asstance
Post by unknownHello Sawyer,
According to "The name will remain domainname.com. the error was the
specified serer cannot perform the requested operation." is the server
member of another domain?
Or is it a fresh installed machine, you trying to add as member server
to the domain? How is DNS configured in your domain, how many DNS
servers and how are they located, do you use AD integrated zones?
Do you try to install it directly as DC in the domain and is the schema
upgraded to version 47 from the 2008 R2 disk before?
Please post the FQDN, the Netbios name and the name shown in AD UC.
Is the 2008 R2 the RTM version?
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and
confers no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
Post by SawyerHello all
I am running a 2003 native domain and forest functional mode, i have 6
DC's spread acorss 3 AD sites 5 out of the 6 DC are running Windows
2008 sp1. Recently i have been gettting some complaints regarding
adding Windows 2008 R2 servers to the domain. The user is able to add
the server to the domain, but soon after the computer gets added to
the domain the user gets an error message " "changing the primary
Domain DNS name ofthis computer to "" failed. The name will remain
"domainname.com. the error was the specified serer cannot perform the
requested operation." I can find nothing of relevance on the DC, the
server was using when it was joined to the domain that would help me
figure out what could be causing this issue. I did however look at the
Netsetup log on the 2008R2 server and the only thing of interest is
"NetpldapBind: ldap_bind failed on DCservername: 81: server down"
The rest of the log file looks good no errors or warnings
Thanks for any assistance with this