>>>>HI
>>>>
>>>>I'm having a problem with an FTP step in a package.
>>>>
>>>>This was working ok till Wednesday when the FTP changed IP address. I don't know what other changes they may have made.
>>>>
>>>>Now the FTP fails with
>>>>
>>>>An error occurred in the requested FTP operation. Detailed error description: 200 Type set to A
>>>>227 Entering Passive Mode (192,168,0,2,199,182)
>>>>
>>>>Entering the same connection details in Filezilla works with no problem.
>>>>
>>>>Anyone got any ideas on how I can solve this problem.
>>>>
>>>>Thanks
>>>>
>>>>Nick
>>>
>>>Try to turn off FTP Passive Mode in IE options.
>>
>>Thanks Boris.
>>
>>Tried that but it made no difference.
>>
>>Any ideas on where I should investigate . Logs etc.
>
>Have no idea.
>I just googled your error and read the results.

Hi Boris

thought I'd let you know what seems to have happened is that they've put their FTP server behind a NAT device. The clue is the 192,168,0,2 IP address instead of a public facing IP address.

From an article

The FTP server returns to the client an IP address and port that the client should use for further communications. The problem is, that when connected behind a NAT devices, the FTP server only knows about it’s local RFC1918 IP address (10.X.X.X, 192.168.X.X 172.16.X.X etc) and not it’s public internet IP address – therefore the server responds with the only IP address that it knows about, the RFC1918 IP address. This is problematic because RFC1918 IP addresses are not routable over the internet so any FTP client using the unroutable IP address returned by the FTP server will be unable to send further data packets to the server.

Annoyingly things like Filezilla deal with this by using the server address instead (see below)

Response: 227 Entering Passive Mode (192,168,0,2,200,178)
Status: Server sent passive reply with unroutable address. Using server address instead.

But the FTP task in SSIS doesn't manage this and so hangs up.

I'll have to work out a way round that.
Still worth knowing about.