What tool is the software vendor using for their test, and where are they testing to?
It does you no good to worry about your network if the problem is elsewhere (I had one vendor wait until after roll-out to tell a client in Amsterdam that the system wouldn't work from their office due to their latency - with the server in the US!)
Once you know what tool they're using, you can try running the same test.
The "standard" version of "PingPlotter" is free, and will give you a nice picture of the times between hops from your location to an off-site location:
http://www.pingplotter.com/download.htmlPingPlotter quickly tells me that from my office I can talk to "
www.google.com" in about 10ms, but that talking to "
www.bbc.co.uk" takes 80 - 90 ms. It also tells me which hop introduces the big delay when talking to the bbc.
If the software vendor doesn't believe the results, configure a computer with the SME server's internet settings, plug it directly in to your WAN connection, and re-run the test from there.
On my SME server:
- The first hop reported is my SME LAN IP
- I think the second hop reported is the near end of my PPP (DSL) connection, but it could be the far end.
- The third hop is definitely at my ISP
You can get the same information in a more text-y mode by running "traceroute" from the SME server itself.