Performance

Hello

Please can you assist with the following:

I have Server 2003, with exchange 2003 and SQL 2005, and I hae been
expereicing performance issues for a while now.

These are the problems we are experiencing:

When we logon in out PC it take a few minutes for the PC to load the network
setting etc and before this used to take well under a minute.
Our outlook connection to exchange is being constantly lost and reconnected.
From time to time we have to wait for the network drives and folder to
display it contents.
When we are using out accounting system we get write delays errors to the
server.
If I connect to the server using remote destop I get connection lost and the
remote desktop keeps trying to reconnect.

The most common problem is the delays in loging on and accessing the shared
drives/folder, but from time to time we experience all of the problems at
once, especially after we reboot the server.

These problems started at the end of last year. I downloaded in installed
server 2003 SP2 which solved the problems. However after a shutdown and
restarted the server last week due to power maintance the problems are back.
I have done a windows update which did not solved my problems, and I have
also checke for virus. I have also updated the nic drivers to the latest
available drivers.

Can you post an un edited IPconfig /all from one of the affected computers?


DDS

"Zak" <> wrote in message
news:676687C9-8B37-4B1E-AD7C-...
> Hello
>
> Please can you assist with the following:
>
> I have Server 2003, with exchange 2003 and SQL 2005, and I hae been
> expereicing performance issues for a while now.
>
> These are the problems we are experiencing:
>
> When we logon in out PC it take a few minutes for the PC to load the
> network
> setting etc and before this used to take well under a minute.
> Our outlook connection to exchange is being constantly lost and
> reconnected.
> From time to time we have to wait for the network drives and folder to
> display it contents.
> When we are using out accounting system we get write delays errors to the
> server.
> If I connect to the server using remote destop I get connection lost and
> the
> remote desktop keeps trying to reconnect.
>
> The most common problem is the delays in loging on and accessing the
> shared
> drives/folder, but from time to time we experience all of the problems at
> once, especially after we reboot the server.
>
> These problems started at the end of last year. I downloaded in installed
> server 2003 SP2 which solved the problems. However after a shutdown and
> restarted the server last week due to power maintance the problems are
> back.
> I have done a windows update which did not solved my problems, and I have
> also checke for virus. I have also updated the nic drivers to the latest
> available drivers.
>

Hello

See below, I think the problem is on the server, as when the problem occurs
i can ping other pc and ther server from any of the pc, but i can't ping the
pc's router or printers from the server.

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 . . . . . . . . . . . : 196.25.1.11
196.43.1.11
192.168.0.1
Primary WINS Server . . . . . . . : 192.168.0.1
Lease Obtained. . . . . . . . . . : 16 April 2009 08:01:23 AM
Lease Expires . . . . . . . . . . : 17 April 2009 08:01:23 AM

DNS Servers . . . . . . . . . . . : 196.25.1.11
> 196.43.1.11
> 192.168.0.1


Actually this is your problem. I am assuming that 192.168.0.1 is your Domain
controller /DHCP/DNS server?

If so this is the only server you should assign to your clients for DNS. I'm
guessing 196.25.1.11 and 196.43.1.11 are your ISP's DNS servers?

If so they should NEVER be listed on an AD client or you will see exactly
the problems you are experiencing. The only place on an AD domain your ISP's
DNS servers should be listed is as a forwarder on the DNS server.

See:
Setting Up the Domain Name System for Active Directory
http://support.microsoft.com/default...b;en-us;237675

Best Practices for DNS Client settings in Windows 2000 server and in Windows
Server 2003
http://support.microsoft.com/default...b;en-us;825036

How to configure DNS for Internet access in Windows Server 2003
http://support.microsoft.com/default...b;en-us;323380

hth
DDS


"Zak" <> wrote in message
news:E375553C-59D5-4CDE-9B21-...
> Hello
>
> See below, I think the problem is on the server, as when the problem
> occurs
> i can ping other pc and ther server from any of the pc, but i can't ping
> the
> pc's router or printers from the server.
>
> 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 . . . . . . . . . . . : 196.25.1.11
> 196.43.1.11
> 192.168.0.1
> Primary WINS Server . . . . . . . : 192.168.0.1
> Lease Obtained. . . . . . . . . . : 16 April 2009 08:01:23 AM
> Lease Expires . . . . . . . . . . : 17 April 2009 08:01:23 AM
>
>

Hello Danny

Basically my problem is that my ISP DNS IPs which is been distributed
throught the DHCP, and all I need to do is set up a fordward with these
address?

Before you answer, remember the gateway of 192.168.0.2 is our router.

