> Type something on the client: you should see the letters on the other
> side.  Wait some time, and type something on the other program, and
> see if the letters appear on the opposite program again.
> Some experiment with how long to wait before answering should give
> you an idea if it is a timing issue with udp or not.

I also started to get wierd etimeout errors on random hosts for no good
reason - However we had changed switch configuration, tagged VLANS, and
also firewall version, FW-1 running on Linux to FW-1 running on SPLAT

Turns out that in FW-1 the default UDP timeout is 40 seconds and
increasing that to something higher has solved the issue for us. The error
we were seeing in the debug was the same as yours.

thanks