Network Connection

Hello

Please can you assit with following:

From last December I have been experiencing network connection problem on my
network using Server 2003 and Exchange 2003 SP2. At first the problem
occured once in a while but after a month it started to happen more often.
These problems included outlook connecting and disconnecting, slow logon to
client, delays in accesing shared drives, delayed wirte to our account system
which is shared from the server and lost is connection to remote desktop. I
upgraded
the server to SP2 and install the updated to disable the SNP and the TCP
Offload, this solved the problem for a short while.

In March this year the errors reappeared, this time the problems were
resolved by running netdiag /fix and ipconfig /flushdns.

On Monday I had to shut down the server due to power failure which lasted
longer that UPS battery and we booted the sever up on Tuesday morning the
problem reoccured. I have ran the netdiag /fix again and all that have happen
is the we experience the problem for about 30min about 4 to 5 times a day.
These problem are been experienced by all out client pc some with Vista and
the rest with XP.

Hello Zak,

For the clients make sure that you use following policy to prevent logon
with cached credentials:
Computer Configuration\Administrative Templates\System\Logon "Always wait
for network at computer startup and logon"

Additional post an unedited ipconfig /all from the DC/DNS server and a problem
machine so we can exclude DNS configuration problems.

You should also make sure on all machines that the latest SP and patches
are installed.

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


> Hello
>
> Please can you assit with following:
>
> From last December I have been experiencing network connection problem
> on my
> network using Server 2003 and Exchange 2003 SP2. At first the problem
> occured once in a while but after a month it started to happen more
> often.
> These problems included outlook connecting and disconnecting, slow
> logon to
> client, delays in accesing shared drives, delayed wirte to our account
> system
> which is shared from the server and lost is connection to remote
> desktop. I
> upgraded
> the server to SP2 and install the updated to disable the SNP and the
> TCP
> Offload, this solved the problem for a short while.
> In March this year the errors reappeared, this time the problems were
> resolved by running netdiag /fix and ipconfig /flushdns.
>
> On Monday I had to shut down the server due to power failure which
> lasted longer that UPS battery and we booted the sever up on Tuesday
> morning the problem reoccured. I have ran the netdiag /fix again and
> all that have happen is the we experience the problem for about 30min
> about 4 to 5 times a day. These problem are been experienced by all
> out client pc some with Vista and the rest with XP.
>

Hello Meinolf

I have check the clients PC and enabled the "Always wait for network at
computer startup and logon". All PC have the latest SP, the last update was
run on the 14/04/2009 and all the PCs are 100% up to day according to the
WSUS.

I am going to run another update this weekend and below are the IPconfig,
first one is from the DC/DNS and the second from my PC:

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Administrator>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : anza-server1
Primary Dns Suffix . . . . . . . : ANZA.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : ANZA.local

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : ANZA.local
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection
Physical Address. . . . . . . . . : 00-15-17-26-67-88
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.2
DNS Servers . . . . . . . . . . . : 192.168.0.1

C:\Documents and Settings\Administrator>

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Zakaria.ANZA>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : anza2
Primary Dns Suffix . . . . . . . : ANZA.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : ANZA.local
ANZA.local

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : ANZA.local
Description . . . . . . . . . . . : VIA Rhine II Fast Ethernet Adapter
Physical Address. . . . . . . . . : 00-1A-4D-22-12-76
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.10
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.2
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
Primary WINS Server . . . . . . . : 192.168.0.1
Lease Obtained. . . . . . . . . . : 08 May 2009 08:11:40 AM
Lease Expires . . . . . . . . . . : 09 May 2009 08:11:40 AM

C:\Documents and Settings\Zakaria.ANZA>

Hello Zak,

The ipconfig output looks ok. For the policy run gpupdate /force on the client,
reboot or wait the refresh time which can be between 90-120 minutes.

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


