Ok, some more information. I had the user send me their no-ip log and
their Zebedee log.

The no-ip log shows that their IP has only changed once since Friday,
yet they get disconnected 5-10 times per day, so it looks like my
dynamic IP changing theory wasn't correct.

Again, they say they didn't have this problem before they started
using Zebedee. My new theory is this: Firebird has some decent
retrying logic built in. Zebedee is too sensitive. It has a little
trouble with the connection, and just closes the connection entirely,
without giving Firebird the opportunity to retry. Does this sound
right? If so, I hope there's a way around it, as Zebedee has vastly
improved the speed of the app, but with the frequent disconnects,
it's just as bad as the slow speed.

Here is a snippet from their Zebedee log:

zebedee(1028/1032): accepted connection from 64.217.212.65
zebedee(1028/1032): waiting for connection on port 11965
zebedee(1028/2820): tunnel established to target 127.0.0.1, port 3050
zebedee(1028/2820): compression level 0x9, key length 256
zebedee(1028/2868): read 156896 bytes (221372 expanded) in 3693 messages
zebedee(1028/2868): wrote 1093985 bytes (11156480 expanded) in 6178 messages
zebedee(1028/2868): ERROR: failed communicating with remote client
zebedee(1028/2820): read 64957 bytes (86097 expanded) in 1594 messages
zebedee(1028/2820): wrote 417869 bytes (5112063 expanded) in 2737 messages
zebedee(1028/2820): ERROR: failed communicating with remote client
zebedee(1028/1032): accepted connection from 64.217.212.65
zebedee(1028/1032): waiting for connection on port 11965
zebedee(1028/3520): tunnel established to target 127.0.0.1, port 3050
zebedee(1028/3520): compression level 0x9, key length 256
zebedee(1028/1032): accepted connection from 64.217.212.65
zebedee(1028/1032): waiting for connection on port 11965
zebedee(1028/2016): tunnel established to target 127.0.0.1, port 3050
zebedee(1028/2016): compression level 0x9, key length 256
zebedee(1028/2016): read 57983 bytes (72984 expanded) in 1532 messages
zebedee(1028/2016): wrote 445294 bytes (4081432 expanded) in 2396 messages
zebedee(1028/2016): connection closed
zebedee(1028/3520): read 282946 bytes (373416 expanded) in 6359 messages
zebedee(1028/3520): wrote 4349114 bytes (25484832 expanded) in 12065 messages
zebedee(1028/3520): ERROR: failed communicating with remote client

Here are their Zebedee config files:

Server
=========================
verbosity 2 # Slightly more than basic messages
detached false # You will probably want this 'true' for normal
server true # Yes, it's a server!
ipmode both # Operate in mixed TCP/UDP mode
compression zlib:9 # Allow maximum zlib compression
keylength 256 # Allow keys up to 256 bits
keylifetime 36000 # Shared keys last 10 hours
maxbufsize 16383 # Allow maximum possible buffer size
keygenlevel 2 # Generate maximum strength private keys
redirect none
target localhost:3050


Client
========================
verbosity 2 # Slightly more than basic messages
detached false # You will probably want this 'true' for normal
server false # No, not a server!
ipmode both # Operate in mixed TCP/UDP mode
compression zlib:9 # Allow maximum zlib compression
keylength 256 # Allow keys up to 256 bits
keylifetime 36000 # Shared keys last 10 hours
maxbufsize 16383 # Allow maximum possible buffer size
keygenlevel 2 # Generate maximum strength private keys
redirect none
tunnel 3051:mycomputer.no-ip.info:3050

As you can see, none of Zebedee's timeout options are activated.

Any ideas?

-Joe