WebSTAR 4 Manual & Technical Reference
WebSTAR FTP Troubleshooting
This chapter helps you locate and fix problems with the WebSTAR FTP server.
FTP Server Troubleshooting
If you see errors on startup, in monitors, logs or users report problems, use this list of common problems to locate and fix your FTP server.
See also
How to Get Help
,
WebSTAR Debug Plug-In
and
General Server Troubleshooting Guidelines
.
The WebSTAR FTP Server Startup Errors
Error "FTP port already in use, server not running".
-
If you have
another FTP server running
on the same machine, the first one launched will be listening on port 21 for control transmission, and if WebSTAR is launched second, the FTP Plug-In won't be able to listen on that port. You can't change this port number.
Error "startlistner failed (-3247)".
-
You may have a second copy of WebSTAR running on the same machine. While the Web server can listen on multiple ports, the FTP server cannot. You should remove the FTP Plug-In from the
Plug-Ins
folder of the alternate server.
Error in initialization: "
The FTP Plug-in could not open the "WebSTAR FTP Users" file"
.
The
WebSTAR FTP Users
file was not found in the
WebSTAR FTP Data
folder in the
Plug-Ins
folder.
-
If you have not yet created any FTP users entries, don't worry, WebSTAR FTP will create the file for you.
-
If you do have FTP user entries, quit the server, locate the file or a backup, make sure it's in the right folder and restart WebSTAR. Otherwise, you'll have to re-enter all the FTP user entries.
Error "'could not get ftp* configuration resource'"
-
The folder
WebSTAR FTP Data
is probably missing from the
Plug-Ins
folder. Make a new folder of that name or re-install the WebSTAR FTP server, and the server will work properly.
Error
"WebSTAR FTP: Could not determine IP address of server"
-
The DNS server is not responding properly: it may be down or otherwise inaccessible. WebSTAR FTP is trying to do a DNS lookup of it's own IP address, and the lookup is failing for some reason.
-
First, try using a web browser or FTP client to check another server. If your DNS server is down, you will get an error.
-
If that works, make sure you have entered a server name in the Admin Web Settings panel
File Names and Paths
.
-
If the FTP server still doesn't work, check your TCP/IP control panel and work with your DNS administrator to check your DNS records.
Errors and Error Codes
-
Bad Folder
entry in the Log means that the folder has a slash (/) somewhere in the path. Check your hard drive and enclosing folders for this character, and remove it.
-
Write Stream Error -5
means that the client has closed the connection. This is informational only, does not indicate a problem with the server or the client, and does not require any action by an administrator.
-
Error -17
means that the request failed. This usually occurs when the server requests that the client close the connection and the client has already closed the connection. In most cases, it does not indicate any problem or require any action.
-
Error -550
(Write Permission Denied): this user account does not have the "Upload New Files" option checked, and the user tried to upload a file.
See
FTP Users: Access Control
to change these settings.
-
Error -552
(Exceeded storage limit): the user account has reached the folder size limit and the user has tried to upload additional files.
Client Errors
Server does not respond to requests outside company
If your FTP server is behind a firewall, the network administrator will need to ensure that ports are available for access. Another option would be to configure the specific IP address for the server machine to be outside the firewall.
See
Firewalls and Server Ports
.
Folders Not Visible in FTP Client
Can't Download WebSTAR Files
-
WebSTAR checks the Mac OS Creator Code before allowing users to download files. As a security feature, any files created by WebSTAR, with the Creator Code
WWWω
, will not be transferred. This prevents accidental or malicious downloading of server settings files.