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?