RE: CU-SeeMe connect requests overloaded the network
Fri, 6 Jan 1995 14:32:47 -0500

>Has anyone seen this happen before? It seems to me that CU-SeeMe should
>have a timeout value to stop sending requests after 1-2 minutes of
>Thanks in advance.
>Steven K. Womble
Hi Steve,

RE: Above

I have been running CU in rec. mode only on WFW with Chameleon. I have
noticed what seems to be a persisting UDP connection at the given port 7xxx
even when a disconnect has been issued. The effect is CU seems to be
disconnecting, announces that it has, (meanwhile - the UDP stat box shows
continued packets incoming and the port is still open) a few seconds go by -
and if CU has not been exited completely, any 'v' or 'c' sessions active
suddenly re-appear - generally all as 'v' sessions.

The fail safe I found is to EXIT the app. The port closes. Disconnect does not
seem to close the port connection, even when it HAS been succesful in saying
"stop sending UDP packets".

You might confirm these findings with Chameleon Newt utilities (or similar), if
you have it at your site.