![]() |
|
|
|
|
|||||||
| Forums | Portal | Register | Forum Rules | FAQ | Contribute | Members List | Arcade | Search | Today's Posts | Mark Forums Read |
| IP Networking Questions involving TCP/IP, Routers, Hubs, Network protocols, etc go here. |
|
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Sed utility | Padmav | Shell Programming and Scripting | 1 | 05-09-2007 11:36 PM |
| RedHat diagnostic commands | soliberus | Linux | 1 | 09-05-2006 09:36 AM |
| Diagnostic Software | camerja1 | UNIX for Dummies Questions & Answers | 2 | 07-29-2003 11:25 PM |
| Unix Equivalent of Windows NT Diagnostic (Winmsd) report | neer | UNIX for Dummies Questions & Answers | 2 | 09-13-2001 01:40 AM |
| What utility do I use for this? | James | UNIX for Dummies Questions & Answers | 8 | 07-11-2001 01:42 PM |
|
|
Submit Tools | LinkBack | Thread Tools | Display Modes |
|
|||
|
Looking for an end-to-end network diagnostic utility...
I am looking for a utility (Windows/Linux/Mac) that will allow me to run some test packets across a customer's network (between their client & my server) to identify a list of (or at least a guess of) all protocols and significant network settings that could adversely effect my systems performance in their eyes...
Description of the Scenario - Problem: A client machine gets poor performance when accessing data from a server. Response: Must be something wrong with the server. Actual Cause: Network overhead because of the core router imposing some rule to my traffic that I was unprepared for. Fix: Check for all imposed rules between end nodes & compare to list of known trouble-causers, alerting customer of incompatibility Any ideas? |
| Forum Sponsor | ||
|
|