Small company logo:
Advertising banner:

About TCP/IP
TCP/IP is a "guaranteed-delivery" protocol that maintains and manages its own connections.
TCP/IP is best for connections that are relatively error free, and where there is high throughput on the connections (so that the TCP/IP buffer is flushed quickly).

About UDP/IP
We use the FCP delivery protocol to deliver reliable connections over UDP/IP. This lets FCP control when to disconnect in the event of an error.
FCP can deal better with errors that would cause TCP/IP to immediately disconnect you, because it has been adjusted to better cope with an unreliable environment. These adjustments involve such things as timeouts waiting for packets before attempting retries, and packet and sliding window sizes.
UDP/IP is best for error-prone or slower connections (where it may take some time to flush the large buffers that are often found in TCP/IP connections). It is optimized to provide faster interactive response to your requests in this environment.
Because the total data size is less than the TCP/IP buffers, you should notice quicker response times for an activity such as opening the first item in a filling container (over a fast, reliable connection, TCP/IP still outperforms UDP/IP in this regard).
UDP/IP connections and firewalls
If you can't connect using UDP/IP, it may be because the client is behind a firewall that doesn't support remembering UDP/IP connections. In this case, try TCP/IP.
If you can't connect, and it's not because of the situation described above, try opening port 810 on your firewall.