> Hello Meinolf
>
> I have check the clients PC and enabled the "Always wait for network
> at computer startup and logon". All PC have the latest SP, the last
> update was run on the 14/04/2009 and all the PCs are 100% up to day
> according to the WSUS.
>
> I am going to run another update this weekend and below are the
> IPconfig, first one is from the DC/DNS and the second from my PC:
>
> Microsoft Windows [Version 5.2.3790]
> (C) Copyright 1985-2003 Microsoft Corp.
> C:\Documents and Settings\Administrator>ipconfig /all
>
> Windows IP Configuration
>
> Host Name . . . . . . . . . . . . : anza-server1
> Primary Dns Suffix . . . . . . . : ANZA.local
> Node Type . . . . . . . . . . . . : Hybrid
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
> DNS Suffix Search List. . . . . . : ANZA.local
> Ethernet adapter Local Area Connection:
>
> Connection-specific DNS Suffix . : ANZA.local
> Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network
> Connection
> Physical Address. . . . . . . . . : 00-15-17-26-67-88
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.0.1
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.0.2
> DNS Servers . . . . . . . . . . . : 192.168.0.1
> C:\Documents and Settings\Administrator>
>
> Microsoft Windows XP [Version 5.1.2600]
> (C) Copyright 1985-2001 Microsoft Corp.
> C:\Documents and Settings\Zakaria.ANZA>ipconfig /all
>
> Windows IP Configuration
>
> Host Name . . . . . . . . . . . . : anza2
> Primary Dns Suffix . . . . . . . : ANZA.local
> Node Type . . . . . . . . . . . . : Hybrid
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
> DNS Suffix Search List. . . . . . : ANZA.local
> ANZA.local
> Ethernet adapter Local Area Connection:
>
> Connection-specific DNS Suffix . : ANZA.local
> Description . . . . . . . . . . . : VIA Rhine II Fast Ethernet
> Adapter
> Physical Address. . . . . . . . . : 00-1A-4D-22-12-76
> Dhcp Enabled. . . . . . . . . . . : Yes
> Autoconfiguration Enabled . . . . : Yes
> IP Address. . . . . . . . . . . . : 192.168.0.10
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.0.2
> DHCP Server . . . . . . . . . . . : 192.168.0.1
> DNS Servers . . . . . . . . . . . : 192.168.0.1
> Primary WINS Server . . . . . . . : 192.168.0.1
> Lease Obtained. . . . . . . . . . : 08 May 2009 08:11:40 AM
> Lease Expires . . . . . . . . . . : 09 May 2009 08:11:40 AM
> C:\Documents and Settings\Zakaria.ANZA>
>

"Zak" <(E-Mail Removed)> wrote in message
news:BE35FD76-5E6D-4CE8-8CD0-(E-Mail Removed)...
> Hello Meinolf
>
> I have check the clients PC and enabled the "Always wait for network at
> computer startup and logon". All PC have the latest SP, the last update
> was
> run on the 14/04/2009 and all the PCs are 100% up to day according to the
> WSUS.
>
> I am going to run another update this weekend and below are the IPconfig,
> first one is from the DC/DNS and the second from my PC:
>
> Microsoft Windows [Version 5.2.3790]
> (C) Copyright 1985-2003 Microsoft Corp.
>
> C:\Documents and Settings\Administrator>ipconfig /all
>
> Windows IP Configuration
>
> Host Name . . . . . . . . . . . . : anza-server1
> Primary Dns Suffix . . . . . . . : ANZA.local
> Node Type . . . . . . . . . . . . : Hybrid
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
> DNS Suffix Search List. . . . . . : ANZA.local
>
> Ethernet adapter Local Area Connection:
>
> Connection-specific DNS Suffix . : ANZA.local
> Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network
> Connection
> Physical Address. . . . . . . . . : 00-15-17-26-67-88
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.0.1
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.0.2
> DNS Servers . . . . . . . . . . . : 192.168.0.1
>
> C:\Documents and Settings\Administrator>
>
> Microsoft Windows XP [Version 5.1.2600]
> (C) Copyright 1985-2001 Microsoft Corp.
>
> C:\Documents and Settings\Zakaria.ANZA>ipconfig /all
>
> Windows IP Configuration
>
> Host Name . . . . . . . . . . . . : anza2
> Primary Dns Suffix . . . . . . . : ANZA.local
> Node Type . . . . . . . . . . . . : Hybrid
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
> DNS Suffix Search List. . . . . . : ANZA.local
> ANZA.local
>
> Ethernet adapter Local Area Connection:
>
> Connection-specific DNS Suffix . : ANZA.local
> Description . . . . . . . . . . . : VIA Rhine II Fast Ethernet
> Adapter
> Physical Address. . . . . . . . . : 00-1A-4D-22-12-76
> Dhcp Enabled. . . . . . . . . . . : Yes
> Autoconfiguration Enabled . . . . : Yes
> IP Address. . . . . . . . . . . . : 192.168.0.10
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.0.2
> DHCP Server . . . . . . . . . . . : 192.168.0.1
> DNS Servers . . . . . . . . . . . : 192.168.0.1
> Primary WINS Server . . . . . . . : 192.168.0.1
> Lease Obtained. . . . . . . . . . : 08 May 2009 08:11:40 AM
> Lease Expires . . . . . . . . . . : 09 May 2009 08:11:40 AM
>
> C:\Documents and Settings\Zakaria.ANZA>
>
>


