I have created a testing/learning windows 2003 server environment with 3 clients. The server is setup with DNS, Active Directory, DHCP and RIS. Currently I have been trying to install XP on the clients using RIS but I keep getting PXE-E53: No boot filename received. Now I have done my research and most everyone points to the knowledge base below. But I have gone through them and for the most part my network checks out, a couple of things I do not understand. I have put the article that everyone refers to and I have put my comments in caps next to them. I am hoping to get some advice to see what I am doing wrong.
Trouble Shooting RIS client issues (PXE)
Problem/Error: PXE client does not connect to the RIS server (never receives a prompt to press F12). In addition, the client may receive a "PXE-E53: No Boot filename received from BINL, DHCP, or BOOTP" error mesage.
Proposed Actions/Solutions:
? Check the PXE revision of the client, especially in the case where a router separates the client and the RIS server. The currently recommended version is 99N or greater. I DONT KNOW WHERE TO CHECK FOR THIS. I HAVE A 3COM PXE AND I WENT TO THEIR WEBSITE AND DID NOT SEE ANY FIRMWARE UPDATES.
THIS IS THE MODEL PXE CARD I HAVE - 3C905CX-TX-M
? Check to see that the RIS services are running (BINL, TFTP, and the Groveler service). To do this, click Start, click Run, type risetup -check, and then click OK. THIS ALL CHECKS OUT FINE
? Check the RIS server to see if the "Answer all Clients" or "Answer only known clients" option is enabled. If the client is not pre-staged in Active Directory and the RIS server has the "Answer only known clients" option enabled, the RIS server does not respond. For more information, please refer to the "Pre-Staging Client Computers" section of this white paper. THIS ALSO CHECKS OUT.
? Verify that the RIS server is authorized in the domain. RIS servers do not respond if the server is not authorized. Use the DHCP Management snap-in to view authorized servers. If the RIS server is not displayed in the list of authorized servers, use the following steps to authorize the server and stop and start the RIS service: THIS IS GOOD TO GO.
? If a router separates the client and RIS server, and clients on the same segment as the RIS server are answered but clients on other segments are not, check the following:
Check to see if the router is forwarding DHCP or IP requests. A good test for this is to see if other clients (Windows 95/98, Windows NT, and so on) can obtain an IP address from that server. If the clients can obtain an IP address, the router may be misconfigured. Check to see if the router has an IP helper address for the RIS server (for more information, refer to the "Deploying RIS Servers" section of this document).
THIS I AM NOT SURE ABOUT. THE ROUTER IS IN ANOTHER ROOM OF THE HOUSE AND THE NETOWRK IS CONNECTED THROUGH AN ETHERNET CONVERTER. I LOOKED IN MY ROUTER AND DID NOT FIND ANY SECTION THAT HAS A HELPER ADDRESS. IN DHCP THE CLIENTS DO GET AN ADDRESS LEASED TO THEM.
? If RIS and DHCP are on the same computer, make sure the ResponseDelay value is set to 0. This value is located in the following registry key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Binlsvc\Parameters THIS CHECKS OUT
|
