|
Your suggestions and my investigations on this end have revealed a number of things that I need to look into, but didn't yield much I could use. The problems are configurations on my end, so there's some more work for me. Last night, our network guru was impacted enough by the issue that he dug deeper on his end and discovered errors on the network switch that no one else had noticed yet. The cause ended up being a bad network cable. Swapping out the netowrk cable appears to have resolved the issue. Thanks to everyone for your suggestions, they are all much appreciated. Hopefully, I will be able to make use of some of the tools and suggestions provided next time something happens. Thanks again, Patrick
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.