08-09-2010 11:22 PM
Hello to all. I am running Norton Security Suite 220.127.116.11 and no matter what I do I can't get in to my FTP server. When I turn the firewall off I get in with no problems. I have set incoming rules to allow access to ports 20 and 21 as well as program rules allowing full access for my FTP server. Has anyone here experienced this and had success creating rules for incoming traffic? I've been running and FTP server for several years but recently switched over to Norton and that's when the problem started. Evidently I'm missing something.
Thanks for any suggestions.
Solved! Go to Solution.
08-11-2010 11:41 AM
Well, with 52 views and no responses it seems that no one knows - and evidently Symantec doesn't care. I guess I should just uninstall it anyway since its file, ccSvcHst.exe is constantly hogging up resources.
08-11-2010 12:02 PM
Welcome to Norton Community!
Make sure that you have moved the rule (to allow the access to ports 20 and 21) to the top of the list. If the problem persists, create a new firewall rule to allow all communications to your FTP server ip address, and then move it to the top of the list. Refer to the instructions from the following Symantec Article:
08-11-2010 01:13 PM
Thank you very much. Moving the rule to the top seems to have taken care of the issue. I'll test a few times and then mark this thread as Solved.
Can you point me to a solution for ccsvchst.exe constantly having high (40-50+ %) CPU usage? I can reboot and in only a few minutes the usage is high again and stays high. For now, I've disabled scheduled scans and anything else I thought might be causing it but to no avail.
08-12-2010 04:19 PM
The rule was working fine but I did a total uninstall of Norton 360 due to the CPU usage issue that I described. I reinstalled the package, set the same exact rule and program permissions and it won't allow me through. I then added a rule to allow all and this works unless I change the rule to add port 21 in place of ALL. Both rules were placed at the top of the list.
Is setting a rule that allows ALL communication on all ports not equivlent to turning off the firewall? Any idea why the rule might stop working when nothing has changed?
Thanks again for your or anyone else's assistance.
08-12-2010 10:11 PM
Thanks Dave. I realize I left port 20 out of my post but I had it in the rule. I did another restart - actually a cold start and left the machine off a minute - and it works now. Also, a complete uninstall/reinstall with Revo seems to have fixed the high CPU usage issue as well.