I'd get a network analyser and start looking at the packets to find out who is the guilty one. For example I have seen client systems choke on maximum sized packets (older Trumpet stacks with TCP MSS=1460). Depending on target or intermediate systems MTU and/or MRU negotiations this eventually lead to symptoms similar to yours. -- 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="msg09199.html">Re: (ASCEND) 50Ap27 fatal error</A></STRONG> </LI> <LI>Next by Date: <STRONG><A HREF="msg09211.html">RE: (ASCEND) SNMP usage tracking?</A></STRONG> </LI> <LI>Prev by thread: <STRONG><A HREF="msg09202.html">Re: (ASCEND) FTP problem - Please help</A></STRONG> </LI> <LI>Next by thread: <STRONG><A HREF="msg09185.html">(ASCEND) Accounting program??</A></STRONG> </LI> <LI>Index(es): <UL> <LI><A HREF="maillist.html#09198"><STRONG>Main</STRONG></A></LI> <LI><A HREF="thrd182.html#09198"><STRONG>Thread</STRONG></A></LI> </UL> </LI> </UL> <!--X-BotPNI-End--> <!--X-User-Footer--> <!--X-User-Footer-End--> </BODY> </HTML>