Netservices problems with RIS

Archived from groups: microsoft.public.win2000.setup_deployment (More info?)

I have recently installed a new RIS server in one of my remote sites and
they are having problems receiving a boot file this is what I notice is
different from my working RIS servers in other remote site and this one:

Here is a working RIS server
dn:
CN=kin-stgw01.ehp.na.mydomain.com,CN=NetServices,CN=Services,CN=Configuration,DC=am,DC=mydomain,DC=com

Here is the non-working server:

dn:
CN=10.75.98.42,CN=NetServices,CN=Services,CN=Configuration,DC=am,DC=mydomain,DC=com

one registered the FQDN and the other registered the IP address:

The RIS servers address is 10.75.98.42 and the DHCP server is 10.75.98.43,
so the are both on the same network. The clients are all on different
subnets than the RIS server and the DHCP server. All of our switched have
helper addresses for the DHCP server only in all sites (working and
non-working). In the non-working site If I boot a client into windows it
will obtain an IP address with no problem. but if I do a PXE boot I receive
PXE-E53 : No boot filename received

PXE-M0F: Exiting Intel Boot Agent.



Do the fact that the server (for some reason) registered its IP address
insted of a FQDN in AD have anything to do with the problem?