> > My strong supsicion is that the crashes occur following an attempted
> access
> > over the 100-Mb Ethernet network to the our central server.  Other
> machines
> > on the network seem to be able to access the server without similar
> > problems.  The machines all have 3COM 3C905B NIC's and the hub is a 3COM
> > OfficeConnect TP800.  Both my machine and the server are running Win95.
> The
> > other machines run WIn98 and WinME.
> >
> > In some cases I get an error reported by the application about 30
seconds
> > after the machine has "locked up"  - and I can then recover by allowing
> > Windows to shut down the application.  This doesn't always work however
> > since the application concerned will often then not restart at all or
will
> > crash immediately after starting.  In most cases I can recover from the
> > crash by rebooting my PC, however in some instances it has also been
> > necessary to reboot the server (most applications and most data reside
on
> > the server).  A possible explanation for the need to reboot the serever
> may
> > be that corrupt file data may be getting into the server cache.  As far
as
> I
> > know there is no way to manually flush the server cache so its difficult
> to
> > prove the theory.

I did some work for a customer once that used to have an IPX network.  I
replaced the server with a Linux box and TCP/IP naturally.  They had been
using "silver satin" for patch cords (completely illegal in terms of
networks).  This caused all sorts of peculiar behavior including 'blue
screens of death'.

Some things to try:
1) change the patch cords
2) repunch the patch panel and wall plate connections
3) make sure wiring is not running over top of a flourescent light (a bad
ballast can make allot of junk on the line)
4) switch ports on the hub with another machine
5) replace the NIC
6) don't use Win95 for a "server"
7) don't use Win95 for anything  ;-)

Windows (95, 98 or Me) cannot handle an excessive error rate when using
TCP/IP.  It will cause lock-ups and blue screens and other assorted fun.

Find someone with a $2000.00 network analyzer and have them sweep the
connection.  This will tell you allot about the connection.  A cheaper test
is to string a new cable (on the floor of course) between the pc and the
hub.  If the problem goes away, then you've figured it out.

hope this helps

michael brown

--
http://www.piclist.com hint: PICList Posts must start with ONE topic:
[PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads