FTP
There are 6 entries for the tag
FTP
I find that helping people troubleshoot FTP connectivity issues is much easier if they have PowerShell installed. I can just have them run the NetCmdlets ftp cmdlets with the –debug switch, which displays a trail of information about the communication over the wire. In this way you can see every command send to the server and every response coming back from the server, including what ports a server is attempting to use for ftp data connections. Very often ftp transfer connectivity errors are the...
Its easy to forget about the –debug parameter, but a lot of times it can be very helpful, especially with NetCmdlets where in many cases –debug will output the protocol interface (the “PITrail” as we call it at /n software) of the connection. The PITrail includes a trail of communication between the cmdlet and the remote host it is talking to. Rob emailed me to ask for help diagnosing a 425 error he was getting when using the NetCmdlets get-ftp cmdlet. As I described to Rob, in a nutshell the 425...
Every so often I get a question from someone who wants to transfer files between two FTP servers. In order to do so, they usually have to connect to server 1, download the files, and then connect to server 2 and upload the files. The process could go much sooner if they could eliminate the extra transfers and just copy the files directly from server 1 to server 2. It turns out this is possible, and is in fact mentioned in the FTP spec (RFC 959), but most people don't realize it. Also most servers...
One of the most common questions I get about FTP has to do with error 425, "Can't open data connection." This is indeed a protocol level error that is defined in the RFC. Its meaning is obvious: the data connection (for a directory listing, upload, or download) was unable to be established. First - the most common solution: change the active/passive mode settings. But that might not work, and if it does its only a band-aid covering up the real problem. As I've mentioned in the past, one of the most...
update: here's an updated function for uploading an entire directory tree: ## ftprecursiveupload.ps1: Recursive FTP Upload## Uploads a directory tree to a remote FTP server.## Returns an objects containing information about the files transferred.function upload-directory { param( [string] $server = $( Throw "You must specify an FTP server to logon to."), [string] $dir = $( Throw "You must specify a local directory to upload (ie, C:\Testing\FTPTest\)"), [switch] $overwrite = $false, [System.Management.Automati...
Some examples of using NetCmdlets in PowerShell. The FTP NetCmdlet supports plain and secure (both SSL and SSH) FTP connections right from the PowerShell console. List files on a remote server: PS C:\> get-ftp -server myserver -user lancer -password mypass The same, but using SSL (auth-tls): PS C:\> get-ftp -server myserver -user lancer -password mypass -ssl explicit And again, but using SSH 2.0: PS C:\> get-ftp -server myserver -user lancer -password mypass -ssh Find the files on a remote...