DNS-Snap In slow after transfering DNS to Windows Server 2003

[Robert Kettel]

In our current Active Directory with DNS on a Windows 2000 Server (not
Active Directory integrated) we installed a Windows 2003 DNS Server. This
one is now running as a primary DNS Server with another 2003 DNS Server as a
secondary. The Windows 2000 DNS Server was removed. A strange thing happens
now: If you connect to DNS from a 2000 Professional Workstation with the
adminpak installed via DNS-Snap In, the DNS configuration (a zone with 3000
records) loads very fast (1 second). If you do the same thing directly from
the console of the Windows 2003 server (or via terminal session), it lasts
up to 3 minutes (!) until all records show up. It doesn't matter, wether you
connect to the Primary or Secondary. There is no load on the servers.
Any ideas, if Windows 2003 DNS has problems with DNS zones, that were
formerly created and hosted on a Windows 2003 DNS Server?

Thanx for help

Robert Kettel

[TJ Campana [MSFT]]

--------------------
>From: "Robert Kettel" <robert...@hotmail.com>
>Subject: DNS-Snap In slow after transfering DNS to Windows Server 2003
>Date: Sat, 10 Apr 2004 20:51:34 +0200
>Lines: 18
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
>Message-ID: <#mscZzyH...@TK2MSFTNGP12.phx.gbl>
>Newsgroups: microsoft.public.windows.server.dns
>NNTP-Posting-Host: p3EE208A8.dip0.t-ipconnect.de 62.226.8.168
>Path: cpmsftngxa06.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.phx.gbl
>Xref: cpmsftngxa06.phx.gbl microsoft.public.windows.server.dns:7402
>X-Tomcat-NG: microsoft.public.windows.server.dns

Robert,

The slow zone load only happens when you are connected to the actual 2003 Server either at the console or using a Terminal Server connection?
Connections using the admin pack are fine! I have seen an issue similar to this that was only able to be reproed on particular hardware and it was
happening with Windows 2000 so I have not seen this on 2003.

Could you provide some additional information regarding the hardware that you are running. Single or Multiple Proc, brand and model. etc?

T.J. Campana [MSFT]
Microsoft EPS Networking
--
This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.

[Robert Kettel]

It is a single domain, that was once inplace-upgraded from
a NT4 domain. The domain is now in Windows 2000 native
mode. There are running 2 DNS-Servers with Windows 2003
OS, which are Domain Controller and WINS-Server as well.
DNS is not active directory integrated. All domain
controllers (3x) are running with Windows 2003 OS. No
sites, no site replication, no DNS delegations.

>.
>

[TJ Campana [MSFT]]

>It is a single domain, that was once inplace-upgraded from
>a NT4 domain. The domain is now in Windows 2000 native
>mode. There are running 2 DNS-Servers with Windows 2003
>OS, which are Domain Controller and WINS-Server as well.
>DNS is not active directory integrated. All domain
>controllers (3x) are running with Windows 2003 OS. No
>sites, no site replication, no DNS delegations.
>

Hardware? Is this a Compaqu DL380 gx with multiple procs? If i remember correctly this is the only hardware that i could repro this issue on. That is not to
say that this issue the issue, just looking for more data on the issue.

TJ

[Robert Kettel]

2 of the servers are ProLiant DL360 G3, one is a ProLiant DL320. All are
single processor machines.
Any ideas?

Robert Kettel

"TJ Campana [MSFT]" <tcam...@online.microsoft.com> schrieb im Newsbeitrag
news:7M0MeCjI...@cpmsftngxa06.phx.gbl...