-1

I have built a script for downloading files from an FTP server. The script is working well with all the servers I have tested expect for one. For this server I am able to get the directory listing, but when I attempt to download a file it fails and returns a "421 Service Not Available, closing control connection" error. Below is the code I am using for downloading a file.

function Get-FtpFile
{
    Param ([string]$fileUrl, $credentials, [string]$destination)
    try
    {
        $FTPRequest = [System.Net.FtpWebRequest]::Create($fileUrl)
        if ($credentials)
        {
            $FTPRequest.Credentials = $credentials
        }
        $FTPRequest.Method = [System.Net.WebRequestMethods+Ftp]::DownloadFile
        $FTPRequest.UseBinary = $true
        $FTPRequest.UsePassive = $true

        # Send the ftp request
        $FTPResponse = $FTPRequest.GetResponse()

        # Get a download stream from the server response
        $ResponseStream = $FTPResponse.GetResponseStream()

        # Create the target file on the local system and the download buffer
        $LocalFile = New-Object IO.FileStream ($destination,[IO.FileMode]::Create)
        [byte[]]$ReadBuffer = New-Object byte[] 1024

        # Loop through the download
        do {
            $ReadLength = $ResponseStream.Read($ReadBuffer,0,1024)
            $LocalFile.Write($ReadBuffer,0,$ReadLength)
        }
        while ($ReadLength -ne 0)

        $ResponseStream.Close()
        $ReadBuffer.clear()
        $LocalFile.Close()
        $FTPResponse.Close()
    }
    catch [Net.WebException]
    {
        return "Unable to download because: $($_.exception)"
    }
}

I am able to download files from this server using the Windows File Explorer FTP so I do not think this is a problem with the server itself.

One interesting thing I have noticed through testing is that when the server returns the directory listing each filename has a trailing NULL included. I have tried downloading files both including and not including this trailing NULL, both attempts produce the same error code.

Has anyone seen a similar error before? Or is anyone aware of the differences in the way that Windows File Explorer uses FTP compared with the PowerShell script I have listed above?

MRoth
  • 63
  • 6
  • A [Wireshark](https://www.wireshark.org/) dump would reveal if the client behavior is different. – vonPryz Apr 03 '20 at 05:47
  • Or if you are not familiar with Wireshark, post [`FtpWebRequest` log file](https://stackoverflow.com/q/56220620/850848), as well as a log file from any FTP client that can download the file. – Martin Prikryl Apr 03 '20 at 06:22
  • Thank you guys for the recommendations, unfortunately I do not have access to the server myself, a client of ours is accessing it from a secure location. Martin I will attempt to implement the .NET tracing ability in my code. I will not be able to get test results from this server until next Tuesday. But when I do get the log files I will post them here. Thank you again for the assistance. – MRoth Apr 03 '20 at 18:29
  • Hello, I was able to add the .NET tracing ability to my script, and it turned out I was not correctly removing the trailing NULLs. After correcting this problem I am now able to download all files needed from the server. Thank you for the assistance. – MRoth Apr 08 '20 at 19:13

1 Answers1

0

This issue I had was I was not correctly removing the trailing NULL in each filename. Once I was able to correctly remove the NULLs I no longer had any issues.

If anyone runs into this problem in the future, encountering 421 errors when attempting to download files, check if the filenames being provided by the directory listing have trailing NULL characters. If so, delete these characters from the filename strings before attempting to download each file.

MRoth
  • 63
  • 6