Please Help.... Server 2003 and 2008 domain controller problems...

Hi,

I'm replacing servers on my network with with new servers running server
2008. I'm removing the 2 old server 2003 domain controllers. One of them
crashed and I I seized all rolls and removed all records of that server with
ntdsutil. That left me with one 2003 domain controller. I then added 2 new
2008 servers and promoted them to DCs. I transfered all FSMO roles to the
new DCs and made them global catalogs, DNS servers and DHCP servers. I
pointed all DCs to themselves and eachother for DNS. I then tried to demote
the old 2003 DC to a member server to remove it from the network. It fails
with and error that says that the "last domain controller in domain" check
box in not checked, but no other DC could be contacted.

I ran dcdiag....it says that no global catalog could be contacted.....all
GCs are down. replmon showed an error but I think I got that resolved. It
seemed like replication was working, but not 100% sure....brain is mush at
this point.

Exchange 2003 is running on another 2003 server. In Exchange managment
console, it only shows the one 2003 DC as well, nothing about the 2008 DCs.

I looks like a DNS error somewhere, but I can't find the problem.

Forest and Domain functional level are set to 2003.

Please help if anyone has suggestions.

Thanks so much.

Hello DKB,

Make sure the 2003 DC is using the new DNS servers and also that all entries
are listed in the DNS zones. Uncheck the GC on the 2003 DC and try again.

Is the 2003 on the same subnet?

Hi
Ok, first change the DNS config on all DCs. Point the preferred DNS server
to the same DC in all DCs NIC. Then restart netlogon service, after that do
from cmd "dcdiag /fix" in the 3 DCs. Do a manuall replication using repadmin
"repadmin /syncall /A /e /P" or using Active Directory Sites and Services
"NTDSSettings - Connection objects"

Wait a little, and check for errors. Additionally run dcdiag and check for
output errors. Then try again, what are the results?

Yep, 2003 was pointed to the 2008 DC DNS. I uninstalled DNS from the 2003
DC. I unchecked GC on the 2003 DC. I checked the DNS zones, it all looked
good to me. You said "all entries"...which are you referring to? Just want
to make sure I don't miss anything. Yes, it's all on the same subnet.

I'm kicking around the idea of starting fresh with a whole new domain.
Would I be opening an ugly can of worms by doing that?


"Meinolf Weber [MVP-DS]" <meiweb(nospam)@gmx.de> wrote in message
news:ff16fb661ac328cb66368ab28b2c@msnews.microsoft.com...
> Hello DKB,
>
> Make sure the 2003 DC is using the new DNS servers and also that all
> entries are listed in the DNS zones. Uncheck the GC on the 2003 DC and try
> again.
>
> Is the 2003 on the same subnet?
>
> 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
>
>> Hi,
>>
>> I'm replacing servers on my network with with new servers running
>> server 2008. I'm removing the 2 old server 2003 domain controllers.
>> One of them crashed and I I seized all rolls and removed all records
>> of that server with ntdsutil. That left me with one 2003 domain
>> controller. I then added 2 new 2008 servers and promoted them to DCs.
>> I transfered all FSMO roles to the new DCs and made them global
>> catalogs, DNS servers and DHCP servers. I pointed all DCs to
>> themselves and eachother for DNS. I then tried to demote the old 2003
>> DC to a member server to remove it from the network. It fails with
>> and error that says that the "last domain controller in domain" check
>> box in not checked, but no other DC could be contacted.
>>
>> I ran dcdiag....it says that no global catalog could be
>> contacted.....all GCs are down. replmon showed an error but I think I
>> got that resolved. It seemed like replication was working, but not
>> 100% sure....brain is mush at this point.
>>
>> Exchange 2003 is running on another 2003 server. In Exchange
>> managment console, it only shows the one 2003 DC as well, nothing
>> about the 2008 DCs.
>>
>> I looks like a DNS error somewhere, but I can't find the problem.
>>
>> Forest and Domain functional level are set to 2003.
>>
>> Please help if anyone has suggestions.
>>
>> Thanks so much.
>>
>
>

Hello Dan,

You can migrate to a new domain if you like with ADMTv3.1, but why? If you
do not have the real need, because your system is total screwed up or you
have to change to a new domain name, it will be lot more work and testing
needed instead of adding new DC's and removing the old one.

