The Cow wrote on Apr 17
th, 2012 at 12:58pm:
I suspect that adding more users simply added more routes between clients and the server. The more routers/card/wires, the more points of possible failure.
Quote:Sounds logical, However I would think other users not in Sesame but connected to other apps via the web would also have connection issues at the same time and they don't.
The only common denominator is Sesame.
Depends a lot on the programs involved. Most modern programs do not require a constant connection. Web browsers, as a typical example, will connect a disconnect frequently. This can mask connection problems, because most of the time the browser is not actually connected at all. Sesame2 requires a continuous connection.
Your business is using a bonded T1, are all of your clients on bonded T1s? Are all of the points between your clients and the server on T1s. Are all of the routers between all of your clients and your server, part of the same network? Are all of those routers operating well?
Run traceroute from the server to one of the troubled clients or vice-versa when there is a problem. See if you get consistent results over time. See if it is particular clients that disconnect frequently. If so, investigate their connection and points between their client and the server (card, cable, router, modem, trans-route routers, etc...)
Sesame3 depends a lot less on a constant connection and has reconnection capability built into it, just for remote cases like your's.