How to find where a connection is failing
I have a website that is running a basic ASP.NET application that is mostly used from one location, which is my office for clients. The server is located in a high performance data center.
Whenever I have tested or used my app from outside my office, I have consistently good connections, but from their office, the connection seems inconsistent. Sometimes the requests just don't show up on the server from the browser. I'm not familiar with office networking equipment, but they have a T1 connection that should always be on.
I've tried pinging and tracing and everything looks fine. When running Firebug during a failed request, the request appears in the log and then just sits there without showing that it is sending any data, eventually time out.
My question is, what tools can I use to diagnose this connection problem and start narrowing it down to a specific cause so that I can fix it? Its an intermittent problem, so a durable tool will probably make more sense if you have one.
Thanks for any help.
source to share
All your standard ping and traceroute tools are probably the best. I don't understand where is the site?
If you open a command prompt, run ping -t aspwebsiteurl.domain <- will show if there is any packet loss. From the command line again tracert aspwebsiteurl.domain <- will show you which route the packet is taking to get the site. Can also show you if there is a particular jump that hickup gives you.
source to share
Speed Test - Internet connection speed can help in some links to test the connection at the client's office to see how well it works.
Another question: how far is the client and data center? If someone is in New York and the other is in Los Angeles, then the distance between them may be a factor. Also, have you considered any possible DNS issues?
source to share