Bit of background first: GSS 2.5.1 running on Windows Server 2008 R2, has worked for us for many years without issue to image a couple computer labs (roughly 200 computers total).
Our network team has just moved us to a new network architecture, and now the 224.x.x.x range is no longer usable for multicast across the network (in our case between vlans in different buildings, all connected through a gbit network). They advised using 239.x.x.x instead. I had a look and sure enough in the Ghostcast server there is an option to change the multicast range so I've changed it from 224.77.2.0 to 239.77.2.0 (and the respective end range). Hit OK, rebooted the entire server to be sure. Start a new ghostcast session and while computers can connect to the ghostcast server the actual multicast distribution doesn't start (the clients sit there waiting).
Opened up a command prompt to check, and sure enough netsh interface ip show joins shows only a session joined on 224.77.0.0, despite the option being set to 239.77.2.0. If I stop the session then that join disapears, so I know its coming from Ghostcast.
Changing it back to 224.77.2.0 and it still shows the same when I restart the session. Or changing it to anything else.
I also tried calling Ghostsrv.exe from the command line with the appropriate switches and still no luck.
GhostSrv.exe -M239.77.2.0-239.77.255.255 "c:\RESTORE.gho" -N2 -TTL32 -UU -Fc:\ghost.log -LA ghostsess
The log file though does show that its using 239.77.2.0
Two questions I have for anyone who may know before I endure a possibly long phone call to tech support:
1. Does this option work? Or is it known to not actually affect anything?
2. Has anyone else had success in using a different range than 224.x.x.x? I've searched but not found much useful in past discussions