Symantec Endpoint Protection Port Sniffer?

Hello!  I am going to provide a lot of data on my problem.  Sorry if anything is extraneous!

 

Here's the problem: I was wondering if the Endpoint Protection Port Sniffer could be blocking internet traffic to and from my computers.  Additional data is as follows:

 

I have 5 computers in my house.  1 is Windows Home Server 2011, 4 are personal computers running Win7 x64.  Three of the computers are running Norton 360 and two are running Symantec Endpoint Protection (the home server and one laptop).  I also have 4 wifi enabled i-devices.

 

I switched from DSL to cable internet 20 days ago.  The home server is hard-wired to the cable modem.  All other devices are connecting by wifi.  The internet is being managed by a combination cable modem and wireless gateway, Motorola SBG6580.  Since I switched to cable internet, two computers and two of my i-devices have not been able to consistently connect to the network and receive the internet stream.  Yes, they connect to the network just fine.  No, they are not consistently receiving the internet stream.

 

Last weekend, the laptop running Endpoint Protection stopped connecting to the network and flagged suspicious activity from an IP address.  The problem is that the IP address listed is the home server, the other computer running Endpoint Protection.  I know the home server performs "health assessment" scans every so often, but I think Endpoint Protection is reacting negatively to those scans and then blocking the port.

 

I thought I narrowed my internet woes to the wireless gateway, but then this port sniffer message came up.  So, could it be Endpoint Protection messing with the internet in my home network or do I have a bad wireless gateway?  My i-devices are not virus protected, but for some reason they don't consistently connect to the network...  Do I need to add my home server to a list of "accepted connection sockets" or something?  Could it be the wireless protocol (e.g. 802.11 b or g or n)?  I'm pulling my hair out and I don't want to buy new equipment if it isn't going to solve the problem.

 

Any information this community can provide will be greatly appreciated!

 

-dj