Sebastian Lundh
Jul 1, 2011
visibility 8523
star star star star star
(4 votes)

Multicast configuration with multiple NIC’s.

nicToUseName gives the possibility to name the Network you want to send EPiServer remote events over.

UDP multicast is so esey, no need to add a section for each site in an enterprise configuration.  No need to setup special ports for listening and sending events. Just uncomment from standard configuration and it works.

Very often servers have double NIC's in use and when sending out udp multicast packets it will by standard choose the NIC with lowest index. So you startup Wireshark and don’t see any packets at all when listening on one of the NIC’s and filtering out UDP packets. So you listen on the other NIC and see that it’s actually trying sending out events over the wrong network.

Solution:
Control Panel\Network and Internet\Network Connections
Check the name of the connection.

Set this value as nicToUseName="nameofthenetwork"

Add this to web.config like:
<customBinding>
        <binding name="RemoteEventsBinding">
          <binaryMessageEncoding />
          <udpTransport multicast="True" nicToUseName="Local Area Connection"  />
        </binding>
</customBinding>

Now it will send and listen on this network.

Jul 01, 2011

Comments

error Please login to comment.
Latest blogs
Add more scheduled job settings from the Optimizely CMS 12 admin UI -- with OptiScheduledJob.ExtraParameters

  Optimizely (EPiServer) CMS 12 ships a great scheduled-jobs framework, but it has one frustrating gap: a job has nowhere to store its own...

Binh Nguyen Thi | Jun 25, 2026

Automated Search & Navigation to Graph Migration with Claude Code

A Claude Code plugin that scans your S&N codebase, applies Graph SDK transformations, and validates the result. Install once, run one command. CMS ...

Connor Fortin | Jun 24, 2026

Migrating from Find to Graph: Lessons Learned from a Real CMS 13 Project

While migrating a search solution from Optimizely Search & Navigation (Find) to Optimizely Graph in CMS 13, I encountered several issues that were...

Binh Nguyen Thi | Jun 24, 2026

Optimizely: Upgrade Opti-ID and .NET 10 in CMS 12

Many Optimizely customers are planning their roadmap around a future migration to Optimizely CMS 13. As a result, upgrades such as Opti ID adoption...

Madhu | Jun 23, 2026 |

Understanding Optimizely Graph: Caching, Webhooks & Avoiding Stale Content (Optimizely SaaS CMS)

📌 Scope: This post covers Optimizely CMS (SaaS) only — using the official @optimizely/cms-sdk and @optimizely/cms-cli packages with Next.js 15. If...

Kiran Patil | Jun 23, 2026 |

Optimizely Content APIs: the Setup the Docs Don't Walk You Through

CMS 13 is pushing things firmly in the direction of Optimizely Graph, but plenty of teams are still running on older CMS versions, or have good...

Andre | Jun 22, 2026