The following list provides
information on common problems you may encounter in setting up a
remote folder, and how to resolve them:
The Dreamweaver FTP
implementation might not work properly with certain proxy servers,
multilevel firewalls, and other forms of indirect server access.
If you encounter problems with FTP access, ask your local system administrator
for help.
For a Dreamweaver FTP implementation,
you must connect to the remote system’s root folder. Be sure to
indicate the remote system’s root folder as the host directory.
If you’ve specified the host directory using a single slash (/),
you might need to specify a relative path from the directory you
are connecting to and the remote root folder. For example, if the
remote root folder is a higher level directory, you may need to
specify a ../../ for the host directory.
Use underscores in place of spaces, and avoid special
characters in file and folder names wherever possible. Colons, slashes,
periods, and apostrophes in file or folder names can prevent Dreamweaver from
creating a site map.
If you encounter problems with long filenames, rename
them with shorter names. On the Mac OS, filenames cannot
be more than 31 characters long.
Many servers use symbolic links (UNIX), shortcuts (Windows),
or aliases (Macintosh) to connect a folder on one part of the server’s
disk with another folder elsewhere. Such aliases usually have no
effect on your ability to connect to the appropriate folder or directory;
however, if you can connect to one part of the server but not another,
there might be an alias discrepancy.
If you encounter an error message such as “cannot put
file,” your remote folder may be out of space. For more detailed
information, look at the FTP log.
Note: In general, when you encounter a problem with an FTP
transfer, examine the FTP log by selecting Window >
Results (Windows) or Site > FTP Log (Macintosh), then clicking
the FTP Log tag.