In ESM you have to change manual from the 2003 DC to one of the 2008 DC's
under Recipient update service. Or what do you mean with the Exchange part?
Missed it in the first answer.

As Jorge said, check replication between the DC's. And alos run on all DC's
dcdiag /v and netdiag /v to check for errors.

1) Can you post unedited ipconfig /all for the three dc's, after you take
care of step 3.

2) What is the dns server 1.1.1.1? This is non-functional.

3) Are you using dc's with multiple network cards? If so, you need to make
these all single nic's (Not multihomed).

3a) DC1 has four nic's defined, this is not good these are dc's not
routers, don't use them for both.
3b) DC1a has two nic's defined, disable one of them.
3c) DC2 has two nic's defined, disable one of them.

4) After 3a, 3b and 3c are complete either restart the NetLogon service or
run netdiag /fix on each dc

5) run repadmin /syncall

6) Wait 30 minutes and rerun the diagnostics

Thanks so much for your help so far Paul. Here are answers to your
questions:

1) Ipconfig are pasted below...

2) I read somewhere that all NICs on a DC needed to have an address
assigned. I assigned 1.1.1.1 etc to the unplugged NICs. Not sure how that
IP got to be known as a DNS server.

3 a,b,c) Yes, DCs have multiple network cards. I have disabled the unused
ones. DC2 has one connecting to the LAN and one connecting to a SAN. DC2
is part of my DFS structure and must connect to the SAN as well. DC1A has a
NIC that won't disable...clicking disable does nothing.

4) Done

5) Done

6) New dcdiag output is pasted below the IPconfig output. I noticed it
says Root Zone for this server not found, failed NETLogon test, and other
failures.

I recommend to remove the loopback on DC1. If you don't need IPv6, I would
suggest to uncheck IPv6 and the two Link-layer Discovery options. Make sure
you have a reverse zone created for your IP subnet(s) and set to AD
integrated Forest Wide.

Is the San interface necessary on DC on DC2? Multihomed DCs can cause
numerous issues, as Paul mentioned. I would suggest to use a non-DC for
whatever purpose the SAN connection is used for. If you absolutely need it,
there are ways to force a DC to work properly with multi NICs. I posted
how-to below, along with additional info on multihomed DCs.

I hope this helps.

********************************
Multihomed DCs, DNS, RRAS servers.
By Ace Fekay, Directory Services MVP
+++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++++++++++++++++++++++++++++++++++++++++++++++++++++++

With all due respect, multi-homed DCs are not recommended because of the
associated issues that WILL occur with AD. If using a DC as an internet
access gateway, I recommend purchasing an inexpensive Linksys, DLink, etc,
Cable/DSL router to perform NAT for you, take out the extra NIC off the DC,
but still let the DC handle DHCP (and not the router).

If used for some other reason, I would highly recommend removing the NICs
and apps and use a non-DC for the task.

Little background on AD and DNS:
First, just to get this out of the way, if you have your ISP's DNS addresses
in your IP configuration (DCs and clients), they need to be REMOVED. If the
ISP's DNS is in there, this will cause additional problems. I usually see
errors (GPOs not working, can't find the domain, RPC issues, etc), when the
ISP's DNS servers are listed on a client, DCs and/or member servers, or with
multihomed DCs. If you have an ISP's (or some other outside DNS server or
even using your router as a DNS server) DNS addresses in your IP
configuration (all DCs, member servers and clients), they need to be REMOVED
and ONLY use the internal DNS server(s). This can be very problematic.

More background: AD uses DNS. DNS stores AD's resource and service locations
in the form of SRV records, hence how everything that is part of the domain
will find resources in the domain. If the ISP's DNS is configured in the any
of the internal AD member machines' IP properties, (including all client
machines and DCs), the machines will be asking the ISP's DNS 'where is the
domain controller for my domain?", whenever it needs to perform a function,
(such as a logon request, replication request, querying and applying GPOs,
etc). Unfortunately, the ISP's DNS does not have that info and they reply
with an "I dunno know", and things just fail. Unfortunately, the ISP's (or
your router as a DNS server) DNS doesn't have information or records about
your internal private AD domain, and they shouldn't have that sort of
information.

