Werbung: SecurityConsole.de verwaltet Ihre Computer mit Security Essentails aus der Cloud!
30 Tage kostenfrei testen und 20% Rabatt für Ihre Bestellung mit Promocode: WBF2685582
(Promocode gültig bis 31.12.2011)

Group:  English: Windows Server » microsoft.public.windows.server.dns
Thread: FRS/DNS/RPC after joining 2003 Servers on 2000 domain

HTVi
TV Discussion Newsgroups

FRS/DNS/RPC after joining 2003 Servers on 2000 domain
Dennis Procopio 6/11/2007 8:01:01 PM
I added 2 new 2003 domain controllers to our domain, leaving 2 existing 2000
servers as DC's until flaws and dependencies are identified. One of the 2003
DC's (DC3) has been made an AD-Integrated DNS server, and the other (DC4) has
inherited the WINS and DHCP services as I moved them from one of the 2000
servers (DC2). DNS is also running on DC1 (also a 2000 server).

One of the 2000 domain controllers (DC2) seems to be losing communication
with the new DNS server (DC3). It can ping it one minute, and the next can't
even resolve it's fqdn. When I added the 2003 servers I moved all FSMO roles
to DC3. When doing a dcdiag on the entire site , DC3 reports back errors in
the system log with event id 0x00000457. I don't see anything weird with the
other domain controllers. DC3 reports event id 2088 for source domain
controller DC2. DC2 also complains about not locating the global catalog
when trying to use AD Users and Computers. I've also seen errors about RPC
and DNS but cannot seem to locate them right now. I did have to make a
registry adjustment about a month or more back on the rpcprotocol portion of
the dns server in the registry because of the flaw in MS DNS Server...is that
the problem?

I'd like to be sure that DC3 has a healthy AD & DNS installation before
demoting the 2000 servers. Any help on completing this would be awesome.

Thanks!


Re: FRS/DNS/RPC after joining 2003 Servers on 2000 domain
"Kevin D. Goodknecht Sr. [MVP]" <admin[ at ]nospam.WFTX.US> 6/12/2007 1:23:48 PM
Read inline please.

In news:DD1DDEDE-79A8-4C62-BDA2-E0004D8B277F[ at ]microsoft.com,
Dennis Procopio <DennisProcopio[ at ]discussions.microsoft.com> typed:
[Quoted Text]
> I added 2 new 2003 domain controllers to our domain, leaving 2
> existing 2000 servers as DC's until flaws and dependencies are
> identified. One of the 2003 DC's (DC3) has been made an
> AD-Integrated DNS server, and the other (DC4) has inherited the WINS
> and DHCP services as I moved them from one of the 2000 servers (DC2).
> DNS is also running on DC1 (also a 2000 server).
>
> One of the 2000 domain controllers (DC2) seems to be losing
> communication with the new DNS server (DC3). It can ping it one
> minute, and the next can't even resolve it's fqdn. When I added the
> 2003 servers I moved all FSMO roles to DC3. When doing a dcdiag on
> the entire site , DC3 reports back errors in the system log with
> event id 0x00000457. I don't see anything weird with the other
> domain controllers. DC3 reports event id 2088 for source domain
> controller DC2. DC2 also complains about not locating the global
> catalog when trying to use AD Users and Computers. I've also seen
> errors about RPC and DNS but cannot seem to locate them right now. I
> did have to make a registry adjustment about a month or more back on
> the rpcprotocol portion of the dns server in the registry because of
> the flaw in MS DNS Server...is that the problem?
>
> I'd like to be sure that DC3 has a healthy AD & DNS installation
> before demoting the 2000 servers. Any help on completing this would
> be awesome.

You should make all DCs DNS servers and Global Catalogs. For best
redundancy, each site should have two of each.

How To Create or Move a Global Catalog in Windows Server 2003, Windows 2000,
or Small Business Server 2000:
http://support.microsoft.com/default.aspx?scid=kb;en-us;313994


--
Best regards,
Kevin D. Goodknecht Sr. [MVP]
Hope This Helps

===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
http://support.wftx.us/
http://message.wftx.us/
===================================
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
===================================


Re: FRS/DNS/RPC after joining 2003 Servers on 2000 domain
Dennis Procopio 6/12/2007 1:34:02 PM
Okay. All are GC's but not DNS servers, I'll do that next.

"Kevin D. Goodknecht Sr. [MVP]" wrote:

[Quoted Text]
> Read inline please.
>
> In news:DD1DDEDE-79A8-4C62-BDA2-E0004D8B277F[ at ]microsoft.com,
> Dennis Procopio <DennisProcopio[ at ]discussions.microsoft.com> typed:
> > I added 2 new 2003 domain controllers to our domain, leaving 2
> > existing 2000 servers as DC's until flaws and dependencies are
> > identified. One of the 2003 DC's (DC3) has been made an
> > AD-Integrated DNS server, and the other (DC4) has inherited the WINS
> > and DHCP services as I moved them from one of the 2000 servers (DC2).
> > DNS is also running on DC1 (also a 2000 server).
> >
> > One of the 2000 domain controllers (DC2) seems to be losing
> > communication with the new DNS server (DC3). It can ping it one
> > minute, and the next can't even resolve it's fqdn. When I added the
> > 2003 servers I moved all FSMO roles to DC3. When doing a dcdiag on
> > the entire site , DC3 reports back errors in the system log with
> > event id 0x00000457. I don't see anything weird with the other
> > domain controllers. DC3 reports event id 2088 for source domain
> > controller DC2. DC2 also complains about not locating the global
> > catalog when trying to use AD Users and Computers. I've also seen
> > errors about RPC and DNS but cannot seem to locate them right now. I
> > did have to make a registry adjustment about a month or more back on
> > the rpcprotocol portion of the dns server in the registry because of
> > the flaw in MS DNS Server...is that the problem?
> >
> > I'd like to be sure that DC3 has a healthy AD & DNS installation
> > before demoting the 2000 servers. Any help on completing this would
> > be awesome.
>
> You should make all DCs DNS servers and Global Catalogs. For best
> redundancy, each site should have two of each.
>
> How To Create or Move a Global Catalog in Windows Server 2003, Windows 2000,
> or Small Business Server 2000:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;313994
>
>
> --
> Best regards,
> Kevin D. Goodknecht Sr. [MVP]
> Hope This Helps
>
> ===================================
> When responding to posts, please "Reply to Group"
> via your newsreader so that others may learn and
> benefit from your issue, to respond directly to
> me remove the nospam. from my email address.
> ===================================
> http://www.lonestaramerica.com/
> http://support.wftx.us/
> http://message.wftx.us/
> ===================================
> 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
> ===================================
>
>
>

Home | Search | Terms | Imprint Contact
Newsgroups Reader - provided by WiredBox.Net
Suche nach Orten, Städten, Postleitzahlen, Vorwahlen, Kfz-Kennzeichen