Post a reply

Before posting, please read how to report bug or request support effectively.

Bug reports without an attached log file are usually useless.

Options
Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

Options

Topic review

Guest

martin wrote:

Either you have them configured differently

they are using the same .ini config file

martin wrote:

or the portable copy is blocked by Windows firewall or similar.

Can you attach log files from both?[/quote]
both the .exe file and .com are added to the to firewall exception for public and private networks. other than that I am at a loss

martin wrote:

Can you attach log files from both?

logs attached
martin

The portable and installed versions are identical. Either you have them configured differently or the portable copy is blocked by Windows firewall or similar.
Can you attach log files from both?
PeteGB

I have only run the full version on the April 2018 Windows 10 machine,but it was successful
martin

Re: gethostbyname: unknown error April 2018 WIndows 10 update WinSCP portable

Where do you run the "full version of WinSCP"? On the April 2018 Windows 10 machine or on the other one?
PeteGB

gethostbyname: unknown error April 2018 WIndows 10 update WinSCP portable

Since running the April 2018 Windows 10 update WinSCP portable no longer connect to my FTP server.

It throws an error saying "gethostbyname: unknown error".

Running the same portable file from a PC that has not been updated works fine, as does running a full version of WinSCP using the same config file.