[AccessD] Troubleshooting network issues

Just an idea, did'nt read all mails..

Did you checked the system log on the server or pc where the database is
located if you have any disk errors?
A faulty file table or surface errors could cause this to.

I would cerntanly start dooing a checkdisk, surface included (can take
very long).

Erwin

 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of MartyConnelly
Sent: Wednesday, March 21, 2007 1:42 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Troubleshooting network issues

This method will identify the possible machines that might have a bad
NIC.

Then a quick and dirty test to identify a bad NIC is to download a large
text file to the machine say 50 - 100 MB from a server and use a
stopwatch. A faulty NIC will have a large number of retransmission
errors so will be say 50% slower.
Some newer NIC's store the number of these type of errors in a onboard
cache that is readable externally

You might try one of the utilities from
http://www.sysinternals.com
or wherever MS has put them now.

William Hindman wrote:

>http://support.microsoft.com/kb/283849
>
>William Hindman
>
>----- Original Message -----
>From: "JWColby" <jwcolby at colbyconsulting.com>
>To: "'Access Developers discussion and problem solving'" 
><accessd at databaseadvisors.com>
>Sent: Tuesday, March 20, 2007 4:35 PM
>Subject: Re: [AccessD] Troubleshooting network issues
>
>
>  
>
>>I thought that functionality wasn't valid anymore.
>>
>>
>>John W. Colby
>>Colby Consulting
>>www.ColbyConsulting.com
>>
>>-----Original Message-----
>>From: accessd-bounces at databaseadvisors.com
>>[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of William 
>>Hindman
>>Sent: Tuesday, March 20, 2007 4:30 PM
>>To: Access Developers discussion and problem solving
>>Subject: Re: [AccessD] Troubleshooting network issues
>>
>>JC
>>
>>...can you monitor the ldb to see who is having the disconnect
problems?
>>
>>William Hindman
>>
>>----- Original Message -----
>>From: "JWColby" <jwcolby at colbyconsulting.com>
>>To: "'Access Developers discussion and problem solving'"
>><accessd at databaseadvisors.com>; "'Discussion of Hardware and Software 
>>issues'" <dba-tech at databaseadvisors.com>
>>Sent: Tuesday, March 20, 2007 3:12 PM
>>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
>>>      
>>>

--
Marty Connelly
Victoria, B.C.
Canada

--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com