D
Dr. Bob
Now that I am on a DSL I take firewall based security more seriously.
However, my ftp programs are giving me fits. Neither cuteFTP nor
FileZilla will work properly - I get a failure to logon msg back from my
ftp server.
This problem goes away and I can login fine when I simply disable the
Windows XP filewall (via Wscui.cpl).
I have used netstat and taskslist to determine the ports being used
by cuteFTP and have tried making its primary port an exception on the
firewall list. I have also tried putting the ftp program itself on the
firewall exception list. Didn't help a bit. Yes, the ftp program does
use some other ports above 1024, but since these are variable trying to
add them to a port exception(s) list is not going to work.
Anyone out there perhaps have a suggestion for getting deeper into this
issue and zeroing in on the problem?
Machine - AMD dual; Windows XP-SP2, FIREFOX and/or Netscape browser, ATT
DSL; affected ftp apps are: cuteFTP, FileZilla, ATT ftp.
Thanks!! Dr. Bob
However, my ftp programs are giving me fits. Neither cuteFTP nor
FileZilla will work properly - I get a failure to logon msg back from my
ftp server.
This problem goes away and I can login fine when I simply disable the
Windows XP filewall (via Wscui.cpl).
I have used netstat and taskslist to determine the ports being used
by cuteFTP and have tried making its primary port an exception on the
firewall list. I have also tried putting the ftp program itself on the
firewall exception list. Didn't help a bit. Yes, the ftp program does
use some other ports above 1024, but since these are variable trying to
add them to a port exception(s) list is not going to work.
Anyone out there perhaps have a suggestion for getting deeper into this
issue and zeroing in on the problem?
Machine - AMD dual; Windows XP-SP2, FIREFOX and/or Netscape browser, ATT
DSL; affected ftp apps are: cuteFTP, FileZilla, ATT ftp.
Thanks!! Dr. Bob