networking - prove network is truly unavailable -


I have an old school FoxPro web app that is trying to help me lame while writing the system again I am Every day, many times, I get this following error message: The specified network name is no longer available .

Is anyone suggesting how to get rid of it? Perhaps, my IT people have to prove that there really is a network problem. I have theories, but I do not know how to prove anything, it always comes back to FoxPro, writing it again is useless.

I will take any help, equipment and answer those questions which can make it clear for you.

Thank you

You may want to consider writing a short program, At the time the network resource you can just search for a file and if the network is failing and the program file can not find the email to the people in charge of the network and the people themselves, it would be a free app and best if not written in FoxPro , So that you can independently prove that this app or that No language / device that was written to it.

I have seen this when bad wires, a bad port on the switch / hub, an unsuccessful NIC in the mix, and sometimes when the network is filled with requests from workstations.

You did not even mention that this was a wireless connection, I'm not expecting, but I have failed about wireless (especially slow wireless wireless) network surcharge and slow and unreliable performance. Especially compared to the wired network.

Rick Schmumer


Comments

Popular posts from this blog

sql - dynamically varied number of conditions in the 'where' statement using LINQ -

asp.net mvc - Dynamically Generated Ajax.BeginForm -

Debug on symbian -