Hi,

FWIW the problem ended up being two things.

1. The Primary cause, we were using PORT instead of PASSIVE for the FTP Connection, it had been working for about 3 weeks until last Friday when the server picked a high port that was blocked in our Firewall.

Why did PASSIVE work, because in PASSIVE mode it is the Client (Your End) that negotiates the High port to be used during the actual file transfer, so it can select an open port. Whereas with PORT mode it is the FTP server that selects the High Port an it can select a blocked port as it does not know your firewall configuration.

2. Due to the continued testing we were doing (in a test environment not production) the ISP's Firewall treated it as an attack and Black listed our IP address.

Hope this helps someone in the future.

>No high-priority updates for your computer are available -- checked.
>
>I just tested couple of routines I have, VFP modules with direct WinINet calls -- no problem at all.
>
>API calls tested:
>FtpFindFirstFile
>FtpGetCurrentDirectory
>FtpSetCurrentDirectory
>InternetCloseHandle
>InternetConnect
>InternetFindNextFile
>InternetOpen
>FtpCommand
>InternetGetLastResponseInfo
>InternetReadFile
>
>It could be some Windows firewall issues.