|
 
| |
Support - Bug Pages
Error messages
 | PASV (passive-mode) data connections fail -
the version of WFTPD and WFTPD Pro 3.21 Release 2 that was released on
2/29/2004 was not fully regression tested. [This is another one of the
reasons we ask that discoverers of vulnerabilities contact us before
publishing that information.] As a result, a bug crept through to the
release. We have placed a new version of WFTPD and WFTPD Pro 3.21
Release 2, dated 3/3/2004, that does not have this problem. |
| WFTPD Pro Control Panel applet aborts on Windows
2000 - WFTPD Pro 3.20's initial release included an incorrect CPL file,
that does not allow opening of the User Configuration Dialog on a server that
is configured to use the Windows security model. The corrected CPL file
is part of the current shipping version of WFTPD Pro. |
| Home Directory reported as "deleted" - WFTPD Pro, with
the "Windows" Security Model selected, would report "your
current directory and your home directory have been deleted", followed
by the user being disconnected. The directory wasn't deleted, it just
was not available to the security context that WFTPD Pro was running under,
and the check was being performed in the wrong security context.
Fix: Upgrading to WFTPD Pro 3.10 R2 will fix this problem. If,
for some reason, you cannot upgrade, then you could simply assign sufficient
rights to the user context that runs the WFTPD Pro service. |
| WSAESOCKTNOSUPPORT message on Win95 - WFTPD and WFTPD Pro take advantage of the
presence of the file WS2_32.DLL as an indication that you have an installation of Winsock
2.0 on your system. Unfortunately, some programs have taken to installing this file (and
frequently WS2HELP.DLL as well) on Windows 95 without the other elements of Winsock
2.0.
Not only is this against Microsoft's license agreement with Winsock 2.0 developers, but it
also causes programs that link to WS2_32.DLL (like WFTPD and WFTPD Pro) to fail in ways
that suggest TCP/IP is not properly installed. Reinstalling TCP/IP won't help - you're
reinstalling Winsock 1.1, which doesn't have WS2_32.DLL, so the file is neither removed
nor overwritten. Uninstalling the bad app doesn't help either - most uninstall programs
recognize that WS2_32.DLL is a 'system component' and should not be removed.
Fix: The fix is generally to remove WS2_32.DLL from your system. As you are
removing a component that might possibly have a good reason to be there, we recommend
first renaming the file (for instance, to WS2_32.LLD), rebooting and checking that
everything works okay - especially, any network tools, and especially any recent network
tools. |
| WSAEADDRINUSE (especially on Windows 2000) - This message has a
very simple cause - WFTPD or WFTPD Pro attempted to bind to the FTP port (or
the port you asked it to), and the system informed it that the port was
already bound and listening. You can confirm this by opening a command
prompt window, and running the command "netstat -an". You'll
see a list of all connected and listening sockets, and one of these will be
listening on port 21 (or whatever port you asked WFTPD / WFTPD Pro to use).
Fix: On Windows 2000, this is almost invariably caused by the
installation of Microsoft's Internet Information Server; in particular, its
FTP service component. For information on disabling any particular
third-party program, please contact that person or organisation - we cannot
support other people's software, in case we misunderstand it and end up
damaging your system.
In Windows XP, you can find out which program is acting as an FTP server by
running the command "netstat -ano", which will list not only all
the TCP and UDP servers (check for one listening on port 21), but also the
Process ID, which you can look up in the list offered by Task Manager.
To bring up Task Manager quickly, simply hold down Ctrl and Shift, and press
Esc. |
|
