Yep, the CAS are real-ip running DHCP. There's no problem getting an IP
after they are imaged, it's strictly the ghostcast client boot trying to
get an address from the CAS that's failing. I'm going to check it out
this afternoon with a sniffer and see what's up.
Cal Frye wrote:
Don Nightingale wrote:
We're having an issue with the ghostcast clients not getting assigned
an IP from the CAMs.
Moving the target PCs to a non-CCA vlan with a stock linux dhcpd
server allows them to get an IP and start imaging.
Anyone else either see a similar issue or actually have it working?
To clarify, are your CAS's the regular DHCP servers (Real-IP Gateway)?
I've not had an issue with the DHCP services from the CAS. Do these
clients get addresses from the CAS /after/ they've been imaged?
Perhaps you've found a sensitivity in the NIC drivers for the
ghostcast setup?
--
Don Nightingale
Systems and Networks Manager
Wellesley College
781-283-3271
