Interesting!! Thanks for the post back, I have not had the free time to dive that deep into the issue unfortunately. Please keep the thread updated.
SA
Well, the results of changing the âPPIâ default rule to smart mode, reboot and retest are in. Still canât cast from my W11 laptop my TV.
I still can cast from my W11 laptop to my W10 laptop screen. I can also cast from my W10 laptop to my W11 laptop screen.
So I havenât fixed my issue shared by many, but havenât made anything worse. Back to my Franken-norton research roulette.
Thank you SA, sometimes a different viewpoint finds success and this was worth trying.
P
1 Like
More curious behavior from the W11 optional âWireless Displayâ App (âConnectâ in W10 start list). On my W11 laptop when I use my W11 screen as a display to receive a screen cast from my W10 laptop I get Intrusion Signatures disabled and Remote Access disabled in my Security History. When I disconnect the cast both are enabled again.
Same when I cast the W11 laptop screen to the W10 laptop screen.
Raises the question of what did norton forget to disable to prevent the W11 laptop from screen cast to my smart TV? Now to screen cast from my W11 laptop to my TV I have to disable the norton firewall. Before recent updates my W11 would screen cast without issue.
An update since norton has not solved this problem. [I have recently been updated 25.9.10453 (build 25.9.10453.954)]
After unsuccessfully attempting to screen cast to my smart TV, I attempted to modify the norton Program Control entry for âCasting protocol connection listenerâ. norton would absolutely refuse to save my multiple attempted edits, and the time it did accept it, a moment later the program without my input changed to âCustomâ and erased my inputs. Mumbled profanity. norton will not even allow a user to try and help themself while the âKremlinâ sits on their hands. As I watch the norton Program Control it just rolls through all the rules systematically alternating various rules from âAllowâ to âCustomâ and back to âAllowâ, negating any user input and possibly even negating settings for rules that formerly had allowed various programs to function properly. Like screen cast used to work on my W11 laptop before recent updates.
Have you restarted the device to make the changes global? Just a thought.
SA
Was a good thought; I get consumed by this at times. So after a restart screen cast does not work. Program Control firewall settings page seems more stable after the restart.
P
When I again tried to edit the norton Program Control entry for âCasting protocol connection listenerâ, norton would absolutely refuse to save my multiple attempted edits and a moment later the program without my input changed to âCustomâ and erased my inputs. Doesnât seem like a user can fix norton even if they might know how.
SA, saw your new rule suggestion on the citrix thread, thought I would try that. Unfortunately norton is blocking this at well. As soon as I hit Save the ports disappear, and then the Access button rolls to custom, and when Allow is selected the new rule has entirely disappeared. norton is not allowing me any changes.
I found AI generated info for review. Yes indeed this is becoming a farce with the firewall. MAYBE something in the below info will help.
AI Overview
Casting protocol listener remote ports vary by the specific casting technology, but generally include the default Remote Desktop Protocol (RDP) port TCP 3389, and for casting protocols like Google Cast/Chromecast and Miracast, ports such as UDP 1900 for discovery, and TCP 8008-8009 or a range of UDP ports for the actual data transmission. To find the specific ports used by a casting device or software, youâll need to check its documentation or firewall configuration settings.
Default Remote Desktop Protocol (RDP)
- TCP 3389: This is the standard, default port used by the Remote Desktop Protocol (RDP) for remote desktop connections.
Chrome and Google Cast
Used for DIAL protocol discovery, which allows devices like Chromecast to be found on the network.
Required for the Cast V2 protocol to establish connections for casting and control.
Miracast
and TCP 5358: These are the default ports for Miracastâs WS-Discovery and device discovery processes.
Miracast may use a range of UDP ports for the data stream itself, and you may need to configure your firewall to allow this traffic.
- UDP ports 1024-65535: The Windows operating system uses a broad range of UDP ports for its built-in screen casting features.
How to Check and Configure Ports
- Firewall Settings:
Check your software firewall (e.g., Windows Defender) and any hardware firewall for rules related to the casting protocol in use.
- Registry Editor:
For RDP, you can find the current port by navigating to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcpin the Registry Editor.
- PowerShell:
To check the RDP port, use the command
Get-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp' -name 'PortNumber'.
- Manufacturer Documentation:
For devices or applications that use their own casting protocols, always refer to the manufacturerâs documentation or help files for the correct port information.
SA
Hello SA, and thanks for your AI Overview posting. Iâm new to this AI search, but I have seen cases where it scours an incorrect webpage and then passes that along as part of itâs product. I think you know that better than me, just reflecting on it after visiting a couple websites today with clearly incorrect info. Today Iâve been trying to stick with the previously posted link to the Microsoft technical papers on Miracast, or the technical overview from the certifying body, Wi-Fi Alliance; link follows.
1 Like
A continuation of my previous postâŚ
I came across a table that I have been working on verifying. What I like about it is it presents data in a format that is easier for me to assimilate, but it is from a page that doesnât have any Citations. Iâm going to try and verify the parts that pertain to Miracast, as that is what I believe Windows 11 (and 10) are using (and norton is abusing). Not going to worry about Air Play or Google Cast, but the table illustrates how AI can hoover up data that doesnât really pertain to the input search question.
Update. Microsoft paper on Miracast states Windows gives priority to Miracast over Infrastructure instead of Miracast over Wi-Fi Direct. Well, I wondered about that in my situation. So, I powered down my router to see if I could establish Miracast over Wi-Fi Direct. The result was norton firewall blocked cast to TV over Wi-Fi Direct. I then turned off the norton firewall, and my W11 laptop successfully cast my screen to my TV over Wi-Fi Direct. (Ran freeware âWireless Network Watcherâ to get the two ipâs)
Powered my router back on, turned off my norton firewall, and my W11 laptop successfully cast my screen to my TV via Miracast over Infrastructure. (Ran freeware âWireless Network Watcherâ again to get the ipâs)
[FWIW I tried all of the previous on my roku attached to my TV, and with norton firewall turned off my laptop was able to successfully screen cast to my roku which displayed on my TV.]
My conclusions are: First, W11 (and W10) gives priority to âMiracast over Infrastructureâ (router LAN) instead of Miracast over Wi-Fi Direct. Second, norton firewall is the problem with screen cast from my W11 laptop.
Late breaking additional observation: Just restarted my computer, and before the norton icon had appeared (system tray icons; lower right taskbar) I hit Windows+K keys to see my TV and roku listed as available wireless displays. After the norton icon was displayed I again hit Windows+K keys, and no displays were listed. Well this is new as of today. Mumbled profanity. Checked, and norton live update had run recently today. Further conclusion: norton is only getting worse, and is now blocking âDiscoveryâ which happens on Wi-Fi Direct. Turning off the firewall did not allow my TV or roku to be discovered. (Ran freeware âWireless Network Watcherâ again to get the ipâs, TV and roku ipâs were there)
Thanks for the detailed insight indeed. Havenât had the free time to dive head long into this recently, for that I apologize.
Wondering, and please refresh me if you have already looked at this section of settings. Does changing any of the RED public settings to green and a reboot change anything? In the other thread where this is discussed I believe you have but with the latest release version? Blocking network discovery is just way over the top.
Hello SA, I have tried only one thing in Public Network Exceptions, and that was to Allow Multicast Traffic on Public Networks.
(Not that I think Public Multicast should matter in my situation.) (You know I sometimes wonder if norton has a hidden setting that identifies my private network a public. On one of the major updates norton had changed many networks from Private to Public.)
norton has lost control of their own program, and canât seem to repair their self inflicted malfunction, or even care about it.
SA, just reread your latest post, and I wanted to clarify something. norton has not blocked network discovery. What norton has blocked is Available Display discovery (device discovery) that is searched when the user presses Windows+K keys together.
From the Microsoft MS-MICE paper previously linked:
âA Miracast over Infrastructure session consists of three phases: device discovery, host name
resolution, and projection.â [W11 (and 10) are said to prioritize âMiracast over Infrastructureâ.] pg24
âThe Miracast over Infrastructure session starts with peer to peer (P2P) device discoveryâŚâ
âGlossary:
peer to peer (P2P): An Internet-based networking option in which two or more computers
connect directly to each other to communicate and share files without use of a central server.â
Also, the Wi-Fi Alliance Miracast document I previously linked has this to say about Device Discovery (pg6):
âSource and display devices discover each other prior to connection setup. The
Device discovery mechanism is defined in the Wi-Fi Peer-to-Peer Specification or
through existing AP connections as defined in the Wi-Fi Display Technical
Specification 2.0. Device discovery over an existing infrastructure connection utilizes
mDNS/DNS-SD.â
SA, just wanted to add that Iâm no expert on any of this. I lay some of the quotes out to make sure Iâm not making any false assumptions. If you see that I have something wrong please let me know.
P
1 Like
OK, a visual of the manner in which norton has broken W11 Miracast device discovery.
W11 Settings â Bluetooth & Devices â Devices â scroll to Wireless displays & docks.
In the image below you can see my LG smart TV, my Roku, and my two other laptops,
all 4 devices I have successfully screen cast to prior to a 2025 norton version update.
When I press the Windows key âď + Kâ combination right after startup and before norton finishes loading I can see my both my LG smart TV and my Roku listed as as Available displays on the Cast fly-out. After norton finishes loading when I press the Windows key âď + Kâ combination we can see that norton has inhibited wireless display discovery in the image below.
Got my device discovery back. Went to Intel support and downloaded the latest driver for my network adapter. Now I can again select my TV or Roku, but still cannot screen cast to them unless I turn off norton firewall.
norton tells us how important and protective their firewall is. Doesnât do much good if their customer needs to turn off the firewall to use the computer norton is getting paid$ to protect. Shameless.
1 Like