"Error retrieving server address" message after 4.3.8->4.4.0

Hi after upgrading a test server from WinSCP 4.3.8 to 4.4.0 some scripted transfers exhibit strange errors in the logfiles:

Snippet from before:

. 2013-06-03 08:30:19.734 Changing directory to "XX".
> 2013-06-03 08:30:19.734 CWD XX
< 2013-06-03 08:30:20.140 250 CWD command successful.
. 2013-06-03 08:30:20.140 Getting current directory name.
> 2013-06-03 08:30:20.140 PWD
< 2013-06-03 08:30:20.546 257 "XX" is current directory.
< 2013-06-03 08:30:20.546 Script: XX
> 2013-06-03 08:30:20.546 Script: synchronize local -delete
< 2013-06-03 08:30:20.546 Script: Comparing...
. 2013-06-03 08:30:20.546 Collecting synchronization list for local directory 'XX' and remote directory 'XX', mode = 1, params = 3
. 2013-06-03 08:30:20.562 Retrieving directory listing...
> 2013-06-03 08:30:20.562 TYPE A
< 2013-06-03 08:30:20.953 200 Type set to "A".
> 2013-06-03 08:30:20.953 PASV
< 2013-06-03 08:30:21.359 227 Entering Passive Mode (153,46,254,66,206,122)
> 2013-06-03 08:30:21.359 LIST -a
< 2013-06-03 08:30:21.781 125 ASCII data connection for -a
< 2013-06-03 08:30:21.859 226 Transfer complete.
. 2013-06-03 08:30:21.859 Directory listing successful
< 2013-06-03 08:30:21.890 Script: Nothing to synchronize.


After:
Same thing but:
. 2013-06-04 06:03:16.689 Getting current directory name.
> 2013-06-04 06:03:16.689 PWD
. 2013-06-04 06:03:17.095 Retrieving directory listing...
> 2013-06-04 06:03:17.095 TYPE A
< 2013-06-04 06:03:17.486 200 Type set to "A".
> 2013-06-04 06:03:17.486 PASV
< 2013-06-04 06:03:17.892 227 Entering Passive Mode (153,46,254,66,53,96)
. 2013-06-04 06:03:17.892 Error retrieving server address
> 2013-06-04 06:03:17.892 LIST -a
< 2013-06-04 06:03:18.376 125 ASCII data connection for -a

But everything seems to work normally. What dows this error imply?


regards,
Jesper

When using passive mode WinSCP optionally tries to detect, if the IP address, the server has provided, is correct one or not. And fix it, if it is wrong. In your setup, WinSCP was not able to detect the correct IP address (it's common e.g. if you are behind a proxy). This feature was off by default in 4.3.8 and is on in 4.4. As it does not work for you anyway, there's no change for you, except for the error record in the log.