The real problem is that Mirocsoft is only capable of writing single theaded operating sytems. A ConfReq-TermAck sequence is nothing that should time out but is intended to go on forever. As such, it should not delay the normal progress of the connection but run in parallel. Certainly it is unreasonable by Ascend to enforce this on dialup lines for quake-players. On mission-critical leased lines however, enabling/disabling protocols and changing operating parameters temporarily without having to tear down the connection has its virtue. Worst of all, Ascend is permanently changing its negotiation strategies without documenting them or make them user-configurable. -- Manfred Kwiatkowski, ZRZ (Zentraleinrichtung Rechenzentrum), Sekr.: EN 50, Technische Universitaet Berlin, Einsteinufer 17, D-10587 Berlin, GERMANY. INTERNET: kwiatkowski@zrz.TU-Berlin.DE phone: +49 30 314 24355 X.400: s=kwiatkowski ou=zrz p=tu-berlin a=d400 c=de fax: +49 30 314 21060 ++ Ascend Users Mailing List ++ To unsubscribe: send unsubscribe to ascend-users-request@bungi.com To get FAQ'd: <<A HREF="http://www.nealis.net/ascend/faq">http://www.nealis.net/ascend/faq</A>> </PRE> <!--X-MsgBody-End--> <!--X-Follow-Ups--> <!--X-Follow-Ups-End--> <!--X-References--> <!--X-References-End--> <!--X-BotPNI--> <HR> <UL> <LI>Prev by Date: <STRONG><A HREF="msg08277.html">Re: (ASCEND) Disconnects and Cause 47</A></STRONG> </LI> <LI>Next by Date: <STRONG><A HREF="msg08268.html">(ASCEND) connection dies with MAX4060...</A></STRONG> </LI> <LI>Prev by thread: <STRONG><A HREF="msg08283.html">Re: (ASCEND) Authentication times</A></STRONG> </LI> <LI>Next by thread: <STRONG><A HREF="msg08298.html">RE: (ASCEND) Authentication times</A></STRONG> </LI> <LI>Index(es): <UL> <LI><A HREF="mail25.html#08279"><STRONG>Main</STRONG></A></LI> <LI><A HREF="thrd147.html#08279"><STRONG>Thread</STRONG></A></LI> </UL> </LI> </UL> <!--X-BotPNI-End--> <!--X-User-Footer--> <!--X-User-Footer-End--> </BODY> </HTML>