Server freezes but I'm able to ping it!

Hi everyone,
This is a long time coming, but I've finally been able to see this problem through the complete cycle.
We have two servers both based on the IBM 206 server. The servers are about 9 months old and are based on the Intel motherboard and integrated LAN, sound and Intel video. They are both P4 3000 and have 1 Gig of ram made up of 512 that came with the servers and 512 matched Kingston ram to make them up to the gig. The serevr has only one HDD that is aSATA 80 Gig with 50 Gig free space.
One server is running Small Business Server 2003, and that's our domain controller, the other is running Windows standard server 2003, as our file server. I understand that both are up to date with service packs and patches.

We have about 20 users connected to the domain running a mixture of Windows 2000 and XP, our aim is to finish the roll out of XP by March.

About every 6 weeks the fileserver freezes up. Normally the file server is so frozen up that the desktop , mouse or task man wont respond. All the users in the building loose mapped drives and the file server isn't able to respond to task man. A reboot later and all is fine. The event log shows a net logon error and sometimes the Time error..... I'm guessing that these are because the server wasn't able to connect to the DC. That said the net logon error has been logged in the event log about every four hours or so.

I thought that this was a network issue so here's what I've done:

Checked the cables from the servers to the switch
Checked the network cards

Today I was able to leave the server for a while whilst just after another freeze (about one a day).Although everyone had lost the mapped drives, the fileserver was still responding to mouse keyboard, task man and I was able to browse the local HDD. I was surprised to learn that I could Ping test the file server from the DC and the results were good. I had already set up some mapped drives to the fileserver from the DC and tried to access them whilst the fileserver was in this terrible state. Yep... you guessed it they didn't respond. Nor was I able to browse the fileserver from network neighbourhood.

It was when I tried to gain access to the internet from the fileserver that I got stop errors.
The fileserver gets the internet from the Small Business Server. The Fileserver is running ISA client firewall, and this is part of the ISA 2004 installed on the Small Business Server.
Once I tried to open a web page I got the following error:
Stop Error 0x0000008E (0XC00000D8,0XF7279969,0X855CE634,0X00000000) The fileserver then completed the memory dump and booted back into Windows.

Thinking that this could be a hardware problem I placed the hard drive from the fileserver into an identical server model that we use for swap outs. the server booted up and recognised that the hardware had changed and prompted me to reregister my copy of Windows 2003 on the internet, I agreed and then faced another stop error: 0X0000008E (0XC00000D8,0XF7279969,0X8597D5BC,0X00000000)

I'm a little lost right now because this isn't such a straight forward problem.
It seems that the DC stay up but everyone looses mapped drives. I’ve run check disk and nothing seems wrong. The net logons are a pain, but I'm not so sure that that is the cause.

Is anyone able to help?
Regards
Steff
HalfhiddenAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Chris2AgeCommented:
Hi,

I had a problem like this too, 2 month ago.
Do you have an AntiVirus Software on the Clients?
Is this AntiVirus Client configured to search the mapped drives?

My File Server stopped responding to all, except ping, because all my clients was scanning the mapped drives.
So the Server had an very high disk I/O and didn't respond to anyone, except the ping command.

I turned off this function on my clients, since that the file server is running and running and running without freezing.

So check out your virus software.

Regards
Chris
cpc2004Commented:
Nt status code 0XC00000D8 means can't wait. I search google and no hit.

The crash may be caused by faulty ram or device driver error. The system event log and the minidump has the most useful diagnostic information. When Windows crashes with blue screen, it writes a system event 1001 or 1003 and a minidump to the folder \winnt\minidump. Check system event 1001 and 1003 and it has the detail of the blue screen.

Event ID: 1001
Source: Save Dump
Description:
The computer has rebooted from a bugcheck.The bugcheck was : 0xc000000a (0xe1270188, 0x00000002, 0x00000000, 0x804032100).
Microsoft Windows..... A dump was saved in: .......

Event Source: System Error
Event Category: (102)
Event ID: 1003
Description:
Error code 1000007f, parameter1 0000000d, parameter2 00000000, parameter3 00000000, parameter4 00000000

Control Panel -> Adminstrative Tools -> Event Viewer -> System -> Event 1001/1003. Copy the content and paste it back here

Zip 5 to 6 minidumps to a zip file and attach it at any webspace. I will study the dump and find out the culprit. If you can't provide the minidumps, run memtest to stress test the ram. Make sure that your windows is not infected with spyware and adware.
http://www.memtest86.com/

Get public webspace
Use a free service like rapi
HalfhiddenAuthor Commented:
Hi Chris,
Theclients are running Norton Antivirus corporate edition 7.6. I have already unticked the "scan network drives" from the clients real time scanning. I haven't excluded any extentions or drives from the "exclusions" as yet, but I give that a go.
Thanks I'll post a reply and let you know if its helped.
Regards,
Steff
Exploring ASP.NET Core: Fundamentals

Learn to build web apps and services, IoT apps, and mobile backends by covering the fundamentals of ASP.NET Core and  exploring the core foundations for app libraries.

HalfhiddenAuthor Commented:
Hi cpc2004,
Thanks for the offer. I'd be happy if you could look up these minidumps for me I'll have them zipped up and sent to you. I'll also check for spyware and addware this is a very real possibility as we have no policy in place to prevent this..... We will have a policy and network software inplcaed by the end of the morning.
Thanks for your help.
Regards,
Steff
Netman66Commented:
Is there a reason you are running the Firewall client on this server?

You should simply make it proxy client (no firewall client installed) by pointing IE to the SBS server and port 8080.  All other domain-related functions should already have pre-canned filters on the SBS box.



HalfhiddenAuthor Commented:
Hi Netman66,
Yes the reason the fileserver has firewall client for ISA 2004 running is because we have some programs that require more than the proxy server can offer. One of those programs is PCAnywere version 11. The reason why we use that was to transfer files remotely from the fileserver to remote clients..... But this hasn't yet been set up fully.
Some of the clients also need to run remote desktop in Win XP.
Regards,
Steff
Netman66Commented:
It might be PCA that is causing your problems.  Since you cannot turn off the Terminal Server Service on 2003 then there might be a conflict there.

We'll see what cpc has to say about your dumps.



cpc2004Commented:
Hi Halfhidden,

You haven't attached the minidumps at the webspace.
HalfhiddenAuthor Commented:
Sorry cpc2004,
I was notified by Microsoft to add a patch to the O/S because they informed me of compatibilities with Norton Corporate edition and 2003. However, dispite spending a long time on the phone with them and waiting for them to send the patch (not general release) it crashed the server. I wasn't able to establish trusts or shared drives, most of the time the fileserver wasn't able to communicate with the PDC dispite the fact I could ping the PDC by:
IP address
Server Name
Domain
Server name /Domain
and this resolved to the correct IP address every time.
Not a light decision, but I started to rebuild the server and have now established stability once more.
DarthModCommented:
PAQed with points refunded (500)

DarthMod
Community Support Moderator

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.