Now, I've done these tasks following the help document
1. Install Remote Boot Server in the development system. Then I can find "Remote Boot Services" & "Trivial File Transfer Protocol" when I run services.msc
2. Deploy a image with " Windows RAM Disk Driver" Component to the target device, and complete FBA.
3. Copy the golden image to golden.sdi. Then create a final sdi file ramdisk.sdi, which use "SDIMgr /readpart" command
4. Configure Remote Boot Manager fields: "Client MAC Address" with the target device mac address, "Action" with "boot"
"Boot Server" with default valve, "Boot Program" with "startrom.n12", "Boot Image" with "ramdisk.sdi", and verify the field"use dhcp prot(67)?" is not checked
5. Configure the DHCP service on the same computer which has a static IP address. Set the address range, and add the option 60
6. Start the target device through network.
The result is that the target device can get DHCP IP address after a few minutes, but report the error message "PXE-E55: ProxyDHCP service did not reply to request on port 4011", that means the 3com PXE service did not start on my server device
I think I was puzzled by the help document. Does not " Remote Boot service" mean "PXE server"? If not, which PXE server tool and how can I install on my server device? If yes, how can I resolve the problem? What is the difference between the phrase "remote deploy" and "remote boot"
I'm just a newbie and thirst for you advise.

Arlin,

PXE-E55 error may be caused by many reason. Mostly it means your PXE client
does not "see" the tftp server.
I'd suggest you to check:
1. There is no switches or routers between the PXE client and the DHCP
server.
2. Make sure your server static IP and the dhcp IP range on the same subnet.
3. I recall some problems with 60 option when you add it to dhcp server
global scope instead of adding it to the IP range scope.
4. Check if BINL (Boot Information Negotiation Layer) service is running on
your server.

You may post here your IP configuration (server static IP, dhcp IP range,
masks) and more info from the client error (there should be IP information
in the error).
Also you can always use net monitor tools (like MS NetMon, Ethereal) to see
what is going on on your network between the client and the server.

KM

> Now, I've done these tasks following the help document:
> 1. Install Remote Boot Server in the development system. Then I can find
"Remote Boot Services" & "Trivial File Transfer Protocol" when I run
services.msc.
> 2. Deploy a image with " Windows RAM Disk Driver" Component to the target
device, and complete FBA.
> 3. Copy the golden image to golden.sdi. Then create a final sdi file
ramdisk.sdi, which use "SDIMgr /readpart" command.
> 4. Configure Remote Boot Manager fields: "Client MAC Address" with the
target device mac address, "Action" with "boot",
> "Boot Server" with default valve, "Boot Program" with "startrom.n12",
"Boot Image" with "ramdisk.sdi", and verify the field"use dhcp prot(67)?" is
not checked.
> 5. Configure the DHCP service on the same computer which has a static IP
address. Set the address range, and add the option 60.
> 6. Start the target device through network.
> The result is that the target device can get DHCP IP address after a few
minutes, but report the error message "PXE-E55: ProxyDHCP service did not
reply to request on port 4011", that means the 3com PXE service did not
start on my server device.
> I think I was puzzled by the help document. Does not " Remote Boot
service" mean "PXE server"? If not, which PXE server tool and how can I
install on my server device? If yes, how can I resolve the problem? What is
the difference between the phrase "remote deploy" and "remote boot"?

Thanks to KM
You 3rd suggestion resolves my problem. I add 60 option to the global scope before. I tried to delete it and add it to the IP address range. Now the client device can load sdi image
BINL service is not running on my server.Is'nt it necessary for PXE?

Arlin,

I am glad it helped you.
No, you don't need BINL (it gets used by RIS server but not RBS). However,
by default BINL uses the port #4011 so it could've been a possible problem
in your case. Anyway, you can forget about BINL now :-) as your problem was
about global scope.

KM

> Thanks to KM.
> You 3rd suggestion resolves my problem. I add 60 option to the global
scope before. I tried to delete it and add it to the IP address range. Now
the client device can load sdi image .