Are there any event log errors on the DCs or clients?
What apps and services are installed on the DC?
What AV are you using?


Usually hardware is the last thing we think of. But in this case, I must
ask, how is the switch? Have you tried changing the port the server is
plugged in to? How about the Exchange server? Change ports, too, or is that
installed on the DC (not recommended due to performance conflicts and drive
controller settings differences between the DC's requirements and changes it
makes to the controller, and Exchange's requirements).

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSA Messaging, MCT
Microsoft Certified Trainer
(E-Mail Removed)

For urgent issues, you may want to contact Microsoft PSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

"Efficiency is doing things right; effectiveness is doing the right
things." - Peter F. Drucker
http://twitter.com/acefekay

Hello Meinolf

I have updated the clients and the server this weekend, and also updated the
group policy on all the clients. And My Problems still exists.

Ace, currently we are using Symantec EndPoint MR3, I have checked the
Hardware, I have replaced the switch, changed ports on the switch and server,
used teh second available network point and othing resolved the problems.
Also we currntly only have one server and we are five users. The server is
our DC and has Exchange, WSUS 3.0 SP1 and our Accounting software.

I have checked the error log, the client have no error and I found the
following on the server. These error start around the time I began to
experiencing the problem last year till when I repaired the DNS last month.
Before and after that there are no errors.

Error 4521

Event Type: Warning
Event Source: DNS
Event Category: None
Event ID: 4521
Date: 2009/04/16
Time: 05:41:17 PM
User: N/A
Computer: ANZA-SERVER1
Description:
The DNS server encountered error 32 attempting to load zone Internet from
Active Directory. The DNS server will attempt to load this zone again on the
next timeout cycle. This can be caused by high Active Directory load and may
be a transient condition.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Error 4004

Event Type: Error
Event Source: DNS
Event Category: None
Event ID: 4004
Date: 2009/04/04
Time: 10:32:11 PM
User: N/A
Computer: ANZA-SERVER1
Description:
The DNS server was unable to complete directory service enumeration of zone
ANZA.local. This DNS server is configured to use information obtained from
Active Directory for this zone and is unable to load the zone without it.
Check that the Active Directory is functioning properly and repeat
enumeration of the zone. The extended error debug information (which may be
empty) is "". The event data contains the error.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 2a 23 00 00 *#..

Error 4015

Event Type: Error
Event Source: DNS
Event Category: None
Event ID: 4015
Date: 2009/04/04
Time: 10:32:11 PM
User: N/A
Computer: ANZA-SERVER1
Description:
The DNS server has encountered a critical error from the Active Directory.
Check that the Active Directory is functioning properly. The extended error
debug information (which may be empty) is "". The event data contains the
error.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 51 00 00 00 Q...

Error 6702

Event Type: Error
Event Source: DNS
Event Category: None
Event ID: 6702
Date: 2008/11/18
Time: 03:41:38 PM
User: N/A
Computer: ANZA-SERVER1
Description:
DNS server has updated its own host (A) records. In order to ensure that
its DS-integrated peer DNS servers are able to replicate with this server, an
attempt was made to update them with the new records through dynamic update.
An error was encountered during this update, the record data is the error
code.

If this DNS server does not have any DS-integrated peers, then this error
should be ignored.

If this DNS server's Active Directory replication partners do not have the
correct IP address(es) for this server, they will be unable to replicate with
it.

To ensure proper replication:
1) Find this server's Active Directory replication partners that run the DNS
server.
2) Open DnsManager and connect in turn to each of the replication partners.
3) On each server, check the host (A record) registration for THIS server.
4) Delete any A records that do NOT correspond to IP addresses of this
server.
5) If there are no A records for this server, add at least one A record
corresponding to an address on this server, that the replication partner can
contact. (In other words, if there multiple IP addresses for this DNS
server, add at least one that is on the same network as the Active Directory
DNS server you are updating.)
6) Note, that is not necessary to update EVERY replication partner. It is
only necessary that the records are fixed up on enough replication partners
so that every server that replicates with this server will receive (through
replication) the new data.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 2a 23 00 00 *#..

