Interestingly, As soon as I switched the client to bootp, it worked fine with Windows2000 for both bootp and tftp. As to your "(why would we??)" question - simple. Many MANY corporate environments are running NT and going to Win2000. Many others are currently running Netware. The lure of a global directory for a company running NT makes Win2000 a holy grail. For better or for worse, all these wonderful projects like Etherboot and Netboot should be integrated and tested with Win2000 as well as Linux. If you only make it work with Linux, it will remain an academic curiosity. Don't get me wrong - I LOVE Linux - I've been using it since 1994. But I can't ignore M$. I have a client who has a cluster of HP9000s in Switzerland, a worldwide WAN, and a Windows2000 Active Directory that spans the globe. Now that I have etherboot working with Windows 2000 and bootp/tftp, I can propose to them several hundred diskless Linux terminals that provide access to the HP9000 cluster. They already use Windows2000 DHCP and TFTP for RIS support for their Windows2000 Workstations, so adding Linux/Etherboot support into that existing setup will be a snap! And THAT is why this netboot stuff is so much fun! ----- Original Message ----- From: "Kent Snook" <firstname.lastname@example.org> To: <email@example.com> Cc: <firstname.lastname@example.org> Sent: Tuesday, January 16, 2001 6:53 PM Subject: Re: [Etherboot-users] Re: A Request - Next Server 0.0.0.0 > "Eric W. Biederman" wrote: > > > > "Dave Stubbs" <email@example.com> writes: > > > > > I can't seem to get Windows NT4 DHCP server or Windows2000 DHCP server or > > > Netware 4.11 DHCP server or Netware 5 DHCP server to do this. > > > > > > Dave... > > See http://support.microsoft.com/support/kb/articles/Q142/3/73.ASP. > It seems that NT versions before 2000 did not support tftp without > 3rd party software. There are instructions on how to enable bootp > on this page. > > While we have not used NT as a bootp server ( why would we?? ) > we have done testing of dhcp on NT vs Linux/Unix > and response time wise, NT came out in a distant last place. > > Kent > > > > Very weird (if true). Because the siaddr field dates back to bootp. > > It has always been there. > > > > Have you used tcpdump or the equivalent to look at the DHCP packets > > being sent, and confirm that is what's wrong? > > > > Of course the DHCP servers may be specialized so they can only hand > > out IP addresses, and can't support network booting at all. > > > > Eric > > > > _______________________________________________ > > Etherboot-users mailing list > > Etherbootfirstname.lastname@example.org > > http://lists.sourceforge.net/lists/listinfo/etherboot-users > > -- > > Kent Snook > email - email@example.com > > Maryann's Law: > You can always find what you're not looking for. > =========================================================================== This Mail was sent to netboot mailing list by: "Dave Stubbs" <firstname.lastname@example.org> To get help about this list, send a mail with 'help' as the only string in it's body to email@example.com. If you have problems with this list, send a mail to firstname.lastname@example.org.
For requests or suggestions regarding this mailing list archive please write to email@example.com.