RIS Problem: 2000 domain with 2003 RIS Server

  • Thread starter Thread starter Microsoft
  • Start date Start date
M

Microsoft

Hi all - hoping someone here can help.


Here's the setup:
-----------------
1. Windows 2000 Domain (DCs running SP4, mixed mode)
2. Server1 = W2K, SP4, DHCP, RIS
3. Server2 = W2K3, RIS
4. Some clients configured to RIS to server1, some set to RIS to server2


Here's the problem:
--------------------
1. Clients using server1 have no problem.
2. Clients using server2 boot, show the F12 prompt, and then hang with a
black screen when F12 is pressed.


Variations:
------------
1. Configure server1 to stop responding to clients, server2 clients work
fine. Set server1 to start responding, server2 clients hang.

2. Switch DHCP to server2, server2 clients can now RIS but server1 clients
either hang with either "OS Chooser 5.2" or with an "NTLDR is corrupt"
error.

3. Replace server2 with a Windows 2000 box, all is fine.

4. Test network with both server1 and server2 as W2K3 servers works fine.


Other information:
------------------
1. RIS debug logs on server2 show that clients contact server2, and server2
responds with a broadcast to 255.255.255.255. It never proceeds beyond this
step.

2. RIS debug logs on server1 show that server1 also responds to the client
(even though it shouldn't, right?) and sends its response to the x.x.x.x IP
address of the client.

Does anyone have any clever ideas? It seem as though the client is getting
confused by responses from two servers, though only one should be
responding. Any help you can offer would be great.

Jeff
 
Answre found!

Replacing the ntldr and startrom.com files on the Windows 2000 RIS server
with those found on the Windows Server 2003 server solved the problem.

Jeff
 
Back
Top