I work within a company which has two OUs - one for School Administrators the other for Pupil Curriculum usage. We have had to move the Admin side onto Windows 2000 as part of a large migration exercise. We wished to switch off the Admin server once this migration had been completed.
However. the master replica for the NDS was located on the Admin server and so switching it off meant that no-one on the curriculum side was able to login (logically). With the Admin server on, login ability returned.
Should we have created a new partition, moved NDS into this and deleted the old Admin server?
This morning, a CNE logged in remotely to FSCURRICULUM1 and ascertained that the NDS master was now located correctly on FSCURRICULUM1
I have also changed the NWHost file on a number of PCs to remove reference to the Admin server, but this makes no difference to the ability for these PCs to log in. I am quite frustrated that I am missing something vital here. Can you help? My last thought that due to the random nature of the problem, that it may be DHCP related. The new admin PCs have static IP addresses. Is it possible that these static addressses are conflicting with those issued from FSCURRIC1 or that the scope needs extending. Unfortunately the system policy for the workstations prevents me from running anything useful in order to look at the ip config of a workstation that is not connecting for any reason. What do you think?
This problem is really frustrating - any help greatly appreciated. Anyone seen this before?
However. the master replica for the NDS was located on the Admin server and so switching it off meant that no-one on the curriculum side was able to login (logically). With the Admin server on, login ability returned.
Should we have created a new partition, moved NDS into this and deleted the old Admin server?
This morning, a CNE logged in remotely to FSCURRICULUM1 and ascertained that the NDS master was now located correctly on FSCURRICULUM1
I have also changed the NWHost file on a number of PCs to remove reference to the Admin server, but this makes no difference to the ability for these PCs to log in. I am quite frustrated that I am missing something vital here. Can you help? My last thought that due to the random nature of the problem, that it may be DHCP related. The new admin PCs have static IP addresses. Is it possible that these static addressses are conflicting with those issued from FSCURRIC1 or that the scope needs extending. Unfortunately the system policy for the workstations prevents me from running anything useful in order to look at the ip config of a workstation that is not connecting for any reason. What do you think?
This problem is really frustrating - any help greatly appreciated. Anyone seen this before?