Web Client 4 - Multicasting and RTD

[JDup]

Just wondering if anyone has suffered through the same issue we are experiencing.

We have three sites that register, listen and recieve multicast traffic for 3 reports - Agent, Application and Skillset (Moving window and Interval to date). In each of the sites the Skillset report data populates the Webclient but will not for the any of the other reports*. *In one site it populates another report - Application. Very strange.

- in a past config the SWCS was local to one site and all the reports populated for this site so I know that the workstation (IE wise) can display the data
- I can bring up all the reports from the local host and if I place a machine on the same VLAN as the SWCS.
- No ports are blocked in the WAN or LAN.
- Receiving machines are XP, IE 6 with the latest updates.
- I have packet sniffed and it looks like the machine is getting the packets but I have no way of telling if the actual data is good

My next step is to use the trace utilities on the SWCS CD and load them on a workstation the normally recieves the report data. Will these show me if the incoming data is good though?

 

[sandyml]

Sounds like you moved the Web Client, is that right? What IP changes have you made to all these servers? The SWC, particularly version 4, is picky about that. Also, I have run into issues among different software versions of routers for the WAN. IGMP will be needed for the LAN, but you probably need PIM enabled for the WAN routers.

 

[JDup]

Only the SWCS IP was changed. We have verified all the address, naming etc. The SCCS' can communicate with the SWCS without problem. The upstream data is getting there.

Our network is relatively simple with only 1 or 2 hops at the most (LAN extension). All the routers have been configured identically and the necessary protocols are in place.

 

[teleshooter]

I have had this same issue, multicast can be a real pain in the neck if your network is large and those real time reports are rather large and time sensitive, troubleshooting can be a chore as well.

After futile efforts to resolve, we installed MS terminal server local to the real-time web server, hence we only have multicast running on that local segment and have had no further issues. The remote supervisors log into terminal services rather than the web client for their stats...

 

[JDup]

Thanks teleshooter. I was thinking of doing the same thing. Good to know it's a decent option.

Another option is to upgrade the SWCS of take advantage of unicast. Unfortunately the server has not been scaled to support unicast connections.