SmartFTP unable (unwilling?) to reonnect.

Happens literally every time I use the software app.  If I leave it sitting open, connected to the server for longer than "X" minutes, the app wont reconnect.
Reproduce:
 
1)  Load up any FTP location
2)  Let it sit for a couple hours
3)  Click on a subdirectory displayed on the server side of the screen to tell SmartFTP to open up that directory.
4)  SmartFTP attempts to connect to the server, then fails.
 
I always have to close SmartFTP completely and reopen it and reconnect to the site.  Its getting frustrating.
 
Here is what I see when this happens:
 
[23:15:09] The operation has been added to the Transfer Queue. Check the Transfer Queue for the status.
[23:18:18] The operation has been added to the Transfer Queue. Check the Transfer Queue for the status.
[13:59:04] 3>Resolving path "/var/www/shop/app/".
[13:59:23] 3>An established connection was aborted by the software in your host machine.
[13:59:23] 3>Server closed connection
[13:59:23] 4>Resolving path "/var/www/shop/app/".
[13:59:42] 4>An established connection was aborted by the software in your host machine.
[13:59:42] 4>Server closed connection
[13:59:42] 5>Resolving host name "162.242.238.219"
[13:59:42] 5>Connecting to 162.242.238.219 Port: 22
 
Before you say this isn't a bug - yes it is.  Even if the server times out, or my machine times out, or your software times out, I should be able to click on a remote directory and your software should re-initiate the connection to that path.  Very simple.  I shouldn't have to close the application manually and reopen it and connect.  You can program that function in.
 
Thanks.

The reason you are seeing this behavior is because the server does not send a disconnect message or it never arrives in SmartFTP. For example if the disconnect message is blocked by a software firewall or a network device. The solution is to fix the network setup so that this message does not get lost.

So your software needs to see a disconnect message in order to initate a full reconnect, otherwise I have to repeatedly close your entire program, reopen it, and manually reconnect?

To be completely honest - your solution seems to be a lazy one. 
 
Why can't your software simply see the problem and initiate a full reconnect on its own?   It can.  
 
My server is set up correctly and doing what its supposed to do.  There is nothing blocking its communication with your software.  
 
 
Your application does this with every server I connect to. 
 
You very easily could write a function into it that recognizes it when it happens and re-initiates a full connect to the server. 
 
It just happened again:
 
[11:35:34] 1>935 bytes transferred. (14.7 KB/s) (62 ms)
[11:35:34] 1>Closing file handle.
[11:35:34] 1>Directory listing complete.
[12:11:09] 1>Resolving path "/var/www/shop/skin/".
[12:11:28] 1>An established connection was aborted by the software in your host machine.
[12:11:28] 1>Server closed connection
 

Best answer? 
 
You voted your own answer the best answer, and you haven't helped me solve the problem.
 
Outstanding.
 
Your response doesn't even make sense.
 
Your software is failing to receive a "Disconnect" message from the server > Therefore your software is disconnecting?

Could you please explain how that makes any sense?
 
"The reason you are seeing this behavior is because the server does not send a disconnect message"
 
So if the server sent a disconnect message, your software WOULDNT disconnect?

That doesnt make any sense.