I was using the Filezilla client to connect to a Filezilla server on the LAN the other day, and I could not get a directory listing of the FTP server and I would have the following error “Error: Failed to retrieve directory listing” . I had opened port 21 on the firewall of the FTP server, but still could not get access.
I had to do the steps below, and after this I got access and a directory listing right away.
Open Windows Firewall under Control Panel.
If using Vista, click “Change Settings”
Select the “Exceptions” tab.
Click “Add program…”
Do NOT select “FileZilla Server Interface” from the list, instead click on “Browse…”
Locate the directory you installed FileZilla Server to (normally “C:Program FilesFileZilla Server”)
Double click or select “FileZilla server.exe” and press open (Once again, NOT “FileZilla Server Interface.exe”)
Select “FileZilla server.exe” from the list and click “Ok”
Verify that “FileZilla server.exe” is added to the exceptions list and that it has a check mark in the box next to it
Press “Ok” to close the window
I had a few servers that were hitting and sustaining 100% CPU for long periods of time. They were either dual or quad core XEON processors, and the servers normally sat below 10% CPU usage. I ran task manager and found that the monitoringhost.exe process was using all of the CPU cycles, and so i set about researching the issue.
Monitoringhost.exe is the agent for System Center Operations Manager 2007 that is installed on client systems, and it thankfully has a patch out to fix this issue. Below is the link to the patch on the Microsoft website.
To download the hotfix, you need to enter a valid email address and then Microsoft email you a link to the file and a password to extract the file.
Download and install this patch to each of the SCOM server and the affected servers and you will not have any issues anymore.
I had a Windows 2008 server that I was attempting to install the Symantec Endpoint client on, but the client would not install, and the following message was left in the event log:
Symantec Endpoint Protection (SEP) Installation fails with the following error “Symantec Endpoint Protection has detected that there are pending system changes that require a reboot. Please reboot the system and rerun the installation.”
I rebooted the server and then tried to install the client again, but the same error would appear.
I found that there was a registry entry that was giving me grief with the install, and here are the instructions that I used to fix the problem.
- Navigate to:
- Back up the registry key
- Delete the registry key
- Install the software without restarting the computer first (Restarting the computer may result in the registry key being placed back in the registry before installation.)
- Restore the registry key from the backup location.
NOTE: If you are running Windows Vista look for this key - HKEY_LOCAL_MACHINE\SYSTEM\Current\ControlSet001\ControlSessionManager\PendingFileRenameOperations
* Thanks to Bill for this Windows Vista suggestion.
The easiest way to do this is via a command prompt.
Press the WINDOWS key and R at the same time to bring up a RUN box, then type CMD.
At the command prompt type powercfg -h off and then press ENTER.
This will disable hibernation and also delete any hiberfil.sys files on the hard disk.