What to do if Firewall is blocking Multicast on Windows 10

At times, the Multicast streaming may not work if you have your Firewall enabled. Users have reported that they are unable to use the Multicast stream on Windows 10 due to their Firewall blocking Multicast.

In this article, we take a look at the best fixes to resolve Multicast firewall blocking issue in Windows computer.

What to do if Windows 10 multicast isn’t working?

1. Check for VM Network Adapter

1. If you or your client has Virtual Machine installed, it will also install the Host-Only network for the VM. This network adapter can create issues with Multicast streaming and Firewall.
2. Try to disable the Network adapter from the control panel and check if that resolves the error. Here is how to do it.
3. Press Windows Key + R to open Run.
4. Type control and press OK to open the Control Panel.
5. In the Control Panel, go to Network and Internet > Network and Sharing Center.
6. From the left pane click on Change Adapter Settings.
   
   
7. Right-click on the VM installed Network adapter and select Disable.
8. Now start the stream and you should be able to start Multicast streaming.
9. From the Control Panel, right-click on VM network Adapter again and select Enable.
10. Right-click on the Network Adapter again and select Properties.
11. Double-click on “Internet Protocol Version 4 (TCP/IPv4)”.
    
    
12. Click the Advanced button at the bottom of the window.
    
13. Uncheck “Automatic Metric” and set the value to 0 for ethernet or wireless if required and 1 for VM.

2. Add Application to the Windows Firewall Exception List

1. If you haven’t already, you can add an application on the Windows Firewall exception list and allow it to receive all incoming traffic from that application. This is the easiest but not the safest method to resolve this issue. Here is how to do it.
2. Press Windows Key + R to open Run.
3. Type firewall.cpl and press OK to open Windows Defender Firewall window.
4. From the left pane click on Advanced Settings.
5. Click on Inbound Rules options.
6. On the left pane click on New rule.
   
   
7. Under “Rule Type” select the option “Program“ and click Next.
8. Select the option “This Program path”.
   
   
9. Now browse the program that you want to add to the exception list. Program‘s .exe file is located in C:\program Files (x86)\Program Name
10. Select the “Allow the connection” option.
    
11. Click Next and leave all the options as it is. Click Next again.
12. Add a name for this rule so that you can identify it easily and click Finish.
13. Now try to start the stream and check if you are able to connect without any issues.

3. Other Workarounds to Try

1. Specifically, allow incoming traffic from the IP addresses of all the server running the Streaming. While this can be a time-consuming task, it is safer than adding the program to the exception list.
2. You can also configure the Windows Firewall to allow UDP traffic only from the specified ports. To do this you need to change the Windows Media Player settings or server configuration.
3. Lastly, you can enable rollover to a TCP based protocol on all Windows Media Server publishing points that streams. This is the most secure but resource hungry method.

RELATED STORIES YOU MAY LIKE:

The VideoLAN Forums

Discussion and support for VLC media player and friends

Recent Windows 10 update killed VLC multicast reception??

Recent Windows 10 update killed VLC multicast reception??

Post by mccreigh » 30 Sep 2018 16:26

A month ago all my Ethernet-connected VLC clients could happily receive
the IP multicast TV provided by my Internet Service Provider (init7.ch)
over my 1Gb/s / 1Gb/s fiber-optic Internet link. On that link, the
IPv4 Multicast address 239.77.0.77 is our main Swiss TV station, SRF1.

Now my Windows clients no longer can receive any IP multicast station
but my Linux clients still can and
so can my iOS clients when hardwired to my Ethernet. (Multicast TV
over WiFi is a well-documented tale of woe.)
All my machines are attached to the same switched 1Gb/sec
Ethernet internal LAN. Neither Windows VLC 3.0.3 nor 3.0.4 still works, and neither the
32-bit not the 64-bit binary works. All my Windows machines are running the
64-bit version of Windows 10 Home, patched to v10.0.17134 Build 17134.

If, however, I launch udpxy on a LAN-connected Linux server at 192.150.23.4
(used as a private address), and then present the URL

to Windows VLC as a network address, the TV channel plays perfectly.

When I present the URL udp://@239.77.0.77:5000 to Windows VLC as a network
address while sniffing that machine’s Ethernet interface using Wireshark
on the same machine, I see a correct
IGMPv2 Membership report, followed some 250msec later by a steady blizzard
of about 150 1358-byte UDP MPEG TS packets per second from 77.109.129.16
to 239.77.0.77. Nonetheless VLC behaves as if it’s waiting for content;
the orange bar sweeps back and forth.

If I had to make one guess about what’s happening, I would guess that
one of the September 2018 Windows 10 update patches changed something about receiving
IP multicast packets, and that the VLC team was not expecting the change.
In September one of my Windows machines installed the OS updates
KB4346783, KB4457128, KB4456655,
KB4457128, KB4100347, KB4464128, as well as the Adobe Flash Player
security update KB4457146, and the usual Windows Defender stuff.