Zak

Yes. You don't want your AD clients using any other DNS server except for
the DNS server setup for the AD domain.

Basic AD DNS setup is install DNS on the domain controller and point the DC
to itself in the properties of TCP/IP. Use hte actual IP address not
127.0.0.1. This allows the DC to register the SRV record the AD clients must
find in order to "find" the domain. Point all AD clients to the DNS server
setup for the AD domain ONLY. Servers are AD clients also.
For internet access configure forwarders on your AD DNS server and list your
ISP's DNS servers as the forwarder.

Any resources on the AD domain the client needs is found in the DNS zone on
the DC. (that is why all AD clinets ate pointed to this DNS zone so they can
register their DNS record for other clients to find and so they can fild AD
resources.

If it is not found in your AD DNS zone (the entire internet) it is sent to
the default gateway and out to be resolved by you ISP's DNS server.

I'm surprised your Domain was working at all. Your AD Domain controller
server was pointed to your ISP's DNS servers. It must register its SRV
record in DNS so the clients can find the domain. Your ISP probably does not
allow you to register your SRV recxords on their server nor do you want your
private SRV record being registered on a public DNS server for the world to
find.


hth
DDS

"Zak" <> wrote in message
news:54D76C38-4DC7-41E2-9F19-...
> Hello Danny
>
> Basically my problem is that my ISP DNS IPs which is been distributed
> throught the DHCP, and all I need to do is set up a fordward with these
> address?
>
> Before you answer, remember the gateway of 192.168.0.2 is our router.
>
> Zak
>

Hello Danny

Thank you for you assistance, it is much appricated.

I have settup the forwards for the ISP DNS, and I have removed the ISP DNS
from the DHCP.

On another note, have have been using this configuration of IP Address since
March 2006, and when I changed the server to the current one about a year
ago, i used the same config.

Once again, thank you for you help, should I experience any problems
tomorrow I will post a reply.

Zak

"Danny Sanders" wrote:

> Yes. You don't want your AD clients using any other DNS server except for
> the DNS server setup for the AD domain.
>
> Basic AD DNS setup is install DNS on the domain controller and point the DC
> to itself in the properties of TCP/IP. Use hte actual IP address not
> 127.0.0.1. This allows the DC to register the SRV record the AD clients must
> find in order to "find" the domain. Point all AD clients to the DNS server
> setup for the AD domain ONLY. Servers are AD clients also.
> For internet access configure forwarders on your AD DNS server and list your
> ISP's DNS servers as the forwarder.
>
> Any resources on the AD domain the client needs is found in the DNS zone on
> the DC. (that is why all AD clinets ate pointed to this DNS zone so they can
> register their DNS record for other clients to find and so they can fild AD
> resources.
>
> If it is not found in your AD DNS zone (the entire internet) it is sent to
> the default gateway and out to be resolved by you ISP's DNS server.
>
> I'm surprised your Domain was working at all. Your AD Domain controller
> server was pointed to your ISP's DNS servers. It must register its SRV
> record in DNS so the clients can find the domain. Your ISP probably does not
> allow you to register your SRV recxords on their server nor do you want your
> private SRV record being registered on a public DNS server for the world to
> find.
>
>
> hth
> DDS
>
> "Zak" <> wrote in message
> news:54D76C38-4DC7-41E2-9F19-...
> > Hello Danny
> >
> > Basically my problem is that my ISP DNS IPs which is been distributed
> > throught the DHCP, and all I need to do is set up a fordward with these
> > address?
> >
> > Before you answer, remember the gateway of 192.168.0.2 is our router.
> >
> > Zak
> >
>

Hello Danny

Things were looking good this morning, however all the problems as back.

Is there anything else that we cah do?

Zak

Try this article:
http://support.microsoft.com/kb/219289

then on a client run ipconfig /flushdns and do some testing to see if that
clears things up. I'm guessing you have a lot of DNS records in your AD zone
that are not valid.'

hth
DDS

"Zak" <> wrote in message
news:8971A647-75CC-40BE-A335-...
> Hello Danny
>
> Things were looking good this morning, however all the problems as back.
>
> Is there anything else that we cah do?
>
> Zak
>
>

Hi Danny

I have the repair as per the KB and did the ipconfig /flushdns on all the
pc, and everything has being fine since.

However yesterday there was a power failure here by and I had to shutdown
the server. The power only can back up last night and this morning when I
restarted the server and the problems are back.

NB: I shutdown the server before the UPS ran out of backup power.

Is there anything else I can try.

Zak