Core FTP

It's Core FTP LE v1.3c, build 1446. If the problem arises, it stays through the entire range until all retries are exhausted and the session self-terminates. Perhaps I should also mention that both client machines (home and server's network) are running Win98SE, server is on Win 2000 Pro. If it happ...

I was finally able to download files at home, through two NAT routers with an encrypted control channel with the same port range as I used on the server's network. I only had to forward one port on the server's router, and since I have an adaptive software firewall at home, I can turn it up full to ...

Did find out that Core FTP seems to be a little picky about that port range. I got a LIST through at home, but all my tranfers failed with a 499 error connecting to the client. So at the server, I tried another computer on the network without a port range, and it worked fine. Then I specified the po...

Finally. That did it. Whew! This has been quite an education in the inner workings of FTP!

Well, still not working! I have no idea what port the server will choose for data during a passive connection (evidently it's only 989 for an active connection), so I have no way to forward the connection to it through the router. I'm going to try active mode since though it says it's not supported,...

Okay, I've found that I have to update the server software to a version that supports the FTP PASV IP parameter when behind a NAT router so that the WAN IP is encrypted. Data channel IS port 989, so I'll forward it. When that's all done - this should work. Sorry to use up the space here for nothing....

Umm... Just found out the Sambar Server only supports passive FTP. I'll need to forward the data channel port to the server. Is that always 989 when the control is 990?

Just saw the "first use hangs" thread. I haven't tried a refresh, maybe that would work. BTW, the server is set for the first SSL option mentioned in the documentation snippet.

I administrate a server running Sambar with a self-generated temporary cert. HTTPS works fine as does regular FTP. The server is behind a LinkSys NAT router. I have port 990 forwarded to the server. I also have a client machine at home that is behind a LinkSys NAT router. My home configuration is: P...

Two NAT routers. Would it be possible to include an option whereby a router's WAN address could be stored as a setting so it could be encrypted and sent to the FTP/SSL server instead of the machine's LAN address? I have been able to connect to the server with all the clients I've tried that support ...