Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

NT4 Server hangs

Status
Not open for further replies.
May 2, 2003
175
GB
On certain appllications, the server just hangs. For example, going into Internet Explorer properties, is fine, but to actually change something in there will cause the server to hang to the point that it must be rebooted.

Another example is with NAV you can't access the histories event log, thus making it impossible to use the event viewer as it is clogged with virus warnings that we are already aware of.

Does anyone know why this happens, or how to force the application to work,
 
I would check with Symantec to make sure you have your NAV properly configured. Possible some settings may be defined and using all of your processor. When this happens verify the process that is causing this. If your server is hanging its possible your processor queue is going to a 100%. Hit the alt+ctrl+del key and check the performance and processes tabs. Start by either calling Symantec or researching their knowledgebase for any known issues that may cause slow response time.
 
I support a number of NT4.0 systems at different locations, & one of them does the same - attempt to change Internet Explorer settings (clicking the OK or Apply buttons) just hangs the explorer setup window, & often leads to explorer.exe crashing in sympathy - I don't know why this happens -- I suspect it is due to either some resource being exhausted, or some dodgy registry entries -- unfortunately I don't enough knowledge to hunt down the cause

 
There could be numerous reasons why a server hangs:

1. Any changes made to the system. Revert back whatever changes were made
2. Hardware issues such as not enough memory, faulty NIC, disk drives, Processor needs to be replaced, other hardware type issues
3. Examining what process is spiking the queue by opening up task manager
4. Run Peformance Monitor or Network Monitor and set counters for disk,memory, processor, set paging counters and other counters to narrow down
5. Network congestion. The network could be peaking. You may not have enough bandwidth at the location of the server. If you notice slowness and server utilization high make an assessment if it could be bandwidth related
6. Make sure you are at the latest Service Packs

* The above are a few suggestions I could think of and I know there could be many more. Point is you have to research and narrow down what the cause could be. The above steps could help at least narrow down. I'm guessing in this case its related to virus activity and possible virus configuration settings need to be refined via Symantec Tech Support*

Zoey
 
Thankyou Zoey, I these are nice pointers for a novice, I shall look at these. It all makes sense, though I am still not really sure what should be running at anyone time, or how much of the processor they should be taking up for a basic file server that also runs one aplication to all the clients.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top