Further insight, anyone?

Many thanks,
Ed McCreight

******
VLC debug log during failed connection attempt

Брендмауэр не пропускает мультикаст

На ПК установлено программное обеспечение для просмотра IPTV. Точнее DRM и CAS идут отдельной программой, просмотр ТВ происходт через браузер (IE9). Если брендмауэр включен — не получается просмотреть ни одного канала. Если запустить с выключенной защитой — всё работает корректно. Не подскажете, где в настройках брендмауэра можно разрешить мультикаст потоки

Здравствуйте. Для этого Вам нужно сделать следующее :

нажать Пуск —> Выполнить (Win + R), в поле ввода вписать:

netsh.exe firewall add allowedprogram program = “C:\Program Files\IP-TV Player\IpTvPlayer.exe” name = IpTvPlayer mode = ENABLE

“C:\Program Files\IP-TV Player\IpTvPlayer.exe” — путь, куда установлен IP-TV Player, по-умолчанию он именно такой. Это приводит к тому, что в брандмауэре автоматически прописывается правило, разрешающее сетевую активность плееру IP-TV.

Если это не поможет, попробуйте создать правило вручную в Дополнительных параметрах Брэндмауэра Windows — Правила для входящих подключений — новое правило — Настраиваимые — Путь прогрммы (укажите путь к IPTV плееру) — тип протокола IGMP — далее — Любые IP адреса — далее Разрешить подключение — далее Выберите профиль — дайте имя правилу — готово.

То же самое для исходящих подключений.

Был ли этот ответ полезным?

К сожалению, это не помогло.

Отлично! Благодарим за отзыв.

Насколько Вы удовлетворены этим ответом?

Благодарим за отзыв, он поможет улучшить наш сайт.

Windows 10 multicast problem

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Answered by:

Question

• Windows 10 x64 Version 1607
• NIC Intel 520 T1 10GigE (Jumbo Frames enabled)
• Switch Netgear s3300 28x poe+

the Intel 520 is the only NIC in the System.

2 Multicast Sender (239.255.15.49, 239.255.14.50) (each sends at 1Gbit/s)

with 2 multicast Receiver applications listening each to asender or 2×2 multicast Receiver applications (2 listen to the same multicast sender)

the 5th application will have Problems receiving udp packets (wireshark Shows that packets do not arrive, the Switch Shows no packet drop in statistics)

Читайте также:  Как установить чистую mac os catalina

if i use 4 applications each listening to one unicast Sender, the 5th application has no Problems even if the traffic is doubled.

Does multicast imply that Windows will be more likely to drop udp packets?

Answers

i think i can explain it now:

the Switch has 10GigE upstream port,

the devices are connected to 1GigE ports.

with multicasts the packets are copied to all ports, so they get traffic at about 2GigE Speeds and this does not work 🙂

All replies

• Windows 10 x64 Version 1607
• NIC Intel 520 T1 10GigE (Jumbo Frames enabled)
• Switch Netgear s3300 28x poe+

the Intel 520 is the only NIC in the System.

2 Multicast Sender (239.255.15.49, 239.255.14.50) (each sends at 1Gbit/s)

with 2 multicast Receiver applications listening each to asender or 2×2 multicast Receiver applications (2 listen to the same multicast sender)

the 5th application will have Problems receiving udp packets (wireshark Shows that packets do not arrive, the Switch Shows no packet drop in statistics)

if i use 4 applications each listening to one unicast Sender, the 5th application has no Problems even if the traffic is doubled.

Does multicast imply that Windows will be more likely to drop udp packets?

Mutlicast traffic and windows 10

Just wanted to check if anyone else has had any trouble with Windows 10 and disappearing multicast traffic.

We have a LOT of iptv traffic on our LAN but we have now had two users not being able to see SAP announcements or IGMP traffic.

This happened mid morning after a windows update and reboot (only office updates) but one of the users has said that Symantec had been complaining about a reboot after an update for a few days (*sigh*).

The strange thing is that the users are bumbling along watching streams etc. and then the windows 10 boxes just suddenly stop (according to the users, one of which is a software engineer working on multicast streaming and the other is QA so should know what they are doing).

VLC doesn’t see SAP announcements and wireshark isn’t seeing it either although I have managed to capture aroung 12 IGMP packets over a 5 minute period.

Steps taken so far.

First things first, disabled the Symantec endpoint firewall, still nothing.

I then run windows update because I can see that there is a failed update to windows defender.

Updated and reboot in to a different user profile.

They can see (ping, traceroute etc the source of the traffic)

They are in the correct VLAN, can see the servers etc but none of the multicast traffic.

Any suggestions before I am forced to go to Symantec for support?