使用PowerShell/WebClient从HP-UX FTP下载文件遇550错误

Hey there, let's work through that 550 FTP error you're running into when trying to pull a file from your HP-UX server to Windows using PowerShell. I've troubleshooted similar issues plenty of times, so here's what's probably going wrong and how to fix it:

Common Causes & Solutions #

1. HP-UX File Path/Permission Issues #

The 550 error almost always boils down to the FTP server not being able to access the source file. Let's rule out the basics first:

• Verify the file exists: On your HP-UX server, run ls -l /tmp/sourceFile.txt to confirm the file is actually in the /tmp directory.
• Check file permissions: Ensure the FTP user has read access to the file. If not, run chmod o+r /tmp/sourceFile.txt (adjust the permission flags if you need to restrict access to specific groups instead).
• Watch out for case sensitivity: Unix systems are case-sensitive! If your actual file is named SourceFile.txt (with a capital S) but your script uses sourceFile.txt, the FTP server will throw a 550 because it can't find the file.

2. Missing FTP Credentials or Incorrect URL Format #

Your current script doesn't include authentication details—if your HP-UX FTP server requires a username and password, that's a problem:

• Add credentials securely: Instead of hardcoding them in the URL (which is unsafe), use the NetworkCredential class with your WebClient object:

  $File = "d:\copiedfile.txt"
  $ftp = "ftp://my_Unix_Domain_name/tmp/sourceFile.txt"
  $webclient = New-Object System.Net.WebClient
  # Add your FTP username and password here
  $webclient.Credentials = New-Object System.Net.NetworkCredential("your-ftp-username", "your-ftp-password")
  $uri = New-Object System.Uri($ftp)
  "Downloading $File..."
  $webclient.DownloadFile($uri, $File)
  

• Test with IP instead of domain: Sometimes DNS resolution can cause unexpected issues. Try replacing my_Unix_Domain_name with your HP-UX server's actual IP address (e.g., ftp://192.168.1.100/tmp/sourceFile.txt) to eliminate that variable.

3. Passive Mode FTP Requirements #

Many modern FTP servers require passive mode for connections, and System.Net.WebClient doesn't always handle this reliably. Switching to FtpWebRequest gives you more control over FTP settings:

$sourceUri = "ftp://my_Unix_Domain_name/tmp/sourceFile.txt"
$destPath = "d:\copiedfile.txt"

# Create FTP request
$request = [System.Net.FtpWebRequest]::Create($sourceUri)
$request.Method = [System.Net.WebRequestMethods+Ftp]::DownloadFile
$request.Credentials = New-Object System.Net.NetworkCredential("your-ftp-username", "your-ftp-password")
$request.UsePassive = $true # Enable passive mode (critical for many servers)

# Execute download
try {
    using ($response = $request.GetResponse()) {
        using ($responseStream = $response.GetResponseStream()) {
            using ($fileStream = [System.IO.File]::Create($destPath)) {
                $responseStream.CopyTo($fileStream)
            }
        }
        Write-Host "File downloaded successfully to $destPath"
    }
}
catch {
    Write-Host "Error downloading file: $_"
}

This script is more robust and explicitly enables passive mode, which often resolves 550 errors caused by connection mode mismatches.

4. Check HP-UX FTP Server Logs #

If none of the above fixes work, dig into the FTP server logs on HP-UX for more details:

• Most FTP servers log activity to /var/log/xferlog or /var/log/messages. Look for entries related to your Windows machine's IP—they'll usually specify exactly why the 550 error was thrown (e.g., permission denied, file not found, or connection refused).

内容的提问来源于stack exchange，提问作者Karthikeyan