tosca925 Posted April 7, 2009 Posted April 7, 2009 We had a old DC that did DNS, DHCP and RIS. We have installed a new DC and put DHCP and DNS on that but left RIS onthe old DC which has now been demoted after having the FSMO roles moved. Simce we have done this RIS does no longer get a DHCP lease when we do a netork boot. DHCP is working fine on th new server has the workstations and laptops onthe network all log on fine and if we do a ipconfig /all it shows the correct detaisl for DNS and DHCP. We have no idea why RIS does not now pick up a DHCP lease to boot. Does anyone ahve any ideas?
Michael Posted April 7, 2009 Posted April 7, 2009 Is the old original server now just a member server or is it still a domain controller? If a domain controller, what roles is it running? The old server most likely has a static IP configuration, so the Primary and Secondary (optional) DNS entries need to be updated to point to the new DC.
DMcCoy Posted April 7, 2009 Posted April 7, 2009 We had a old DC that did DNS, DHCP and RIS. We have installed a new DC and put DHCP and DNS on that but left RIS onthe old DC which has now been demoted after having the FSMO roles moved. Simce we have done this RIS does no longer get a DHCP lease when we do a netork boot. DHCP is working fine on th new server has the workstations and laptops onthe network all log on fine and if we do a ipconfig /all it shows the correct detaisl for DNS and DHCP. We have no idea why RIS does not now pick up a DHCP lease to boot. Does anyone ahve any ideas? You need to create the options in DHCP to point the machines at the correct server, this was not done at the time as RIS was on the same server as DHCP. You may be able to get the RIS setup to do this for you by changing it's settings.
tosca925 Posted April 7, 2009 Author Posted April 7, 2009 You need to create the options in DHCP to point the machines at the correct server, this was not done at the time as RIS was on the same server as DHCP. You may be able to get the RIS setup to do this for you by changing it's settings. Which DHCP option needs configuring? How do we rerun the RIS setup? THe server which has been demoted is going to be flattedn and reconfiigured, we intend to put RIS back on it but until we get chance to do this then we need to get RIS working.
DMcCoy Posted April 8, 2009 Posted April 8, 2009 Which DHCP option needs configuring? How do we rerun the RIS setup? THe server which has been demoted is going to be flattedn and reconfiigured, we intend to put RIS back on it but until we get chance to do this then we need to get RIS working. I think it's options 66 and 67
OverWorked Posted April 10, 2009 Posted April 10, 2009 (edited) I don't think the DHCP options 66 and 67 need configuring. I'm sure I haven't. It sounds to me that the RIS server is no longer authorised as a DHCP server, since you demoted it from a DC (and removed the DHCP role at the same time?). It has to be authorised as a DHCP server, even if it isn't one. Authorize a DHCP server in Active Directory Check your RIS server is in the list, along with your new DHCP server. Also see this and this. MS advise against setting options 66 & 67. I think I had the same problem years ago, and set the options to fix it, then found the real reason for the problem was that it wasn't an authorised DHCP server. Edited April 10, 2009 by OverWorked added more
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now