Configuring the FTP Server on Windows

PPM uses FTP to move files between machines. To transfer files between machines on a network, each source and destination machine must be running an FTP server. On UNIX platforms, this is standard functionality, but machines running Windows require additional FTP server configuration to function with PPM.

Before you configure the FTP server on a machine, make sure that the Windows user account (which PPM uses to open a connection) has access to the directories to which files are to be moved. Some FTP servers require that you map these directories to FTP aliases, and a configuration utility is usually provided for this (for example, for Microsoft IIS, the utility is Internet Services Manager).

Note: On Windows, most FTP servers, including Microsoft IIS, do not support drive letters. If you use FTP in PPM, the drive letter is removed from the base path. If your base path is d:\ppm940, then FTP tries to start from the ftp root directory and FTP fails.

To work around this, you must create an FTP alias. (For example, map /ppm940 to D:\ppm940.)

Configure the FTP server according to directions that the vendor has provided. For the File and Directory Chooser components to work, you must set the FTP server directory listing style to UNIX, and not to MS-DOS.

To set the directory listing style to UNIX:

  1. In Windows, open the Internet Services Manager.

  2. In the left pane, under Console Root, open the Internet Information Server.

  3. Select the machine name.

  4. Right-click the Default FTP site displayed in the right pane, and then click Properties on the shortcut menu.

    The Default FTP Site window opens.

  5. Click the Home Directory tab.

  6. Under Directory Listing Style, click UNIX.

  7. Test the connection by trying to open a session manually. If you can open an FTP session and navigate from one directory to another, then PPM can do this too.