Also, AD registers certain records in DNS in the form of SRV records that
signify AD's resource and service locations. When there are multiple NICs,
each NIC registers. IF a client, or another DC queries DNS for this DC, it
may get the wrong record. One factor controlling this is Round Robin. If a
DC or client on another subnet that the DC is not configured on queries for
it, Round Robin will kick in offering one or the other. If the wrong one
gets offered, it may not have a route to it. On the other hand, Subnetmask
Priortization will ensure a querying client will get an IP that corresponds
to the subnet it's on, which will work. To insure everything works, stick
with one NIC.

Since this DC is multi-homed, it requires additional configuration to
prevent the public interface addresses from being registered in DNS. This
creates a problem for internal clients locating AD to authenticate and find
other services and resources such as the Global Catalog, file sharing and
the SYSVOL DFS share and can cause GPO errors with Userenv 1000 events to be
logged, authenticating to shares and printers, logging on takes forever,
among numerous other issues.

But if you like, there are some registry changes to eliminate the
registration of the external NIC or simply use the internal networking
routing to allow access. Here's the whole list of manual steps to follow.

Another problem is the DC now becomes part of two Sites. This is another
issue that can be problematic.

But believe me, it's much easier to just get a separate NAT device or
multihome a non-DC then having to alter the DC. If the both NICs are
internal, I would suggest to pick a subnet, team the NICs and allow your
internal routers handle the traffic between subnets - Good luck!

1. Insure that all the NICS only point to your internal DNS server(s) only
and none others, such as your ISP's DNS servers' IP addresses.

2. In Network & Dialup properties, Advanced Menu item, Advanced Settings,
move the internal NIC (the network that AD is on) to the top of the binding
order (top of the list).

3. Disable the ability for the outer NIC to register. The procedure, as
mentioned, involves identifying the outer NIC's GUID number. This link will
show you how:
246804 - How to Enable-Disable Windows 2000 Dynamic DNS Registrations (per
NIC too):
http://support.microsoft.com/?id=246804

4. Disable NetBIOS on the outside NIC. That is performed by choosing to
disable NetBIOS in IP Properties, Advanced, and you will find that under the
"WINS" tab. You may want to look at step #3 in the article to show you how
to disable NetBIOS on the RRAS interfaces if this is a RRAS server.
296379 - How to Disable NetBIOS on an Incoming Remote Access Interface
[Registry Entry]:
http://support.microsoft.com/?id=296379

Note: A standard Windows service, called the "Browser service", provides the
list of machines, workgroup and domain names that you see in "My Network
Places" (or the legacy term "Network Neighborhood"). The Browser service
relies on the NetBIOS service. One major requirement of NetBIOS service is a
machine can only have one name to one IP address. It's sort of a
fingerprint. You can't have two brothers named Darrell. A multihomed machine
will cause duplicate name errors on itself because Windows sees itself with
the same name in the Browse List (My Network Places), but with different
IPs. You can only have one, hence the error generated.

5. Disable the "File and Print Service" and disable the "MS Client Service"
on the outer NIC. That is done in NIC properties by unchecking the
respective service under the general properties page. If you need these
services on the outside NIC (which is unlikely), which allow other machines
to connect to your machine for accessing resource on your machine (shared
folders, printers, etc.), then you will probably need to keep them enabled.

6. Uncheck "Register this connection" under IP properties, Advanced
settings, "DNS" tab.

7. Delete the outer NIC IP address, disable Netlogon registration, and
manually create the required records

a. In DNS under the zone name, (your DNS domain name), delete the outer
NIC's IP references for the "LdapIpAddress". If this is a GC, you will need
to delete the GC IP record as well (the "GcIpAddress"). To do that, in the
DNS console, under the zone name, you will see the _msdcs folder.

Under that, you will see the _gc folder. To the right, you will see the IP
address referencing the GC address. That is called the GcIpAddress. Delete
the IP addresses referencing the outer NIC.
i. To stop these two records from registering that information,
use the steps provided in the links below:
Private Network Interfaces on a Domain Controller Are Registered in DNS
http://support.microsoft.com/?id=295328

ii. The one section of the article that disables these records is
done with this registry entry:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters
(Create this Multi-String Value under it):
Registry value: DnsAvoidRegisterRecords
Data type: REG_MULTI_SZ
Values: LdapIpAddress
GcIpAddress

iii. Here is more information on these and other Netlogon Service records:
Restrict the DNS SRV resource records updated by the Netlogon service
[including GC]:
http://www.microsoft.com/technet/tre...o_rr_in_ad.asp

