[AccessD] Troubleshooting network issues

Hi John:

I have run into many similar issues in the past. In my case the problems
were around flaky NIC cards and in one case it was an IT guy, in the
evenings whom would keep rebooting the server to test some backup scripts.
Naturally not everyone had logged out of the Access application at the end
of the day.

We used a packet-analyzer to spot the problem... not necessarily what the
product is designed for but its ability to keep an ongoing transaction file
of network traffic proved invaluable. There are some similar open-source
products out there that will do the same thing.

HTH
Jim   

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of JWColby
Sent: Tuesday, March 20, 2007 12:12 PM
To: 'Access Developers discussion and problem solving'; 'Discussion of
Hardware and Software issues'
Subject: [AccessD] Troubleshooting network issues

One of my clients is apparently having network issues, i.e. starting just
this morning, suddenly the main database be is getting corrupted, as in more
than a dozen times today.  The common wisdom is that corrupted BEs is a
network issue - NICS, cables, switches, routers etc.  Does anyone have any
experience tracking down such a problem, any recommendations for tools that
would watch for intermittent network connections, troubleshooting
suggestions for trying to isolate the offending piece of the puzzle?
 
John W. Colby
Colby Consulting
www.ColbyConsulting.com
 
-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com