Kitz, Orainsear,
Thank you for those valuable tips.
Kitz, true, you'd expect the engineers would know about ADSL characteristics, but ADSL has only become available here (rural Montana) in the last 2 months, and they are self-admitted POTS experts, not TCP/IP-ATM-ADSL engineers. In their defense , they are more focused at bringing ADSL out 36kft, which involves line conditioners, load points, loop resistance, etc.; a far cry from the field of IP. I am an engineer as well, and we've all learned something. I may try the Netlimiter product for fun at a later date; what I like most about cFos, is that it is self-learning, and although it would let me tweak it's parameters as well, I just don't want to bother. Since I am getting full bandwidth up and down, my problem doesn't exist any longer.
Orainsear, my router is a Siemens Gigaset SE567; a combo modem/router/switch/AP. According to the datasheet, it has QoS functionality, but obviously ACK's aren't at the top of it's list! There are no user-settable QoS parms. I lease it and really don't want to be fiddling with the OS anyway. I do love it's WLAN AP, though. Better signal coverage than my Linksys WRT110N "Range Booster". I do have a couple of WRT54's, and I have, in the past, used the DD-WRT OS. I suppose I could eventually use the modem portion of the Gigaset (it has a configurable WAN/LAN port, and can operate in bridge mode) with another router. First, I'll have to learn how to do that! For now, I have tied up the Linksys WRT110N as an N-only AP on the Gigaset switch. Were I to use the Gigaset as a modem, then all the WLAN G-clients on it's AP would need somewhere else to go; ostensibly the WRT54G with the DD-WRT OS. Using the WRT110N in mixed mode for everybody would lose me my 270 Mbps N service. Moreover, the Gigaset radio is superior to the WRT54G. If this PC-based software solution keeps working as it has been, and if I can confirm that I am not locked out of a Remote Desktop session while doing FTP uploads, then I good to go. (Since I will be remotely operating two servers in Montana from the Dominican Republic, my biggest concern was getting locked out of my own servers if either of them were uploading.) Overall, I agree with you that managing traffic at the router level makes more sense. Even using the multi-user version of the cFos product installed on all the clients, they don't actually talk to one another, so they can't know what the others are doing. If I am remoting-in to my terminal server, while the other is uploading, I may not get the results I am looking for. That particluar test is coming soon, I can assure you!