b. Then you will need to manually create these two records in DNS with
the IP addresses that you need for the DC. To create the LdapIpAddress,
create a new host under the domain, but leave the "hostname" field blank,
and provide the internal IP of the DC, which results in a record that looks
like:
(same as parent) A 192.168.5.200 (192.168.5.200 is used for illustrative
purposes)

i. You need to also manually create the GcIpAddress as well, if
this is a GC. That would be under the _msdcs._gc SRV record under the zone.
It is created in the same fashion as the LdapIpAddress mentioned above.

8. In the DNS console, right click the server name, choose properties, then
under the "Interfaces" tab, force it only to listen to the internal NIC's IP
address, and not the IP address of the outer NIC.

9. Since this is also a DNS server, the IPs from all NICs will register,
even if you tell it not to in the NIC properties. See this to show you how
to stop that behavior (this procedure is for Windows 2000, but will also
work for Windows 2003):
275554 - The Host's A Record Is Registered in DNS After You Choose Not to
Register the Connection's Address:
http://support.microsoft.com/?id=275554

10. If you haven't done so, configure a forwarder. You can use 4.2.2.2 if
not sure which DNS to forward to until you've got the DNS address of your
ISP.
How to set a forwarder? Good question. Depending on your operating
system,choose one of the following articles:

fist of all, for the failed DC you will need to perform "metaData cleanup"
http://technet.microsoft.com/en-us/l.../cc736378.aspx

For the exchange server , check to make sure the TPC/IP properties on the
exchange server is configured correctly, it is set to talk to new 08
DC/DNS/GC
Go to DSAccess tab on the exchange system manager and verify the GC are got
picked up by exchange
Make sure your replication has no errors fix replication issues If there is
any
After metadata cleanup , clean site and services and make sure subnets are
getting assigned to correct domain controller
Make sure the new DC/Gc/DNS servers are in the same site as others (
assuming they are since they are replacement DC's)

if the last DC windows 2003 is giving you hard time and you are un able to
DCpromo out, you can use same method as first failed DC and clean ADDS
database with metadata clean process. I have feeling if you fix your
replication issues you will be able to gracefully DCpromo out the last
windows 2003 DC.
Make sure on the old last win03 DC, point this to one of the windows 2008 as
primary DNS and bounce the win03 DC and check replication and try to DCpromo
out to see what happens.

Configure DNS servers correctly use AD integrated DNS

Some DNs best practices.
http://smtp25.blogspot.com/2009/03/d...practices.html


after all make sure all existing servers on the last DC have been
transferred over to new win 2008 DC's, take care any existing DHCP scope
options, clean Site and services, Clean metadata, Run DCDiag on the DC's to
make sure they are happy and replication is occurring with no complains.

good luck
oz


--
Oz Casey Dedeal
Systems Engineer
MVP - (Exchange)
MCITP (EMA) ,MCITP(EA),MCITP(SA),
MCSE 2003| M+| S+ | MCDST
Security+|Project+| Server+|

oz@SMTp25.org
http://smtp25.blogspot.com (Blog)
http://telnet25.wordpress.com/ (Blog)

"DKB" <none@none.none> wrote in message
news:C94E4C4C-C613-415C-9732-6C06FB9FE28D@microsoft.com...
> Hi,
>
> I'm replacing servers on my network with with new servers running server
> 2008. I'm removing the 2 old server 2003 domain controllers. One of them
> crashed and I I seized all rolls and removed all records of that server
> with ntdsutil. That left me with one 2003 domain controller. I then
> added 2 new 2008 servers and promoted them to DCs. I transfered all FSMO
> roles to the new DCs and made them global catalogs, DNS servers and DHCP
> servers. I pointed all DCs to themselves and eachother for DNS. I then
> tried to demote the old 2003 DC to a member server to remove it from the
> network. It fails with and error that says that the "last domain
> controller in domain" check box in not checked, but no other DC could be
> contacted.
>
> I ran dcdiag....it says that no global catalog could be contacted.....all
> GCs are down. replmon showed an error but I think I got that resolved.
> It seemed like replication was working, but not 100% sure....brain is mush
> at this point.
>
> Exchange 2003 is running on another 2003 server. In Exchange managment
> console, it only shows the one 2003 DC as well, nothing about the 2008
> DCs.
>
> I looks like a DNS error somewhere, but I can't find the problem.
>
> Forest and Domain functional level are set to 2003.
>
> Please help if anyone has suggestions.
>
> Thanks so much.