Hello Zak,

What is the zone "internet" in event id 4521? Make sure your server and clients
are registered correct in the ANZA.local zone. Are the servers DHCP client
services set to automatic and are started? Needed for correct DNS registration/update.

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


> Hello Meinolf
>
> I have updated the clients and the server this weekend, and also
> updated the group policy on all the clients. And My Problems still
> exists.
>
> Ace, currently we are using Symantec EndPoint MR3, I have checked the
> Hardware, I have replaced the switch, changed ports on the switch and
> server, used teh second available network point and othing resolved
> the problems. Also we currntly only have one server and we are five
> users. The server is our DC and has Exchange, WSUS 3.0 SP1 and our
> Accounting software.
>
> I have checked the error log, the client have no error and I found the
> following on the server. These error start around the time I began to
> experiencing the problem last year till when I repaired the DNS last
> month. Before and after that there are no errors.
>
> Error 4521
>
> Event Type: Warning
> Event Source: DNS
> Event Category: None
> Event ID: 4521
> Date: 2009/04/16
> Time: 05:41:17 PM
> User: N/A
> Computer: ANZA-SERVER1
> Description:
> The DNS server encountered error 32 attempting to load zone Internet
> from
> Active Directory. The DNS server will attempt to load this zone again
> on the
> next timeout cycle. This can be caused by high Active Directory load
> and may
> be a transient condition.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
> Error 4004
>
> Event Type: Error
> Event Source: DNS
> Event Category: None
> Event ID: 4004
> Date: 2009/04/04
> Time: 10:32:11 PM
> User: N/A
> Computer: ANZA-SERVER1
> Description:
> The DNS server was unable to complete directory service enumeration of
> zone
> ANZA.local. This DNS server is configured to use information obtained
> from
> Active Directory for this zone and is unable to load the zone without
> it.
> Check that the Active Directory is functioning properly and repeat
> enumeration of the zone. The extended error debug information (which
> may be
> empty) is "". The event data contains the error.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 2a 23 00 00 *#..
> Error 4015
>
> Event Type: Error
> Event Source: DNS
> Event Category: None
> Event ID: 4015
> Date: 2009/04/04
> Time: 10:32:11 PM
> User: N/A
> Computer: ANZA-SERVER1
> Description:
> The DNS server has encountered a critical error from the Active
> Directory.
> Check that the Active Directory is functioning properly. The extended
> error
> debug information (which may be empty) is "". The event data contains
> the
> error.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 51 00 00 00 Q...
> Error 6702
>
> Event Type: Error
> Event Source: DNS
> Event Category: None
> Event ID: 6702
> Date: 2008/11/18
> Time: 03:41:38 PM
> User: N/A
> Computer: ANZA-SERVER1
> Description:
> DNS server has updated its own host (A) records. In order to ensure
> that
> its DS-integrated peer DNS servers are able to replicate with this
> server, an
> attempt was made to update them with the new records through dynamic
> update.
> An error was encountered during this update, the record data is the
> error
> code.
> If this DNS server does not have any DS-integrated peers, then this
> error should be ignored.
>
> If this DNS server's Active Directory replication partners do not have
> the correct IP address(es) for this server, they will be unable to
> replicate with it.
>
> To ensure proper replication: 1) Find this server's Active Directory
> replication partners that run the DNS server. 2) Open DnsManager and
> connect in turn to each of the replication partners. 3) On each
> server, check the host (A record) registration for THIS server. 4)
> Delete any A records that do NOT correspond to IP addresses of this
> server. 5) If there are no A records for this server, add at least one
> A record corresponding to an address on this server, that the
> replication partner can contact. (In other words, if there multiple
> IP addresses for this DNS server, add at least one that is on the same
> network as the Active Directory DNS server you are updating.) 6) Note,
> that is not necessary to update EVERY replication partner. It is only
> necessary that the records are fixed up on enough replication partners
> so that every server that replicates with this server will receive
> (through replication) the new data.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 2a 23 00 00 *#..

