Day 30 of my official norton captivity. After contacting “Selvakumar.S EMPLOYEE” with details of the norton malfunction, I was told to “Please wait till we get an update on this.”.
Hmmm… pay USD 126.59 and suffer a norton created loss of function. norton wants us all to suffer in silence. Silently without refund for a dysfunctional software glitch. Of course they get their panties in a knot when I cancelled my subscription, because you know it’s sounfair to expect norton to actually fix their self induced malfunction.
Pulled my credit card information from norton account billing information. More angst at norton customer exploit central! How could a customer not understand!! norton is hard at work valiantly laboring to fix these problems…..
Yep, I look forward to a fix. Perhaps in the afterlife??
Having zero doubt this is a Norton firewall issue, on your part I will tag the Norton employee who previously worked with you for an update directly. If an update is the “fix” it shouldn’t take more than a year to see that update appear. Norton has an emergency update service they can use as a channel to direct a possible fix to specific targets is they so choose. I have seen it running my side.
On the spectrum of a fix, when new releases do come they don’t even correct the issues already presented yet appear to break something new in the process. Just an observation.
@Selvakumar.S Any update for the fix release to correct this issue? This thread was opened in September 2024, shouldn’t this have been corrected eons before now? Thanks in advance.
Just to let you know that I had no problem with screen casting until roughly one week ago. I thought it was a driver issue and spent hours trying to roll back drivers. I came across this thread. I disabled the Smart Firewall and bingo, screen casting works. You’re not alone
Hello @BrianG_Stein, sorry you’re in the growing crowd of of customers norton is failing to support.
For a while I thought if I researched and experimented I could get norton to work. A couple problems with that thinking…
First; norton has so badly broken the firewall there is no user option that will fix it. Believe me, I’ve tried. Norton has taken almost all user setting choice away from the user. The few user firewall choices left are then reversed by the norton software soon after user input. Doesn’t matter in the end, the firewall is so poorly programmed the only effective user input is to turn the firewall off, or find an entirely different software vendor.
Second: As a paying customer, why am I trying to fix a norton self inflicted malfunction? Isn’t that what customer support is supposed to do? What norton is doing is giving us the illusion of support. When we are too noticeable in our complaint norton will send us a Private Message, asking us to “be patient” and that our concern has been “forwarded to the appropriate group”. Norton will assign a tech to remotely dig around your computer to do things we have already done, like check for updates to Windows and also check for norton updates. The norton tech will then remotely try to have your norton debug logs upload to norton, but when they are 6.5GB like mine are the upload will fail. The norton remote tech will be asleep at home by the time upload fails. I was once advised to pay for an upload service so norton could get my debug logs. Really?? Isn’t data retrieval a customer support responsibility? After I refuse to keep the norton Private Message tactic private, norton then publicly asks I remain patient, as the appropriate group is working on a future update to address this issue.
Bovine exhaust. What norton wants is for us to suffer in silence while paying full price for dysfunctional software. If we remain quiet, norton will do nothing to fix this malfunction. I believe the norton plan is to delay into the afterlife if they can just convince us to suffer in silence.
Do we have to create a new rule for all these? Crazy.
Screencasting uses various ports depending on the protocol, but common ports include TCP/UDP 1900 for discovery (SSDP/mDNS), TCP 80 (HTTP) and 443 (HTTPS) for initial communication, and a range of ports for data streaming like TCP 7000-7100 (AirPlay) or TCP 8008-8009 (Google Cast). Miracast uses TCP 5357 and 5358 for discovery and can use high-numbered UDP ports for the stream.
Hello SA. When I first noticed Screen Cast was no longer working for me, I thought if I researched and applied my findings I could get Screen Cast working again. Since I don’t currently use AirPlay or Google Cast, I only worried about Miracast. As you correctly mention, Miracast uses a few different ports for discovery, control, and a broad range of higher ports for the streaming of the display. I tried all of them in the user available inputs to the norton firewall. Most often the norton software would erase my inputs before I could finish my list of changes. A hamster wheel of norton induced malfunction.
I have since concluded that norton has so badly broken their firewall that there is no possible user input that will fix it. It really is Norton’s obligation and problem to fix.
I have also taken the position that norton should be making this a priority to fix. Obviously they haven’t. Since norton is not interested in correcting their malfunctioning firewall, I will soon be switching to a different software vendor who is more interested in satisfying a paying customer.
I think the trend of increasing dysfunction and customer dissatisfaction with norton/GenDigital will increase exponentially. Feels like the software version of the Boeing 737 MAX; A smoking hole waiting to happen.
Do you have the VLAN services running, in Windows services? I’m sure you do but otherwise asking none the less. Can you right mouse click on your desktop and in the menu, select Cast. Then see what devices appear that you can cast to and test? Just tested this on my daily duster, the GF went crazy over the show she was watching disappearing lol.
Hello SA. I’ve already tried this, although I left out port 1900 as that is only for Google Cast. Also left out ports for AirPlay, as I don’t use that either. Sticking to miracast ports in an effort to keep it simple. Anyway, my efforts to correct the firewall did not work for me. Like you, my W10 machine can screen cast with the firewall on.
Reading the almost nonexistent norton documentation for the current norton/Avast/Gen firewall circus, they seem to be saying a user rule goes to the bottom of the rule maze. I believe the firewall is blocking screen cast long before the iteration logic reached any user created rule. My W11 laptop can discover my TV and my ROKU with the firewall on, but I believe screen cast is failing at the control port step or at the higher port streaming step. Of course if I turn off the norton firewall Screen Cast works properly.
I am not aware of being on any VLAN, not even sure how that would apply. My private network seems pretty basic.
In reality this is truly a norton self inflicted dysfunction, and they have been botching their chance to fix it for more than a year. Screen Cast is a basic Windows function and I am at a loss to understand why over a year later the norton firewall is still a problem for paying customers.
Once again SA, I thank you for your efforts to find a user solution. At this point I honestly don’t think a user created firewall rule fix is possible, and so I have stepped off that hamster wheel. You are more knowledgeable than I in computer science and in norton details, so you may come to a different conclusion. In any case it is an interesting technical puzzle, but I am not in the mood to do any more of norton’s work for norton.
Thanks for the post back. The issue I see has to be coding, my reasoning is two different Windows versions have two different but similar issues. I haven’t dinged with Group Policy yet to see if that brings any relief so Norton should fix this issue. The VLAN service in Windows allow for isolation of virtual networks/ grouped devices to communicate one to another. I asked about it being enabled for the sake of ruling it out as something confusing the Norton firewall.
This thread has been escalated to watch for someone at Norton to intervene directly or via private message. I also will follow the thread as well.
Hello SA. Both my W10 machine and my W11 machine are the Home version of the OS. I bought both laptops new, and so they both have whatever the default Windows Home Group Policy is. For me at least, I don’t think Group Policy is the issue with Screen Cast because if it were then I doubt turning off the firewall would enable Screen Cast as it does.
Update: Norton has posted a new version release that directly addresses the issues here. Please let us know if your issues are corrected or not so we can get that information back to the teams.
Hello SA, well after a couple restarts and tests of Screen Cast it appears Screen Cast is working normally through the norton firewall. I’m glad to have it back, and I hope it is also working for other users as well.
Hello SA, I just noticed today that I can no longer cast laptop to TV. I tried everything I could find online, with he only option that worked was disconnecting 360 firewall. I have updated to the latest version 25.12.10659 but still the issue persists. This is very annoying as need bigger screen for work.
