hi, On Tue, Oct 26, 2004 at 03:15:36PM -0700, Ashe Coutts wrote: > If I use ethereal on the Windows share cpu I see that the NetBootCpu indeed > issues a port 137 name query for the share cpu name. But when the share cpu > uses arp to find out the hardware address of the NetBootCpu no response > comes from the NetBootCpu. If I use > "asp -s NetBootCpu-Ip# NetBootCpu-HwAddr" > to force the windows share cpu to know the connection then the windows share > cpu does indeed respond to the query but the NetBootCpu still plays dumb and > no conversation ensues. > > What to do/try next??
hmm... this sounds like "NetBootCpu" is not able to receive packets, or is there a successfull dhcp(?) exchange taking place befor that? have you tried setting "PnP aware OS installed: no" in the bios? cu maurice ------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click _______________________________________________ unattended-info mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/unattended-info
