Ошибка no boot filename received

Страницы: [1]   Вниз

0 Пользователей и 1 Гость просматривают эту тему.

Страницы: [1]   Вверх

Перестал загружаться один клиент.

Progress!

I got to the Recovery Console, did the repair, and got back into Windows. There are still some problems, however, which I’ll detail below.

But first let me back up and recount one difficulty I encountered along the way. It wasn’t so clear to me from your instructions on how to actually set the VMWare SCSI Drivers as the Floppy for the Virtual Machine. You gave a good hint when you talked about Virtual Machine Settings, but I want to mention more specifically how I got it to work, so that anyone who reads this won’t have to get stuck at that point.

If you remember I had already tried to to Recovery Console but had run into the following error:

I can see the CD-ROM drive, and even tried to reinstall Windows. That didn’t work it said because it can’t find a hard drive.

And you replied:

This is because the Virtual Machine is use a SCSI virtual hard disk and a driver must be loaded from a virtual floppy when booting under these conditions or to attempt to repair the Windows Registry using information above so to do this have a look at the following.

If the Virtual Machine was created using Windows Easy Install or has a VMware SCSI Virtual Hard Disk you need to download the VMware SCSI Drivers<http://download3.vmware.com/software/vmscsi-1.2.0.4.flp> and set the vmscsi-1.2.0.4.flp file as the Floppy for the Virtual Machine in the target Virtual Machine’s Settings sheet. This floppy image contains the VMware SCSI Disk Drivers needed when booting with the Windows XP CD and you need to press F6 when it says «Press F6 if you need to install…» near the bottom of the Virtual Machine window and it will then prompt for the driver after it continues to load additional files. Just follow the prompts.

First of all, when I clicked on the link above for VMWare SCSI Drivers it just came up with an html page in Safari with all the internal contents/code for the drivers displayed. I had to right click on the download button and specifically tell it to download with my download manager. Then, I was able to get it downloaded as a file on my hard drive.

Secondly, as far as getting the Floppy for the Virtual Machine in the target Virtual Machine Settings set, I had to go into ‘Other Devices’ and from the ‘+’ drop down box, choose ‘Add Floppy’. That opens up ‘Choose a floppy image’ dialog box, which is like a Finder interface, so you just have to navigate to wherever the SCSI Driver floppy file is located on your hard drive, and when you boot into Windows XP setup, hit the F6 button, it will later automatically bring up the floppy file.

Anyway, I was able to get the SCSI drivers to load and then do the repair using Recovery Console as you mentioned in your earlier email. I’m very happy about that.

However, I should say that as it was booting into Windows the first time, I got the following error message:

I just hit ‘Yes’ on the top dialog box, and when it restarted there wasn’t any further error message like the one on the bottom.

As soon as I Windows loaded, I immediately tried to install VMWare Tools and got the error message below:

And, in a, perhaps, related problem, now Windows is a bit wonky. Any installed program, such as Word, etc. won’t start, coming up with various error messages. Programs installed automatically with XP such as Notepad and Paint work fine. Here are error messages for Excel—there were two error messages in succession:

#1

#2:

Any further help you can give would be greatly appreciated.

Thanks,

Ed

In a PXE environment the PXE client minimally must receive:

1. IP address
2. TFTP server IP address
3. Boot filename

This info is sometimes provided by a single DHCP server (which is PXE enabled) or by a regular DHCP server (non PXE enabled) providing only IPs and a complementary proxyDHCP server only providing the rest of the PXE related parameters.

In your case it looks like (despite which method you are using) the Boot filename info is missing from the DHCP/proxyDHCP offer.

You can easily check this by running a Wireshark capture at your DHCP/proxyDHCP server and see if the DHCPOFFER contains the Boot filename info or not.

Your case looks like a typical DHCP/proxyDHCP miss-configuration

From PXE error codes

• PXE-E53: No boot filename received. The client received at least one
valid DHCP/BOOTP offer, but does not have a boot filename to download.
There are several possible causes:

1) The DHCP Server and the PXE Server were located on the same server, but one of them was moved to a different server. This would
result in an incorrect PXE Server configuration.

To resolve this issue, reinstall the PXE Server component of the Altiris Deployment Solution.

2) The DHCP relay agent, either a Proxy DHCP Server or a switch configured with helper addresses, is not configured correctly. For
example, if DHCP and PXE are on separate servers, the DHCP relay agent
needs to have both addresses in its configuration.

To resolve this issue, correct the DHCP relay agent configuration.

3) If the Microsoft DHCP service is installed on the PXE server, but is disabled or unconfigured, Altiris PXE Setup configures PXE to
work with the local DHCP service (even if the DHCP service is
disabled). This causes the PXE server to not respond to PXE clients
that get a DHCP address from DHCP services running elsewhere on the
network.

To resolve this issue, remove Microsoft DHCP services from the PXE server and reinstall the PXE Server component of the Altiris Deployment Solution.