"Zak" <(E-Mail Removed)> wrote in message
news:3D9AB415-A26D-4B08-8789-(E-Mail Removed)...
> Hello Meinolf
>
> I have updated the clients and the server this weekend, and also updated
> the
> group policy on all the clients. And My Problems still exists.
>
> Ace, currently we are using Symantec EndPoint MR3, I have checked the
> Hardware, I have replaced the switch, changed ports on the switch and
> server,
> used teh second available network point and othing resolved the problems.
> Also we currntly only have one server and we are five users. The server is
> our DC and has Exchange, WSUS 3.0 SP1 and our Accounting software.
>
> I have checked the error log, the client have no error and I found the
> following on the server. These error start around the time I began to
> experiencing the problem last year till when I repaired the DNS last
> month.
> Before and after that there are no errors.

I am curious as Meinolf, what is the zone called "Internet" that the error
message is indicating?

Also, how is your Forwarder setup? What is it pointing to?

Ace

The zone call internet was a mistake and has no configuration on it.

Basically when configured by very first Server 2003 as a DC for a client
some years back, I had no internet connectivity so I added the ISP DNS IPs on
to the DHCP and distributed them to the Clients PCs and I had internet. So
everytime I setted up a new server if I had no internet connection I would
distribute the ISP DNS using DHCP.

Now if you go back to my orginal post I mentioned about a month ago I
repairded the DNS on my server which resolved the problem. I repaired the DNS
becaued my server was setup in the same manner using DHCP to distribut the
ISP DNS to our clients for internet and while searching on the internet I
found a few KBs which said that the ISP DNS IP needed to be in a forwarded.

I have read a few KBs about configuring a DNS for internet AD and clients
etc and I followed http://support.microsoft.com/kb/323380/en-us

I removed the ISP DNS from the DHCP and I started at step 3 of the KB hence
the internet zone. Thats how there is an internet zone. It is a primary zone
and I tried to delete it but I could not find it.

The forwarder has both the ISP DNS IPs only, also all the PCs are registered
to the correct ANZA.local. and the DHCP services is set to automatic and
started.

Hello Zak,

Step 3 is for configuring the basic DNS setting in your domain. So in your
case it has been ANZA.local. So remove the "internet" zone if exist, there
is no need for.

If you have removed the "." (root) zone you can configure the forwarders
with the ISP/s DNS server. And as you said the domain machines should only
use the domain DNS server, this one forwards all request it can not answer
to the ISP's DNS server.

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


> The zone call internet was a mistake and has no configuration on it.
>
> Basically when configured by very first Server 2003 as a DC for a
> client some years back, I had no internet connectivity so I added the
> ISP DNS IPs on to the DHCP and distributed them to the Clients PCs and
> I had internet. So everytime I setted up a new server if I had no
> internet connection I would distribute the ISP DNS using DHCP.
>
> Now if you go back to my orginal post I mentioned about a month ago I
> repairded the DNS on my server which resolved the problem. I repaired
> the DNS becaued my server was setup in the same manner using DHCP to
> distribut the ISP DNS to our clients for internet and while searching
> on the internet I found a few KBs which said that the ISP DNS IP
> needed to be in a forwarded.
>
> I have read a few KBs about configuring a DNS for internet AD and
> clients etc and I followed
> http://support.microsoft.com/kb/323380/en-us
>
> I removed the ISP DNS from the DHCP and I started at step 3 of the KB
> hence the internet zone. Thats how there is an internet zone. It is a
> primary zone and I tried to delete it but I could not find it.
>
> The forwarder has both the ISP DNS IPs only, also all the PCs are
> registered to the correct ANZA.local. and the DHCP services is set to
> automatic and started.
>