Windows 2003 server freezes intermittently

[p***@powelldobson.com]

The Windows 2003 server tends to intermittently freeze for over 10-20
seconds at a time at random times. This can be replicated by browsing
the mapped network drives and from Terminal Services but does seem more
severe if browsing from the console d:\

The D:\ folder consist of shares which is around 380Gb and one share is
many folders deep.

1.The server spec is fine - it has 2 Gb and generally over 1 Gb free,
CPU Usage is between above 10% and network util is around 1% however
the server does house around 70 users for file shares the stats tell me
that the server is not under stress.

2. There are no events log entries indicating a problem and the server
is up to date with all drivers with SP1.

3. The D:\ is raid5 (HP Proliant DL380).

4. Anti-Virus has been disabled at various stages so there are no
scanning issues etc . The only thing I need to do now is run some form
of Chkdsk for errors.

I don't know if this is co-incidence (and will need to check) but any
problems seem to be removed with a server reboot at least for a few
days/week. This morning I logged into the server from the console
(after a restart yesterday) browsed the D:\ and almost immediately got
a freeze for about 20 seconds (this freeze was also evident for users
on the network). Logged a call with HP but nothing conclusive.

Any thoughts would be appreciated!

[p***@powelldobson.com]

Sorry should have mentioned that the server is also a DC and file/print

[Frankster]

Post by p***@powelldobson.com
I don't know if this is co-incidence (and will need to check) but any
problems seem to be removed with a server reboot at least for a few
days/week. This morning I logged into the server from the console
(after a restart yesterday) browsed the D:\ and almost immediately got
a freeze for about 20 seconds (this freeze was also evident for users
on the network). Logged a call with HP but nothing conclusive.
Any thoughts would be appreciated!

This type of intermittent behavior is often the result of a dns
misconfiguration. Check that your DC has ONLY itself (and other DCs if you
have 'em) configured into its own TCP/IP properties for its NIC. Next, best
practice is to ensure it has "forwarders" configured into its dns server
(only your ISP DNS IP or your router IP goes in here). Make sure all your
client machines have ONLY (only is very important) your DC(s) IP configured
into their TCP/IP properties for DNS (static or dynamic doesn't matter).

Often, what happens is that someone (mis)configures their ISP-provided DNS
servers into their DNS client, along with their own DC IP (either on their
DC or their client machines). When this is the case, occasionally, when the
dns client is using the ISP DNS, it cannot locate internal resources.
Rebooting (or restarting your own DNS service) often seemingly "corrects"
the problem. But only because it has switched back to using the proper
(local) DNS, until this happens again.

Anyway, just check. This might not be it. Just a thought.

-Frank

[Willard]

Did you ever find the answer for this problem?? I have the same problem.

Post by p***@powelldobson.com
The Windows 2003 server tends to intermittently freeze for over 10-20
seconds at a time at random times. This can be replicated by browsing
the mapped network drives and from Terminal Services but does seem more
severe if browsing from the console d:\
The D:\ folder consist of shares which is around 380Gb and one share is
many folders deep.
1.The server spec is fine - it has 2 Gb and generally over 1 Gb free,
CPU Usage is between above 10% and network util is around 1% however
the server does house around 70 users for file shares the stats tell me
that the server is not under stress.
2. There are no events log entries indicating a problem and the server
is up to date with all drivers with SP1.
3. The D:\ is raid5 (HP Proliant DL380).
4. Anti-Virus has been disabled at various stages so there are no
scanning issues etc . The only thing I need to do now is run some form
of Chkdsk for errors.
I don't know if this is co-incidence (and will need to check) but any
problems seem to be removed with a server reboot at least for a few
days/week. This morning I logged into the server from the console
(after a restart yesterday) browsed the D:\ and almost immediately got
a freeze for about 20 seconds (this freeze was also evident for users
on the network). Logged a call with HP but nothing conclusive.
Any thoughts would be appreciated!

Post by p***@powelldobson.com
Sorry should have mentioned that the server is also a DC and file/print

Post by Frankster
This type of intermittent behavior is often the result of a dns
misconfiguration. Check that your DC has ONLY itself (and other DCs if you
have 'em) configured into its own TCP/IP properties for its NIC. Next, best
practice is to ensure it has "forwarders" configured into its dns server
(only your ISP DNS IP or your router IP goes in here). Make sure all your
client machines have ONLY (only is very important) your DC(s) IP configured
into their TCP/IP properties for DNS (static or dynamic doesn't matter).
Often, what happens is that someone (mis)configures their ISP-provided DNS
servers into their DNS client, along with their own DC IP (either on their
DC or their client machines). When this is the case, occasionally, when the
dns client is using the ISP DNS, it cannot locate internal resources.
Rebooting (or restarting your own DNS service) often seemingly "corrects"
the problem. But only because it has switched back to using the proper
(local) DNS, until this happens again.
Anyway, just check. This might not be it. Just a thought.
-Frank
Submitted via EggHeadCafe
Stock Quotes via jQuery-enabled WCF Service, JSON, and jQuery Templates
http://www.eggheadcafe.com/tutorials/aspnet/9c157185-9ded-4352-8311-73153d9d1297/stock-quotes-via-jqueryenabled-wcf-service-json-and-jquery-templates.aspx

[Peter Foldes]

Poster is gone 5 years ago. You are a deadhead from egghead