Unable to begin session using Directed Broadcast
I'm in charge of imaging client computers that are shipped out to support various events. Hard drive images range from 45-500GB, and we often do a couple dozen per week. This is a small company and I am the self-taught "IT guy," so I'm pretty much not an expert on anything.
I had been suffering along using multicast, sometimes taking 3 days to do a batch of 18 machines (what we consider a full set), until I found that using directed broadcast instead would allow me to get the same batch done in a few hours! Hooray!
Well, that thrill didn't last long, because last week the seven-year-old Server 2003 machine that had been hosting our Ghostcast died. I have put up a new machine in its place, however this new one is running Windows 7 Ultimate. (We have hopes of resurrecting the old server, which is one reason I installed a different OS.) Hard drive speeds are excellent, compared to the SCSI drives on the previous machine, network appears to work well, and in general I'm happy with the new setup.
The problem: I'm not able to use directed broadcast on this new system. Unicast and multicast work, however neither of these is adequate for pushing out the massive images we use. When I set Ghostcast Server to force directed broadcast, the clients connect and show "Waiting for Ghostcast session to start." On the server, I see "Ghostcast session in progress," but no data goes out. Eventually the clients time out.
Here is our equipment:
- Switch, HP ProCurve 1800-24G (J9028B, firmware is PB.03.04) - Does not support multicast/IGMP, static IP 10.10.1.1.
- Server, SuperMicro 6026T-NTR+ running Win7 Ultimate SP1 with...
- ...Ghostcast Server 184.108.40.2063
- ...DHCP server (Tftpd64 4.0)
- ...dual NICs, one answers to 10.10.1.2 and runs the Ghost network; one answers to 192.168.2.56 on our LAN. I've set up this multi-home rig so that Ghost traffic doesn't flood our network but I can control the system from my desk.
- Client machines are various hardware, but all run Ghost32 in either WinPE 3.0 or 4.0.
I have attached a Wireshark capture of a typical attempt. In this capture, I hit "Accept Clients" and then cause two machines to connect to the session named "testsession". The server shows the clients connected, but does not start the session. If there is any more information I need to provide, please let me know! I'll be back in the office January 2 and I'm eager to get this solved!
Thank you very much for your time!