Quote:
Originally Posted by bigstar
The only time I've seen this type of behavior occur is when you actually unplug the network cable from the computer running FlashFXP.
Although there maybe other ways there is no way to predict it.
|
right,i can confirm this to. I can even confirm that this will 'sometimes' happand when you plug in a socks between two remote sites. When this socks goes offline for a reason or another? you get same results as jcony or "unplug network cable". ffxp will end up fxping for ouers, sometimes over 2-9 houers with same file. Thing is, even If this socks go online again,after a minute or two? ffxp will "sometimes" Not recognize this and keep hanging there till we do a manual abort, reconnect...
With 'some' other socks there are Much less problem. If proxy goes down, then ffxp also disconnects immediately and keep trying reconnect till socks are online again. In another config If 'one' remote site are hooked up through a socks, and the other site are not. If the socks goes down, ffxp keeps hanging there for several minutes up to several ouers, real annoying behavior. Manual abort, reconnect will do the trick (if Not proxy are offline for the moment) But, sometimes it will work like a charm, everytime when it goes down, ffxp disconnects immediately. this is Not speed related, same issue with gigabit pipeline as for 10mbit line. "send noops during transfer" does not help in this Case!! (just to let u know
i have seen this behavior with https proxy to... same issues... same timecycle
agree with DayCuts, it should definitly be site specific and even an "Must Have" options within "ProxyTab" for those who use such configuration?
The proxy Tab should include two: 'Global'(for all proxy in list) and 'socks/proxy specific'
keep up the good work!