RIS server 1

[CCNEH]

Basically.

I've set up a RIS server for use within our organisation.

When testing it on a test subnet, I had dhcp setup on the RIS server and the dhcp responded to a clients request for an IP.

Now, I tried the RIS server on our live netowrk and DHCP is issued by a netware 5.1 server and the client couldn't get an IP when booting from the floppy disk, it came back with an error saying it could not find an available DHCP server.

BUT, The netware dhcp server works for everything else.

Any idea's?

 

[CCNEH]

 

[Lightspeed1]

CCNEH,
Couple of things come to mind, are the network cards PXE compatible? What is the platform on your client PC's? W2K? W98?
Could you set up an identical address pool on the W2K server box and have it take over the DHCP duties for your clients? I don't know a ton about netware so I don't know if you can set up a lease expiration time that you would be able to coordinate with having the W2K DHCP server authorized and take over the DHCP duties.
Sorry, not overly helpful but maybe it will stimulate some dialogue from some more knowledgeable folks eager to prove me wrong
Some more info on your network config and specifics on what you are trying to accomplish might help generate some more troubleshooting steps also.
Regards,
Lightspeed1

 

[spazmahoney]

I had similar problems with having DHCP running on a different win 2k server than the RIS server. I setup DHCP on the RIS server and activated it in Authorized it in Active Directory. Worked like a charm. Another suggestion is to customize the ristndrd.sif and riprep.sif files with your desired config settings for unattended automated installation. The Resource kit and several books all say to create an unattended installation file and associate it....This didn't work. Instead, I created the unattended install file and copied and pasted to the default files-ristndrd.sif and riprep.sif. Fully Automated Success!
Spaz, MCSE

 

[scanjam]

Im not to ofay with NETWARE however on our RIS / DHCP servers we have them separated completely.

DHCP on the 1st server has 2 new options added.
Boot Server Host Name (066) = RISSERVER Host Name
and Bootfile Name (067) = startrom.com


On the RIS Server in the RIS directory (whatever you have already specified it to be) i have the \\server2\d$\RIS\OSChooser\i386 contents copied directly to the d$\RIS folder (startrom.com, startrom.n12 and ntldr)
DHCP is installed on the RIS server and authorised in the AD, however the DHCP service is actually totally disabled.

Can you specify the 66 and 67 options in netware??
Hope this helps in someway.

James

 

[LeoZipper]

Scanjam,
I have been having trouble with the PXE boot from the NIC returning "PXE-E53: No boot filename". I have been able to boot fine with the RIS boot floppy. But some machines, usually those with the NIC integrated, the boot floppy does not have a compatible driver.
By coppying the files referenced in your reply, it worked. Many thanks.
I have found that the DHCP Option 66 can be set to "OSChooser\i386\startrom.com" (the default RIS installation from the RIS share) and the files then do not need to be copied.
Again many thanks; you have my vote for helpful post.

 

[scanjam]

Leozipper,

Appreciate your feedback as well, thats better id prefer not to change the default, it was actually setup that way when i was sorting out the argon boot manager and the PXE menu editor, and i had a similar message about no boot file found.

Thanks for The feedback,
SCANJAM