I was trying to get back on topic, just politely. I thought pointing out that the error occurred regardless of that setting would probably accomplish that but I guess I wasn’t clear.
Starting getting the compromised message this morning on my Samsung S7 phone. Noticed last evening that a Chromecast (1st gen) plugged into Samsung TV was flashing, which seemed strange since no device of mine was trying to access it. Didn't think too much of it until the message this morning. I immediately unplugged the Chromecast and the compromised message went away.
Let's get back on topic. This Windows setting has nothing to do with a detection on the Norton Mobile Security product.
We have to wait for Norton to analyse the logs received.
Unfortunately it doesn't apply in my case. All four of my Windows pc's connected to the router show it as "Private", not "Public". This setting hasn't been changed for years.
I found that our laptop (not main PC that was directly wired to router) had the Norton router settings as 'public'.
That is actually a more secure setting for your network, as it assumes you are connecting to public networks and provides tighter controls over access to your computer.
Allowing Full Trust gives full access to your computer by any device that can connect to router.
Had same problem on 2 android phones and solved by looking at previous blogs. I found that our laptop (not main PC that was directly wired to router) had the Norton router settings as 'public'. Don't know why, have never changed these settings, suspect a Norton update.
Use: Open Norton (on Laptop in my case) > Settings > Firewall > General Settings > Network Trust. Then Configure + and your router should appear, change from 'public' to 'Full Trust'.
I would check all Norton enabled windows devices connected to your router.
Hope this helps.
I have no doubt it’s a false positive, at least in my case and hopefully for you guys too.
Kevinworking
I just installed a google wifi mesh. The Norton version number is 4.0.4024, same as you. I get the same compromised message. You are not alone. I believe the network is NOT compromised. I'm watching for a fix from Norton.
Hi,
As mentioned above, I have the same issue with my HTC 10 phone. Like the others, I'm having issues with my 5GHz band only, and no issues with my 2.4 Ghz band. However, I'm only having issues with my NETGEAR router which is setup as an access point. I get the ARP Spoofing message when I'm connected to my NETGEAR. When I use my dual band router/modem, I have no issues on Norton Mobile Security with either the 5Ghz or the 2.4 Ghz band. When I do a speed test on my 5GHz NETGEAR router, my download speeds are significantly reduced as compared to my no-issue-wifi modem/router. I've even updated the firmware on my NETGEAR and also changed the wifi SSID and password to no effect.
Hi, I also have the same warning in the last 3 days on my Galaxy Tab when casting video using Chromcast. Is it because I use the Google Mini and Chromcast together? One is playing music and the other is playing movie?
Sunil_GA,
Thank you for your response. We appreciate it.
Hi @Gavacho,
Thanks for the logs upload. We have received your logs uploaded and forwarded to concern team. I will update once we have more information from the team.
Peterweb, I understand this is the holidays. Unfortunately, the bad guys out there aren't impressed. My biggest concern is that receipt of my logs were never acknowledged, and I was never told they were even working on it. A "please standby, we received your logs and we're working on it" would be nice. I use a lot of Norton products, and it's important to know that if something goes wrong, Norton is there to help. Do we all just shut down our systems and hope someone out there remembers us? A business absolutely, positively has to inform the customer what is going on. We don't expect a daily update, but again, just an official "we're working on it." would be appreciated. Clearly I'm not the only person encountering this problem.
There is too much crap going on out there nowadays and we need to know our problems are taken seriously.
It is the Christmas holidays. Things may take a little longer.
Even without the holidays, it takes time to parse the logs, figure out what is happening, find the code that needs to be fixed, fix the code, and test thoroughly before releasing a fix. It is not something that can be done in a couple of days.
Richj44,
I am surprised at the length of time they are taking to respond. I understand if they don't have a solution, but they should at least let us know they are working on it. I uploaded my logs, and haven't heard a peep from them since. That in itself makes me concerned. Is there something going on we should know about? Even a little feedback would help.
Just adding a "me too" here in hopes that more data helps solve this faster :). I am experiencing this problem on an LG V10 phone and an AT&T branded tablet. I just had my ISP (AT&T) upgrade my internet last week and they swapped out the old router for a Pace 5268AC router. I have also added a Netgear EX3700 dual band extender into the network. So far I have only seen the error when connected to the 5Ghz side of the extender. Never on the 2.4 side, and never when connected directly to the router.
Yes the ARP Spoofing has been reported by Gavacho above in this thread. See the attachment in this post. https://community.norton.com/en/comment/7756631#comment-7756631
I also see this problem when using my mobile phone. When I click on more details it has a message about ARP Spoofing detected. Is anyone else also seeing this message from ARP Spoofing?
I only started getting this message after I switched my internet providers and after they finished installing their internet. It has also affected my ability to connect to my sonos devices and I've head to re-add them to my network.
Same problem here. I just installed Norton on my Samsung S5. I have a range extender. When I logon to the extender via the phone I get the "compromised" error. I only have the 2.4ghz activated. I am not using NWP.
I just started receiving this notification right after adding an Amazon Echo to my home network. Since it appears Echo also has a separate network, could it be something conflicting there?