I thought I'd share this with you. I recently installed Norton Internet Security (NIS) for some customers.
Just after the installation and update which went successful, I had a call again that they cannot access resources on the network. Truely, I found that network resources cannot be accessed. I battled with this for few hours then something came into mind, Is this a firewall issue?
Checked windows firewall and all was OK. Then I thought, disable the NIS and see what happens? Bingo! there the problem was.
I never thought this could happen especially when the're no special firewalls as its just 7 PC's on a peer-to-peer wireless network.
I share this with my colleaque at work and he knows how to configure the ip address on the NIS. I haven't tried that yet but to let you know some of these little programs could make you sweat.
Just to share.
A smart person knows what to say, but a wise person knows whether or not to say it.
yes mate, you will have loads of problems when you are implementing NIS on a peer-to-peer network, or even in an environment where all the nodes communicate with a single router. i had the same problem. i had a wireless router to which i had attached two laptops and a primary desktop. i was pretty sure that once every node was online i would be able to share files among them. but thanks to NIS being installed on each and every laptop and the desktop, it was preventing sharing of files, and also categorically denied access to and from the router which was obviously acting as the DHCP as well. i had to open up NIS and configure the related IP addresses on the network, adding them to the "Allowed" list, and within seconds i had cross network connectivity, and file sharing was working seamlessly. so the golden rule is whenever you have installed NIS put it on the "learn as it goes" mode where it will keep on asking for allow or deny access for anything that tries to communicate with the network. this will happen for the first few days within which NIS would have created a log of the programmes and processes that communicate with the network. anything else that doesn't work, you will have to manually configure it.
Picking pebbles on the shore of the networking ocean