ZoneAlarm Personal Firewall Help
The following list of steps are intended to guide you through the steps of using GuildFTPD on a computer that accesses the Internet through ZoneAlarm Personal Firewall (free version). Some of the steps listed might help you configure other similar hardware or software. You'll need to be familiar with your software, so if you just purchased it, you may want to read the documentation and visit the Zone Labs web site for additional information if something isn't quite clear.
IMPORTANT NOTE: These instructions were written based on ZoneAlarm Personal Firewall 2.6.357. If you don't have this version, these instructions may not apply.
It is assumed that your computer it directly
connected to the Internet and you do not also use a router to share your
Internet connection. If you share your Internet connection and have a router,
you'll need to set it and GuildFTPd up first. Then, you can configure the
firewall. Otherwise, you shouldn't need to do anything to GuildFTPd (that means
don't set up the passive support), just set up ZoneAlarm.
- Open the ZoneAlarm Personal Firewall icon from the Start Menu (or right-click
the icon in the systray and select Restore ZoneAlarm Control Center
- Now, start GuildFTPd
- ZoneAlarm should prompt you with a message similar to this one,
"Do you want GuildFTPd FTP Server daemon to act as
a server?"
- Check the box for "Remember this answer the next time I use this
program"
- Click YES
- Now, if you click the PROGRAMS tab of the ZoneAlarm Control Center, you should
see GuildFTPd Server Daemon listed
GuildFTPd should have four green check marks next to
it; two for Allow connect and two for Allow server.
- If GuildFTPd does not have all four green check marks, right-click on
GuildFTPd in the list and select
- Local Network --> Allow
- Local Network --> Allow server
- Internet --> Allow
- Internet --> Allow server
You should now be able to connect to GuildFTPd when it's running on the computer with ZoneAlarm Personal Firewall 2.6.357 installed.
Don't forget to check the syslog.txt and make sure that GuildFTPd is recording a Success audit for the ListenSocket Create and ListenSocket Listen options for your FTP port. If they aren't Success, you probably have another program running that is using the same port. You'll need to reconfigure GuildFTPd or the other program to prevent the conflict.