• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Windows 2000 Server and Ghost Multicasting

N

Nucleus111

Golden Member
I have a Windows 2000 Server with a multicast scope setup. I'm also running Ghost 8.0 Corporate. When clients connect from a boot disk they show an IP from the class B scope. If I understand correctly, this is how IP works with multicasting...you need a "real" IP first. How do I know if everything is working correctly? How does Ghost use an IP out of the multicast scope? How do the clients all use the same multicast IP?

Yup...I'm lost!
Thanks for the help.
 
I'm not sure I understand why you're using a multicast scope. AFAIK ghost clients will just pickup and use regular dhcp leases (as you indicated they are recieving class B addresses, this is the behavior I would expect); I cant say I've seen anyone try and use ghost with a multicast scope.

The way I do ghost multicasting:
boot the machines and let them pick up "ordinary" addresses
deliver using ghostsvr.exe's ghostcast
no need for special ip scopes for these clients.

Now that I think of it I cant say I've ever worked on or seen multicast scopes used in production. Generally what I'll see people do is to setup seperate VLANs for ghosting, just to seperate the clients out from the regular networks while imaging.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top