I seem to be having the same problem that a few others are having. I recently installed Windows Server 2003 on a server that used to host RIS via Windows 2000 Server. The server has kept the same IP address and Name since the upgrade. I have authorized and re-authorized the RIS server in DHCP numerous times. All of the RIS services are running, although the RIS server shows a BINLSVC EVENT (1003) every 4 hours. I am not sure if this is normal

The weird thing is, RIS was working perfectly for the last two years when we had the server running Windows Server 2003.

The problem is that I can't get any clients to boot up via PXE boot. I just see "DHCP....." followed with a PXE-E53: No Boot Filename Received. The kicker is that I can use the RIS boot disk (on the few computers that have compatible NICs) and it works fine

Does anyone have any ideas?

Hey Dan,

I'm a little confused based on your post. You stated that you upgraded this
server from Win2k to Win2k3 and it USED to house RIS, but yet RIS is still
functioning. Is RIS now on a different machine running Win2k?

Also, could you provide the details of the 1003 event? Does it mention
anything about SiS? Are you doing anything different with pre-staging the
clients?

--
Doug Allen, Windows 2000 MCSE

This posting is provided "AS IS" with no warranties, and confers no rights.
OR if you wish to include a script sample in your post please add "Use of
included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm"



"Dan B." <(E-Mail Removed)> wrote in message
news:BB15FEF2-72BA-4EE3-809B-(E-Mail Removed)...
> I seem to be having the same problem that a few others are having. I
recently installed Windows Server 2003 on a server that used to host RIS via
Windows 2000 Server. The server has kept the same IP address and Name since
the upgrade. I have authorized and re-authorized the RIS server in DHCP
numerous times. All of the RIS services are running, although the RIS
server shows a BINLSVC EVENT (1003) every 4 hours. I am not sure if this is
normal.
>
> The weird thing is, RIS was working perfectly for the last two years when
we had the server running Windows Server 2003.
>
> The problem is that I can't get any clients to boot up via PXE boot. I
just see "DHCP....." followed with a PXE-E53: No Boot Filename Received.
The kicker is that I can use the RIS boot disk (on the few computers that
have compatible NICs) and it works fine.
>
> Does anyone have any ideas?

Sorry for the confusion

Our MIS server was originally a Win2K SVR box that was running RIS. Domain Controllers DC1 and DC2 both run DHCP services and are Win 2K3 Boxes

I performed a clean installation of Win SVR 2k3 on the MIS server and configured RIS again. The name and IP address of the server is identical to when it was a Windows 2000 server. I made sure the MIS server is authorized in DHCP and I restarted the DHCP services numerous times. I also tried removing the Default Gateway from the DHCP scope, but that didn't seem to help either. Lastly, I performed the risetup -check to verify that RIS is running correctly and that all the services associated with RIS were functioning.

Even after checking everything I am still not able to boot a client via PXE. All the clients are the same as they were when I was using Windows 2000 Server for RIS. The RIS boot disk even works with the clients that have NICs that are supported by the boot disk

As for the 1003 event the following is all it mentions: The Remote Installation service successfully read its settings from the directory service

Any ideas would be greatly appreciated!!

Do you see where the PXE clients get an IP, but just no reponse from RIS?
Or do they not even get an IP from the DHCP server?

I know that some of the following might be redundant, but I want to be
thorough.

Fisrt verify the RIS installation using the Active Directory Users and
Computers Snap-in. Select Domain Controllers and get properties of the RIS
server. Click on the Remote Install tab and verify that the "Respond to
client computers requesting service" check box is enabled. Next verify that
the RIS server is "authorized" to perform the BINL function on the network.
To verify and/or "authorize" a server, utilize the network's DHCP Manager
and
select the DHCP root. Next choose Action --> Manage Authorized Servers...
Then verify that the RIS server is member of the authorized servers list.
If
not simply add it via IP address or name. After accomplishing this task
review the RIS server's application log to verify that the following events
are logged. Event 1003 in the Application log and event 1044 in the System
log . These events will help to verify that the BINL fucntion is available
for PXE clients.

If this still doesnt work, there could be a problem in AD because of the
machine's account from before and now. Was the machine acct in AD deleted
and re-created?

--
Doug Allen, Windows 2000 MCSE

This posting is provided "AS IS" with no warranties, and confers no rights.
OR if you wish to include a script sample in your post please add "Use of
included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm"



"Dan B." <(E-Mail Removed)> wrote in message
news:9A65322F-03B8-4949-92AD-(E-Mail Removed)...
> Sorry for the confusion.
>
> Our MIS server was originally a Win2K SVR box that was running RIS.
Domain Controllers DC1 and DC2 both run DHCP services and are Win 2K3 Boxes.
>
> I performed a clean installation of Win SVR 2k3 on the MIS server and
configured RIS again. The name and IP address of the server is identical to
when it was a Windows 2000 server. I made sure the MIS server is authorized
in DHCP and I restarted the DHCP services numerous times. I also tried
removing the Default Gateway from the DHCP scope, but that didn't seem to
help either. Lastly, I performed the risetup -check to verify that RIS is
running correctly and that all the services associated with RIS were
functioning.
>
> Even after checking everything I am still not able to boot a client via
PXE. All the clients are the same as they were when I was using Windows
2000 Server for RIS. The RIS boot disk even works with the clients that
have NICs that are supported by the boot disk.
>
> As for the 1003 event the following is all it mentions: The Remote
Installation service successfully read its settings from the directory
service.
>
> Any ideas would be greatly appreciated!!
>

Forgot to paste this as well.

284987 PXE Client Receives a "No Reply From Server" Error During RIS Server
http://support.microsoft.com/?id=284987

--
Doug Allen, Windows 2000 MCSE

This posting is provided "AS IS" with no warranties, and confers no rights.
OR if you wish to include a script sample in your post please add "Use of
included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm"



"Dan B." <(E-Mail Removed)> wrote in message
news:9A65322F-03B8-4949-92AD-(E-Mail Removed)...
> Sorry for the confusion.
>
> Our MIS server was originally a Win2K SVR box that was running RIS.
Domain Controllers DC1 and DC2 both run DHCP services and are Win 2K3 Boxes.
>
> I performed a clean installation of Win SVR 2k3 on the MIS server and
configured RIS again. The name and IP address of the server is identical to
when it was a Windows 2000 server. I made sure the MIS server is authorized
in DHCP and I restarted the DHCP services numerous times. I also tried
removing the Default Gateway from the DHCP scope, but that didn't seem to
help either. Lastly, I performed the risetup -check to verify that RIS is
running correctly and that all the services associated with RIS were
functioning.
>
> Even after checking everything I am still not able to boot a client via
PXE. All the clients are the same as they were when I was using Windows
2000 Server for RIS. The RIS boot disk even works with the clients that
have NICs that are supported by the boot disk.
>
> As for the 1003 event the following is all it mentions: The Remote
Installation service successfully read its settings from the directory
service.
>
> Any ideas would be greatly appreciated!!
>