FTP Using TC x64 8.0B6

[CHamlin]

If I go back to an older TC...no problem...but with 8.0B6 it connects to my FTP but I can't do anything with it. It will not list files/folders. Disconnect takes forever...etc. It just does not work at all for me.

[karlchen]

Hello, CHamlin.

It would be helpful if you could provide details on what is going on, e.g. you might post a T.C. ftp logfile which illustrates what's happening during the FTP session.
In case you post such a logfile, please, make sure to camouflage any piece of confidential information like real account names or passwords.
In order to make T.C. log ftp sessions to a file, go to Configuration => Options => FTP and tick the option [x] Create a logfile.

Kind regards,
Karl

[ghisler(Author)]

Yes, please post a log file. My guess is that some kind of personal firewall or internet "security" suite is blocking Total Commander.

[CHamlin]

The log did not have much:

Get directory
PASV
OFFLINE7, error=10050

I checked the firewall (Windows Firewall) and Total Commander is an exception so it should be letting it through.

[ghisler(Author)]

I think that my guess with a firewall is right, just google for:
error 10050

The error means "A socket operation encountered a dead network. Check your Winsock, protocol stack, network driver, and network interface card configuration. Note that this error occurs rarely, because a Winsock implementation cannot reliably detect hardware problems.".

Apparently it's not a hardware problem, but a block.

[CHamlin]

I have made sure that there is an entry in Windows Firewall to allow it. The 32-bit version works without any problems at all...it is the 64-bit version which is giving me the hassle...but it is setup the same way. Are you doing things any differently?

[Flint]

CHamlin
Could you please just try to turn Windows Firewall off temporarily and check whether the problem persists or not?

[CHamlin]

It does work if I turn off my firewall...but that is confusing since there is an exception put into the firewall for your software. It is a duplicate of the 32-bit one for the 64-. 32- works but 64- does not...which is why I was asking if you are doing things differently with the 64- that I need to exclude something else as well.

[karlchen]

Hello, CHamlin.

32-bit Totalcmd.exe and 64-bit Totalcmd64.exe are two totally different and unrelated programmes from the perspective of your personal software firewall.
Therefore, your statement

It is a duplicate of the 32-bit one for the 64-.

might suggest that this is the source of the problem. The two rules cannot be identical, because one is about Totalcmd.exe and one should be about TotalCmd64.exe.

Kind regards,
Karl

[CHamlin]

I know they are different executables. I meant that they are setup exactly the same in the firewall as far as protection, what is allowed/disallowed, etc...the paths and executable names are indeed unique. That is not the problem, so I am wondering what else I can look at.

[ghisler(Author)]

So you really have different entries in the firewall for totalcmd.exe and totalcmd64.exe?

[CHamlin]

Absolutely.

[ghisler(Author)]

Try to delete the 64-bit entry. Windows should ask you to allow TC x64 the next time you try to connect.

[CHamlin]

I removed it...and I get the same reaction. It does the actual connect/login into the FTP site...but then cannot do anything. The firewall never prompted me for anything. It still works fine for the 32-bit program...I just cannot get the 64-bit to work.

[CHamlin]

I finally got it to ask...I informed it to allow...and it still does not work. It can connect...but cannot list/etc.