Issues with 2008 R2 server taking over as DC after 2003 SBS server fails.
A couple of months ago I added our 2008 R2 server as a DC to our domain controlled by our 2003 SBS server. Everything appeared fine, and AD was replicating; however, the 2003 server has now crashed, and the 2008 server will not process domain logins consistently. Also, I try to access Active Directory Users and Computers, I am met with:
"Naming information cannot be located because: The specified domain either does not exist or could not be contacted. contact your administrator to verify that your domain is properly configured and is currently online."
I can sometimes choose Change Domain by right clicking, and the old 2003 and 2008 DC's show up, with 2008 showing online. If I choose the 2008 server, services begin working again. However, only sometimes the server shows up, and manually entering it does not work. When it does show up in the list, and I choose the 2008 server, the connection only lasts for 20-30 minutes, and then then I am back to no logins and administrative functions giving me the error above. Any help is greatly appreciated.
"Naming information cannot be located because: The specified domain either does not exist or could not be contacted. contact your administrator to verify that your domain is properly configured and is currently online."
I can sometimes choose Change Domain by right clicking, and the old 2003 and 2008 DC's show up, with 2008 showing online. If I choose the 2008 server, services begin working again. However, only sometimes the server shows up, and manually entering it does not work. When it does show up in the list, and I choose the 2008 server, the connection only lasts for 20-30 minutes, and then then I am back to no logins and administrative functions giving me the error above. Any help is greatly appreciated.
Last Comment
SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
I checked DNS and the 2008 server has its IP (and not 127.0.01) as the primary DNS.
Prior to posting, I did run ntdsutil and seized the roles, but I will verify the roles per #2.
I will do step #3 as well, as I had not done this.
Thank you.
Prior to posting, I did run ntdsutil and seized the roles, but I will verify the roles per #2.
I will do step #3 as well, as I had not done this.
Thank you.
ASKER
Here is what I get when I check the FSMO roles. I had to check them using ntdsutil, because I cannot get Active Directory Sites and Services to come up, because I get the same error as above:
"Naming information cannot be located because: The specified domain either does not exist or could not be contacted........"
C:\Users\administrator.TCO
ntdsutil: roles
fsmo maintenance: connections
server connections: connect to server application
Binding to application ...
Connected to application using credentials of locally logged on user.
server connections: q
fsmo maintenance: Select operation target
select operation target: List roles for connected server
Server "application" knows about 5 roles
Schema - CN=NTDS Settings,CN=APPLICATION,CN
N=Sites,CN=Configuration,D
Naming Master - CN=NTDS Settings,CN=APPLICATION,CN
-Name,CN=Sites,CN=Configur
PDC - CN=NTDS Settings,CN=APPLICATION,CN
ites,CN=Configuration,DC=T
RID - CN=NTDS Settings,CN=APPLICATION,CN
ites,CN=Configuration,DC=T
Infrastructure - CN=NTDS Settings,CN=TCOAT-SBS,CN=S
-Site-Name,CN=Sites,CN=Con
select operation target:
"Naming information cannot be located because: The specified domain either does not exist or could not be contacted........"
C:\Users\administrator.TCO
ntdsutil: roles
fsmo maintenance: connections
server connections: connect to server application
Binding to application ...
Connected to application using credentials of locally logged on user.
server connections: q
fsmo maintenance: Select operation target
select operation target: List roles for connected server
Server "application" knows about 5 roles
Schema - CN=NTDS Settings,CN=APPLICATION,CN
N=Sites,CN=Configuration,D
Naming Master - CN=NTDS Settings,CN=APPLICATION,CN
-Name,CN=Sites,CN=Configur
PDC - CN=NTDS Settings,CN=APPLICATION,CN
ites,CN=Configuration,DC=T
RID - CN=NTDS Settings,CN=APPLICATION,CN
ites,CN=Configuration,DC=T
Infrastructure - CN=NTDS Settings,CN=TCOAT-SBS,CN=S
-Site-Name,CN=Sites,CN=Con
select operation target:
What are the names of the servers (SBS and 2008)?
ASKER
The hostnames are "Application" (thats the 2008) and "TREFFERTUSA-SBS" (the 2003 SBS that crashed)
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
This may be unrelated but I know is SBS 2011 you need to be running priemum edition in order to have another server on the network and believe there is something similar with SBS 2003 as well.
That's incorrect compdigit44 - there is nothing in any version of SBS that stops you running another server on the domain.
The restrictions with SBS is that the SBS server MUST hold all the FSMO roles. Other than that, you can install as many other servers as you like in the domain.
The restrictions with SBS is that the SBS server MUST hold all the FSMO roles. Other than that, you can install as many other servers as you like in the domain.
ASKER
Thank you all for the input. A Dell software engineer has resolved the issue. There were some old DNS entries that pointed to the 2003 server, and some missing items in the SYSVOL folder. Those were resolved, the SBS 2003 server was shutdown, and now we seem to be working normally.
Thank you for the clarification Alan Hardisty... I learned something myself....
Windows Server 2003
Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).
129K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
ASKER
DCDIAG.txt