Ok, I have a toughy...
I have a machine that needs to use bootp & NFS to connect to a remote computer to boot up its operating system (Montavista Linux 3.1). The working server setup we had before was a Redhat Linux 9 machine supplying the dhcp/bootp and nfs services. Now what I need to do is figure out how to make this work with Windows as a server.
My first attempt was with tftpd32 (tftpd32.jounin.net) and ProNFS v2.3. I quickly learned tftpd32 didn't support bootp and I could never get ProNFS to work correctly.
My second attempt was to use my Windows 2000 server's built in DHCP server and the now free Services for Unix v3.5 from Microsoft. I am now able to use bootp to get an IP address and connect to the NFS share. The computer first loads init and then freezes. I checked the permissions of the files on the NFS server and everything is set to 777, so it can't be a permissions problem.... I even did a network trace with Ethereal to see what's going on. I see it grab init and then it never makes another request.
Am I just asking for trouble here? Has anyone had any success with a Windows machine supplying an NFS share that a computer can actually boot from?
One last problem I have had... When I unpacked the tarball with the whole partition for this remote computer, some files were overwritten. They did not appear to be critical files though. Basically they were files of the same name but differing cases (like 'bigfile' and 'Bigfile'). Obviously Windows thinks these are one and the same as it doesn't allow the same file name with a different case. Is there any way to change this behavior?
One last thing - I can't put any money into buying additional software, so purchasing Omni-NFS or other NFS products is out of the question. I need open source/freeware apps. All I got was this computer running Windows 2000 Server.
Thanks in advance for any help you can offer!