Some Win XP clients very slow opening files from SBS2003. Other PCs all fine.

I have a client with an SBS2003 server that crashed over the weekend. Power Outage I think.

Its a small network, only 5 PCs (4 x XP and 1 x Windows 7), all connected to the domain.  1 of the Win XP machines and the Windows 7 PC are fine, but on the other 3 Win XP machines it is now very (very) slow to open any documents.

I have been able to connect 2 laptops to the network, although not to the domain, and they both open and access files fine.  I've checked network settings, DNS, DHCP etc., I'm even using a different Network Adapter in the server in case it was a faulty card.

I've downloaded latest updates on both the XP client PCs and the Server but still nothing.  The XP machines connect to the server for DHCP OK and work fine with Outlook and the business system they use connects to the server via SQL OK.  

The PCs can also open the file shares and browse the contents pretty quickly, but as soon as I try to open any file (Word, PDF, JPG - doesn't matter), the local PC hangs and it takes minutes to work.  Sometimes the file then opens, often I get a timeout / failure to connect error.

Everything was fine on Friday, with all PCs.  Something over the weekend, maybe the crash, maybe an update, has caused an issue with 3 PCs.  I've tried all I can think of.  Help would be very welcome.
Who is Participating?
WestcountryBusinessAuthor Commented:
Problem solved - it seemed to be a combination of problems caused by the power outage.

The following day, there was no network access.  This wasn't resolved until the NIC card was physically removed, despite it being disabled and not in use!

I finally pinpointed the problem to be with all PC, but only when saving a document for the first time in Word.  Saving back to an existing doc was fine, saving in all other apps, including Excel was fine.  I eventually resolved this by uninstalling the anti-virus (CA eTrust) on the server. It had been disabled and I'd manually disabled the services too, just to be safe.  However completely uninstalling it seems to solve this issue.
Darius GhassemCommented:
Do you have antivirus software running on the PCs?

Read this as well:
What Anti-virus software is on the workstations?  Could be a corrupted update.  Try disabling the AV software on the workstation and opening the  document?

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Change the original NIC back. Changing NIC's on an SBS 2003 server will cause the bindings to get incorrect, and that will cause issues (unless you use the server's wizards to reflect the changes).

Also, if there was a power outage, it'll be likely the RAID array got corrupted (particularly if a cheap controller without battery backup is used), and so it is possible that the arrays are rebuilding, which will always cause speed issues until the rebuild has finished. So it could just be a case of having to wait until things normalize again. But check the state of the arrays.
WestcountryBusinessAuthor Commented:
Thanks for the replies:

darius -  thanks for the link.  I had found that this morning when googling for solutions & it's not applicable in this case.

Leslie - yep, tried disabling the AV but no luck.

Rindi - That's what I thought it was, but checked the RAID and all OK.  Local disk error check OK too.  Also the server is fine accessed locally and from the three working PCs.

I also had the issue you described changing NICS. Originally no access at all, but ran the internet connection wizard again & sorted this.  Again, as its working from 3 PCs, it would appear not the be a server issue, more a compatibility issue / conflict.

Any further ideas?
I've requested that this question be deleted for the following reason:

The question has either no comments or not enough useful information to be called an "answer".
WestcountryBusinessAuthor Commented:
I've completed a solution to this question myself. Not sure whether it will be helpful to anyone else. Please review before deleting just in case you feel it's worth keeping on file.
It could be helpful. I suggest you accept your own solution as the answer.
WestcountryBusinessAuthor Commented:
I've requested that this question be closed as follows:

Accepted answer: 0 points for WestcountryBusiness's comment #a38375377

for the following reason:

Own solution accepted as answer
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.