3Com e-PC c10/s10, Руководство пользователя, Страница: 97 / 122

C C h h a a p p t t e e r r 9 9 8 8 5 5
rplcmd %1 < %2
goto end
:error
echo rplup <computername> <scriptfile>
echo example: rplup \\nt_server feth.rpl
:end
T
T
r
r
o
o
u
u
b
b
l
l
e
e
s
s
h
h
o
o
o
o
t
t
i
i
n
n
g
g
When things do not work, check these situations to resolve the most likely problems:
Unknown Client NIC ID
If an “unknown client NIC ID” line appears within the NT Server Remoteboot Manger console
while attempting a PC boot, it indicates the PC’s prefix (VendorName) is not defined. Use the
following example to define the prefix. The VendorName field is a unique six-digit value
assigned to the NIC vendor; this value is the most significant six digits of the NIC’s Ethernet
address.
Even though it appears a valid VendorName exists for your NIC, it may be that you have a
newer NIC that had a different VendorName value. To correct this problem, create a new
remoteboot configuration or add the NIC to an existing profile as outlined in the Windows NT
Server Installation Guide. Follow the example and add the new six-digit prefix to the
VendorName parameter.
You must use the RPLCMD utility to add the new VendorName (the first six digits of the NIC’s
node ID) to the NIC’s profile. The following example demonstrates how to add the new
VendorName to an existing profile and assumes that VendorName is 002F00. Enter the
correct VendorName for your NIC.
c:\winnt\rpl> rplcmd
adapter boot config profile service vendor wksta [quit}: b
add del enum: a
bootname=dosh
vendorname=002f00
bbcfile=bblock\netbeui\feth\dosbb.cnf
bootcomment= abc fastethernet
windowsize=0
Searching for DLC RPL Server, retries=nnnnnn
If you see the PC screen stopping at this message and the retry count is increasing, it
indicates that MBA cannot find an active NT server running the Remoteboot Service.
Check the following:
Does a proper connection to a file server exist?
Is at least one server running the Remoteboot Service?
Is the NT Server RPL service rejecting PC requests because the RPL service does
not support the NIC you are using? See “ Unknown Client NIC id ” in this section.
Is there a Remoteboot Manager console for an existing PC entry for the NIC? If one
does not exist, refresh the screen (View Refresh) to see if the NIC’s RPL broadcast
was received.
Is there a Remoteboot Service error in the Event Viewer log?