Quote:
Originally Posted by MxxCon
1st of all, turn off forwarded ports FTP port 21 (TCP) DNS port 53 (TCP/UDP) HTTP port 83 (UDP).
you need to do that only if YOU are running ftp server, dns server or a web server. and obviously are not.
|
already done, after some reading about FTP settings
Quote:
Originally Posted by MxxCon
while your observations are accurate, your conclusion is not correct.
sharingmatrix did not experience this problem nor did they develop any solution to that problem.
they simply have a different type of setup. where the same domain name always points to the same IP address.
|
I mean on "solution" that they have a different type of setup.
They may have other setup because they want to avoid this thing.
Sorry, English is not my language.
Quote:
Originally Posted by MxxCon
other sites you listed use load-balancing solutions where a domain name points to multiple IPs, presumably for multiple servers. i'd imagine that those multiple servers have some sort of data replication between each other to allow you to see and access your files no matter which server you connect to. what's probably happening is that you connected to another server before it had a chance to get replicated data from other servers. i'm sure if you would stop your transfer, disconnect, wait a few hours and then connect to their other servers you'd see your incomplete file.
|
I think there is no data replication between FTP servers.
After an FTP upload of a file has completed, they move the file to your account
and delete it from FTP server.
There is no point using data replication, it would take a lot of space
if every interrupted files would be transfered to their every FTP servers.
.