Ris(remote Installation Services), Problems connecting to se

[Tod]

Ris(remote Installation Services), Problems connecting to server

I am trying to to use RIS for a win2kpro install. I have the correct boot disk and the NIC is PXE enabled. The server has all the requirements, DHCP, DNS, and active directoy. I sniffed the packets and it seems that the broadcasts sent by the client are being received by the server and then the server sends a broadcast message offering an IP address, but for some reason the client will not take it. I wanted to make sure there were no problems so, i connected the server and the client up directly using a crossover cable. Any tips on what the problem may be?

[Curt]

Is the server win2kpro or win2kserver, and is the client win2kpro?
are you using a domain or workgroup?
do both machines have the same domain/workgroup name and unique computer names?
Is DHCP enabled on the client?
I'll have to dig out my old textbooks on RIS - I haven't used it since I learned it in school.

[Sam]

The server is win2kpro and im trying to install win2kpro on the client.
I am using a domain.
The server is on the domain and has a unique computer name. The client machine has nothing on it. I am starting from scratch, so the client is not on the domain and also does not have a unique name. I used the RBFG.exe utility to make a boot disk.
DHCP is enabled
The error message im getting is "Cannot Connect to server".

[Sam]

I've looked in both my win2k books and my winXP books - every reference to RIS says that you must install the RIS service on a Win2kServer... not win2kpro. That could be why you keep getting the message "unable to connect to server". It's looking for a win2kServer and not a win2kpro machine.
Also, when you connect a server directly to the client, then you leave the Domain controller out of the loop. A windows 2000 domain controller is required to authorize the RIS server in Active Directory and hold configuration information for pre-staged client computers.
install the DHCP service on the RIS box itself and authorize it in Active Directory