Guest JohnSmith1 Posted December 8, 2007 Posted December 8, 2007 I have Windows Server 2003 Enterprise Edition. I am trying to deploy some XP pro over Remote Installation. I have configured Active Directory, DHCP, DNS. When I turn the client computer on to install xp pro from RIS I get below message: "PXE-E53: No boot filename received". Why is that? Any idea please?
Guest Meinolf Weber Posted December 9, 2007 Posted December 9, 2007 Re: PXE-E53 Hello JohnSmith1, From another posting: 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. ? 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. ? 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. ? 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: a. Click Start, click Run, type cmd, and then click OK. b. At the command prompt, type the following commands pressing ENTER after each command: net stop binlsvc net start binlsvc c. To verify the server is authorized, check the application event log for an event ID 1045. ? 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). ? 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 Also you can try to set in DHCP the option 66 with "server ipaddress" (without qoutes) and option 67 with the path to the starting file "oschooser\\i386\\filename.com" (with the qoutes) Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights. ** Please do NOT email, only reply to Newsgroups ** HELP us help YOU!!! http://www.dts-l.org/goodpost.htm > PXE-E53: No boot filename received >
Guest JohnSmith1 Posted December 11, 2007 Posted December 11, 2007 Re: PXE-E53 Thanks that sort out the program but I have another one which is: The operating system image you selected does not contain the necessary drivers for your network adapter. Try selecting a different operating system image. If the problem persists, contact your system administrator. Setup cannot continue. Press any key to exit. any idea? how to sort it out. regards, "Meinolf Weber" wrote: > Hello JohnSmith1, > > From another posting: > > 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. > ? 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. > ? 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. > ? 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: > a. Click Start, click Run, type cmd, and then click OK. > b. At the command prompt, type the following commands pressing ENTER > after each command: > net stop binlsvc > net start binlsvc > c. To verify the server is authorized, check the application event log > for an event ID 1045. > ? 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). > ? 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 > > > Also you can try to set in DHCP the option 66 with "server ipaddress" (without > qoutes) and option 67 with the path to the starting file "oschooser\\i386\\filename.com" > (with the qoutes) > > > Best regards > > Meinolf Weber > Disclaimer: This posting is provided "AS IS" with no warranties, and confers > no rights. > ** Please do NOT email, only reply to Newsgroups > ** HELP us help YOU!!! http://www.dts-l.org/goodpost.htm > > > PXE-E53: No boot filename received > > > > >
Guest Meinolf Weber Posted December 11, 2007 Posted December 11, 2007 Re: PXE-E53 Hello JohnSmith1, Check out this one: http://support.microsoft.com/kb/823658 Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights. ** Please do NOT email, only reply to Newsgroups ** HELP us help YOU!!! http://www.dts-l.org/goodpost.htm > Thanks that sort out the program but I have another one which is: > > The operating system image you selected does not contain the necessary > drivers for your network adapter. Try selecting a different operating > system image. If the problem persists, contact your system > administrator. > > Setup cannot continue. Press any key to exit. > > any idea? how to sort it out. > > regards, > > "Meinolf Weber" wrote: > >> Hello JohnSmith1, >> >> From another posting: >> >> 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. >> ? 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. >> ? 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. >> ? 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: >> a. Click Start, click Run, type cmd, and then click OK. >> b. At the command prompt, type the following commands pressing >> ENTER >> after each command: >> net stop binlsvc >> net start binlsvc >> c. To verify the server is authorized, check the application >> event log >> for an event ID 1045. >> ? 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). >> ? 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\Paramete >> rs >> Also you can try to set in DHCP the option 66 with "server ipaddress" >> (without qoutes) and option 67 with the path to the starting file >> "oschooser\\i386\\filename.com" (with the qoutes) >> >> Best regards >> >> Meinolf Weber >> Disclaimer: This posting is provided "AS IS" with no warranties, and >> confers >> no rights. >> ** Please do NOT email, only reply to Newsgroups >> ** HELP us help YOU!!! http://www.dts-l.org/goodpost.htm >>> PXE-E53: No boot filename received >>>
Recommended Posts