How best to find faulty NIC/cable/port

[Joe Webster]

First of all, sorry for the cross-post -- but I'm ready to burn it all down!
;)

The basic problem: We use a crappy software application written in VB using
VBA/Access with a Access DB. I assume that DAO/Jet is used to make the
connections to the DB. The MDB file itself is stored on a server (Windows NT
4.0) and shared over a all 100bt network. We are having problems with the
database becoming corrupt every few days.

I want to rule out hardware problems, and want to find a way to test each
computer. First thing that comes to mind is to make a hefty file, put it on
the server, copy it to the client and back to the server under a different
name. Then I can see if the file is the same. If it's different, then I'll
know it's that client -- or that client's route to the server -- that needs
to be looked at.

What comes to mind right now -- make a nice big file... 100mb or so... copy
it back and forth. Then later I'll run a MD5 on each file and see if they
match up?

How does that sound as a crude test?

Other suggestions?

Thanks,
Joe Webster

[Maxor]

Hi,

first of all you say that your database becomes corrupted every few days,
what happens with it in the meantime? Does it work as it should without
corruption?
If thats the case it probably isn't a hardware problem but probably a
scheduled job that somehow accesses the database and corrupts it.

The test you mentioned is pretty straightforward and should work fine.

Maxor salutes you!

"Joe Webster" <j...@cawfeemilk.com> wrote in message
news:_SiQ9.100498$pe.37...@news2.east.cox.net...