ProLiant Servers (ML,DL,SL)
cancel
Showing results for 
Search instead for 
Did you mean: 

Multicast Problems

ChRiedl
Occasional Visitor

Multicast Problems

On a DL580 G5 server with Windows Server 2003 64bit R2 Enterprise Edition with SP2 (6 Network interfaces, NC373i + NC364T) we have Problems with multicast.
Our application joins interface 1 to multicast group A and interface 2 to group B.
We do not receive multicast data and "netsh int ip show joins" shows that both multicast groups A and B are joined with interface 2 only.
6 REPLIES
KarloChacon
Honored Contributor

Re: Multicast Problems

hi

are you using NIC teaming?
multicast in all NIC cards? PCI and embedded?

latest driver, Network configuration utility and firmware for NICs?

can you run this command

hpnetsvy > nic_survey.txt

bye

Didn't your momma teach you to say thanks!
ChRiedl
Occasional Visitor

Re: Multicast Problems

Teaming is off and I also tried to disable RSS, TCP chimney and TCP offline engine without any success.

I disabled the PCI interface and tried only the 2 NC373i interfaces.

192.168.110.2 Multicast group 224.168.110.1
192.168.120.2 Multicast group 224.168.120.1

and "netsh int ip show joins" shows me

192.168.120.2 224.168.110.1
192.168.120.2 224.168.120.1

and I did not receive any multicast packets.

The same testapp on a 32 bit Windows 2003 DL360 behaves as expected.

I attached nic_survey.
ChRiedl
Occasional Visitor

Re: Multicast Problems

Thank you Karlo,

I will try it.
ChRiedl
Occasional Visitor

Re: Multicast Problems

Karlo,

updating the NIC driver did not solve our problem. But I have some new experience.

It seems that when we join a muticast group, the specified interface is not used but some default interface associated with the computers name (by WINS resolution).

And, compared to the 32 bit servers where our testapp is running fine, the
netsh int ip show joins takes much, much longer (15 secs versus less than 1 second)
ChRiedl
Occasional Visitor

Re: Multicast Problems

I found a solution for my problem, but I do not understand why this workarround was not necessary on my 32 bit systems.

Per default route table contains two lines for multicast and my 2 enabled interfaces.

Dest Mask Gateway
224.0.0.0 240.0.0.0 192.168.110.1
224.0.0.0 240.0.0.0 192.168.120.1

My app joins interfaces to the mcast groups
225.168.110.1 192.168.110.1
225.168.120.1 192.168.120.1

For 32 bit system this is sufficent. The 64 bit system joined both mcast groups on the 120.0 network. Ann I did not receive any multicast packets.

Now i added 2 more static routes
Dest Mask Gateway
225.168.110.0 255.255.255.0 192.168.110.1
225.168.120.0 255.255.255.0 192.168.120.1

Now the application works fine. On all the servers there is no routing service enabled.

Why do I need the additional routes on the 64 bit server ?