If you are an experienced ftp user then you might know what is going wrong and the way to solve it.
Case
Simple standalone in windows reads and saves small text files to a remote server using ftp.
Works on broadband, wired and wirelesly without problem for weeks.
The problem
Due to unusual circumstances I have had to work wirelessly now with a o2 usb stick and GPRS. As expected, the transmission delay has risen from 1 second to about 5 or 6 seconds and often the new file is created or existing one written to with zero contents when always content was sent. Reading a file with content also is very unreliable.
How can a previously working system fail to send content just because of the GPRS method of tranmission?
Is there a solution if it is a delay problem? (i am aware of the 15 second open port time, but the time is no where near that)
My ftp nightmare
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, robinmiller
[quote="Klaus"]Hi user#606
just guessing:
Maybe you could raise "the sockettimeoutintervall" to say 10 secs?
...
set the sockettimeoutintervall to 10000
## do your ftp stuff...
...
At least worth a try :-)
Best
I have extended it to 30 seconds, but no improvement.
Until I get back to civilisation in 9 days time, I cannot try normal broadband again. I cannot believe this is happening or figure out why. The embarrasing thing is, clients are wanting to start using the software.
just guessing:
Maybe you could raise "the sockettimeoutintervall" to say 10 secs?
...
set the sockettimeoutintervall to 10000
## do your ftp stuff...
...
At least worth a try :-)
Best
I have extended it to 30 seconds, but no improvement.
Until I get back to civilisation in 9 days time, I cannot try normal broadband again. I cannot believe this is happening or figure out why. The embarrasing thing is, clients are wanting to start using the software.