Transfer channel can't be opened. Reason: The requested address is not valid in its context

Hello,

Since 3-4 days, I'm not able to connect to an FTP-server anymore. The weird thing is, I can still connect from my local machine, but I can not from my VM (Windows Server 2012 R2). I'm using the same version on both machines which is the newest so far: 5.9.4 (build 7333). Other clients can still connect succesfully, as well locally as on my VM. Some extra details:
I'm using GUI, commander style interface and all default configuration are on since I've reinstalled the newest version of WinSCP once over again. Port 21 for WinSCP is added to the windows firewall like it should. But even after shutting down the firewall, the same error applies.

"Transfer channel can't be opened.
Reason: The requested address is not valid in its context.
Could not retrieve directory listing"

In attachment, I've added the full log file of the VM.

Thank you in advance for your time and effort :)

Additional info: Succesful log WinSCP on local machine

lousegers1 wrote:

Other clients can still connect succesfully, as well locally as on my VM.

Show us their log file for comparison.

Here is the VM's successfull log.

martin wrote:

lousegers1 wrote:

Other clients can still connect succesfully, as well locally as on my VM.

Show us their log file for comparison.

Here it is :)

Is the address in the 227 response to the PASV command really 0,0,0,0 or did you mask it out?

If it is really 0,0,0,0, the problem is misconfigured FTP server.

Set the Force IP address for passive mode connections to On.
https://winscp.net/eng/docs/ui_login_ftp

But please answer my first question in any case.

martin wrote:

Is the address in the 227 response to the PASV command really 0,0,0,0 or did you mask it out?

If it is really 0,0,0,0, the problem is misconfigured FTP server.

Set the Force IP address for passive mode connections to On.
https://winscp.net/eng/docs/ui_login_ftp

But please answer my first question in any case.

Forcing the IP address for passive mode connections works like a charm.
FYI: I did not mask it out :)

Thanks for your time and effort, it's well-appreaciated !

lousegers1 wrote:

FYI: I did not mask it out :)

So then you should get the server fixed, instead of working it around on client side.