Upping the timeouts on the protocols WILL NOT fix the problem. It just makes the app seem more sluggish because it will not timeout as fast. I have been through this with many customers. Also, how long should you make your timeout? As long as the link stays maxed? How long is that? Again, your customer needs to tune their link. The may have the same issue with another app running it the same way. Anything to minimize traffic. Also recommend they get the link checked with an analyzer and/or by their supplier. I had the same issue with a company running my SW & custom apps slow over a T1. I put an analyzer on, and they had a lot of errors. They replaced a CSU/DSU, now everything is great.

>Thanks for the reply. I suspected it was most likely on the network side, but wanted to verify it. I have no control over the application since it is a commercial accounting system. I'm leaning toward a Thin Client solution to alleviate this, but their IS person (also heading up the project) wants "proof" that the application won't work over the T1. He also felt that it was a network timeout issue and that he should be able to increase the timeout and it would correct the problem. They don't have any problems with other applications (all client server based). I tried to tell him that he wasn't comparing apples for apples, but I don't think he gets it.
>
>Again, I appreciate all of the replies. I will attempt to go back to him with some of this information so we can keep moving forward.