2 Intern

 • 

7.9K Posts

December 31st, 2005 00:00

if you're already behind a router, ditch norton and call it a day

2 Intern

 • 

2.5K Posts

December 31st, 2005 00:00

Try configuring Norton Firewall.  Add all your computers IP addresses (you can add a range of IPs as well) to the Trust zone of your active setting.
 

51 Posts

December 31st, 2005 04:00

As mentioned, I have run the Home Networking Wizard (result looks like your screen shot), it adds the address range for the router.  When I try to add any additional addresses individually or in a range it says they are already included.  Then I tried deleting that and entering individual IP addresses of the router and the machines and still no luck--access denied.  However, once I drop the firewall I can instantly access all of the shared files.  Then if I enable it again I can STILL open and close the shared folder with no problems...until I reboot either of the computers...then I'm locked out again until I drop the firewall on the desktop.

I think the program is doing such a good job of hiding the computer, that even the machines in the trusted zone cannot find it!  I suppose everyone who uses Norton has this problem and just deals with it...or I am missing something.

Why do I have a security program on a computer behind a router?  I like the firewall for the simple reason that it monitors outgoing traffic (can you say trojan?  Which could come from opening an email or clicking on an executable on a thumb drive), and the anti-virus and spam control is necessary whether you are behind a router or not.

Ken

2 Intern

 • 

7.9K Posts

December 31st, 2005 05:00

kenp, your point is well taken, but you'll need to decide whether the outbound protection is worth the pain of dealing with norton (there are hints that the final vista will monitor ourbound).

personally, i just use windows firewall and stay current on updates -- I do this mainly for protection against one of my other LAN computers becoming compromised and hurting this one.  I figure my router can handle anything else external.

for trojans, current AV software and some sort of spyware protection is the way to go.  once it's installed on your machine, it's really too late for your firewall to do anything about it -- and there are any number of ways that a running trojan could get around a software firewall.  actually, the real thing to do is not be running as an administrator -- that will stop nearly everything dead in the water.  it's probably the easiest step to take and one of the most effective, unless you have software that won't run with basic rights

51 Posts

December 31st, 2005 15:00

All very good advice.  Each of us have our preferences.  Not running as administrator is the way to go, but I do so many tasks so frequently that require admin rights, that it becomes very tedious to log off and on again.   As for me, right clicking and disabling long enough to poke a hole in the firewall each session is not that much trouble.  I don't need access to the other computer everytime I boot up one of the laptops.  I was just wondering if anyone else had dealt with the same problem and found a software solution that I may have missed.  Despite the ability to enter IP addresses on "trusted" lists, most firewalls worth their salt are not very friendly to other computers when it comes to incoming traffic.  Their strength is also their weakness in this case.

Ken

Message Edited by kenp2002 on 12-31-2005 11:34 AM

Message Edited by kenp2002 on 12-31-2005 11:43 AM

2 Intern

 • 

2.5K Posts

January 1st, 2006 01:00

Have you reconfigured the firewall rules to allow File and Printer Sharing too?
 
 

51 Posts

January 1st, 2006 15:00

Yes I did that.  Even allowed "Any" computer rather than just the specific IP's, or the network range.

2 Intern

 • 

7.9K Posts

January 1st, 2006 16:00

i had the same problem with ZA free a few years ago when I tried it.  it wouldn't allow file sharing of lan computers in my trusted zone -- they don't me I had to buy pro for that at which point I dumped it

2 Intern

 • 

2.5K Posts

January 1st, 2006 22:00



@kenp2002 wrote:
Yes I did that.  Even allowed "Any" computer rather than just the specific IP's, or the network range.



In My Network Places on other computers, can you see the shared folders under your XPS? 

It may help to know when the "Access Denied" message occurred - whether if you can see them but just can't go in to browse their content or no shared folder is being shown.

BTW, was "Access Denied" the full message?

 

PS.  Personally, I never have a problem sharing files and printers through ZA Free :smileytongue:

Message Edited by esquire on 01-02-2006 08:34 AM

January 2nd, 2006 01:00

I had the same problem,,,    Here is what worked for me,  All the rules have to be uncheck and insted of permitted,,   And make shore it is on the Default network, AE, (HOME, OFFICE, and So on)
 
also add the computer to the trusted sone,,,   i had the exact same problem but now i'm free to share
 
To disable rules related to File and Printer Sharing
  1. Open Symantec Client Firewall.
  2. Click Client Firewall >Configure >Advanced >General.
  3. Find the Block Windows File Sharing rule, and uncheck it.
  4. Find the Default Inbound NetBIOS Name rule, and uncheck it.
  5. Find the Default Inbound NetBIOS rule, and uncheck it.
  6. Find the "Default Block Microsoft Windows 2000 SMB" rule, and uncheck it.
  7. Click OK.
    If you close the window instead of clicking OK, your changes will not be saved.

Once you have disabled these four rules, you should be able to use File and Printer Sharing for Microsoft Networks with Symantec Client Firewall enabled.

These instructions are based on the default rules after installing Symantec Client Firewall. If you are using custom rules, then you need to modify the rules to allow traffic on the necessary ports. See References for more information.
 
 
I GOT THE INFO FROM THE SYMANTEC WEB SITE

51 Posts

January 2nd, 2006 02:00

The folders that I am sharing are indeed visable in My Network Places.  Clicking on them when the firewall is down yeilds their contents, when it's up the error message is as follows:

(share name) is not accessible.  You might not have permission to use this network resource.  Contact the administrator of this server to find out if you have access permissions.

The network path was not found

51 Posts

January 2nd, 2006 02:00

I made those changes and it still wouldn't work...hmmm
 
Ken

Message Edited by kenp2002 on 01-01-2006 10:26 PM

2 Intern

 • 

2.5K Posts

January 2nd, 2006 23:00

Try allowing NetBIOS in your firewall rules.
 
 
No Events found!

Top