Troubleshooting 3Com Boot Services v.1.

02
Upgrade Earlier Versions o Boot Services to Boot Services v.1.02
Verify that end users have installed 3Com Boot Services v.1.02. If they are using an earlier
version, they will have ro!lems with the instructions and e"amles in the #uic$start %uide
and alication aer on &utomating %host with Boot Services.
Boot Services v1.02 automatically'
Creates the default directory c'(tft!oot and uts a samle !ootta! file in this directory
Sets )*)+ to secure mode, c'(tft!oot
Sets +,- as the reference in the 3Com Bootta! -ditor
)he a!ove stes will have to !e done manually if using an earlier version of Boot Services.
T!T" Troubleshooting
File not found error.
)his means that the )*)+ service could not find the file the client +C re.uested. )he full
filename is dislayed on the client +C screen. /a$e sure this filename is correct and that the
file e"ists
If you are wor$ing in secure mode, chec$ for conflicts with ath resolution in' the B00)+)&B
file, the 3Com /anaged +C Boot &gent Secure /ode setting 1found !y running
/B&C*%.-,-2, or the )*)+ Secure /ode otions 1found in settings, file transfer ta! of
)*)+ alication or service.2 3Com Boot Services 1.02 automatically sets )*)+ Secure
/ode to c'(tft!oot. 3e recommend that this setting is $et and the !ootta! file and all
image files are $et in this directory
&lso, there might !e an error in the B00)+)&B entry, there could !e an incorrect file
location, or the file may not !e in the secure directory. Chec$ the file ath, ensure that you do
not have a tying error, and ma$e sure the file is actually intact and where you thin$ it is
Access violation error.
)his message usually indicates one of the following'
)he re.uested file, menu !oot file, or !oot image file does not have everyone4read
ermission
5ou are attemting to transfer a file that resides in a directory outside of the designated
6secure mode6 directory. )he secure mode directory !y default is c'(tft!oot
Client timed out error.
Several situations could invo$e this message'
)*)+ may not !e running on the receiving comuter
& ac$et is not reaching the client. )*)+ is a loc$4ste rotocol that waits for the client to
ac$nowledge a ac$et !efore sending a new one
)he networ$ is congested and the client7s ac$nowledgment ac$et is not reaching the )*)+
networ$ server within the redetermined timeout duration. )ry increasing the timeout duration
in )*)+ 0tions, Settings, Configure )imeout
68na!le to Start Service6 entry in the 3indows 9) -vent Viewer &lication :og. +ossi!le
causes for an entry of this tye include that the ort num!er was in use or that S0C;32.<::
could not !e found
I requested a file with the "..\ path and my request was not fulfilled
3Com )*)+ ignores ..( aths to revent unauthori=ed end users from traversing u to
confidential directories
You receive a "file open" related error.
)he )*)+ service 1rather than the )*)+ alication2 cannot download files using maed
drives. )o wor$ around this ro!lem, you need to assign the service 1in the Startu )ye
Service window in 3indows 9)' clic$ )his &ccount and tye a secific account2 to an
account with a maed drive. >owever, lease note that this wor$around may comromise
security
You request a file, ut there is no response from the networ! server
>ere are some ossi!le reasons for a lac$ of resonse'
)*)+ has not !een started
)*)+ has not !inded to the correct 9IC
)he )*)+ server or )*)+ client is not configured roerly
"he file transfer stops suddenly
)here are many reasons for an interruted file transfer, !ut here are some ossi!le reasons'
5ou are transferring a large file and have e"ceeded the ma"imum num!er of acceta!le
!loc$s?@A,A3A !loc$s. Increase the !loc$si=e and try transferring the file again
5ou have e"ceeded the client timeout duration. If your networ$ is heavily loaded or
congested, you should increase the timeout duration
+,- )rou!leshooting
"he networ! ootstrap pro#ram or menu oot file is not supplied y the $%& server.
)his ro!lem can occur for several reasons'
)he networ$ !ootstra rogram or menu !oot file may not !e in the directory secified in the
B00)+)&B data!ase file
If you have the +,- server installed on a networ$ server that is not also running <>C+, you
must ena!le the +ro"y<>C+ feature. )he first time +,- is used, a romt to ena!le B+ro"y
<>C+C will !e dislayed. 5ou can also manually ena!leDdisa!le +ro"y<>C+ in the otions
menu
If +,- is running on the same server as <>C+ an otion tag needs to !e added to <>C+.
)his should have !een done automatically when +,- was installed. If you are not using
/icrosoft <>C+ or have a nonstandard /icrosoft <>C+ installation, you must add the otion
@0 6+,-Client6 tag string manually
)o add the otion @0 1B+,-ClientC2 to /icrosoft <>C+, follow these stes'
*or 3indows 9) E.0'
1. :aunch the /icrosoft <>C+ /anager on the networ$ server.
2. In the <>C+ Server ane, select the aroriate <>C+ Server I+ address 1or scoe2 from
the list.
3. *rom the <>C+ 0tions menu, select <efaults.
E. )he <>C+ 0tions' <efault dialog !o" aears.
A. Clic$ 9ew, the &dd 0tion )ye dialog !o" aears.
@. In the 9ame field, enter Class I<.
F. Select String from the <ata )ye dro4down list.
G. -nsure that the &rray otion is not selected.
H. In the Identifier field, enter @0.
10. Clic$ 0;.
11. )he <>C+ 0tions' <efault Values dialog !o" aears.
12. In the 0tion 9ame field, select 0tion 0@0 Client I< from the dro4down list.
13. In the Value field, enter +,-Client.
1E. Clic$ 0; to return to the <>C+ /anager.
*or 3indows 2000'
1. *rom the Start menu, select &dministrative )oolsD<>C+.
2. Select Server 0tions from the <>C+ tree listing in the left window ane.
3. *rom the &ction menu, select Configure 0tions.
E. *rom the list of availa!le otions, ena!le otion @0, ClassI<.
A. -nter +,-Client for the otion @0 string array.
@. Clic$ 0;.
F. )he ClassI< otion should now !e listed under the Server 0tions.
G. Close the <>C+ configuration rogram.
You receive a 'not found messa#e for a client $C in the $%& application window.
)his message aears for several reasons'
)he client +C may not have !een added to the B00)+)&B data!ase file
)he media access control 1/&C2 address secified in the B00)+)&B data!ase file for the
client +C may !e incorrect
)he synta" 1colons, !ac$slashes, etc.2 of the client entry in the B00)+)&B file may !e
incorrect. 3hen you receive a Bnot foundC message in the +,- alication 1rather than +,-
service2 on4screen monitorDlog, you have the otion of .uic$ly resolving the ro!lem !y
creating a new B00)+)&B entry
$%& &()* Could not locate oot server error.
If <>C+ is on the same server as the +,- server, ma$e sure that 0tion )ag @0 is listed in
the <>C+ Server
If <>C+ is running on a different server than the +,- server, ma$e sure that you ena!le
+ro"y <>C+
/a$e sure that all routers are configured correctly. +ort E011 needs to !e ena!led and
+,-D<>C+ re.uests need to !e forwarded
"#E $enu Boot !ile
+,- menu !oot files 1or networ$ !ootstra rograms2 are mandatory in 3ired for /anagement
13f/2 environments. )herefore, a client !ooting +,- must !e assigned to a +,- menu file, not a
)C+DI+ image file.
-"amle, an end user creates a )C+DI+ 9etwor$ Boot Image with the Symantec %host Boot
3i=ard. In the 3Com Bootta! -ditor they assign that !oot image to a client !ooting +,-. )his
will result in a )*)+ error. )he user must use the 3Com Image -ditor to create a +,- menu file
from the image created !y the Symantec %host Boot 3i=ard and assign this +,- menu file to the
clients !ooting +,-.
-ach +,- menu !oot file can contain u to 1@ !oot otions, including )C+DI+ !oot image files,
other +,- menu !oot files, or the local hard drive. )hese menu !oot files normally have I.+,-
e"tensions and have a ma"imum si=e of @ ;B, no matter how many !oot otions are included,
!ecause !oot otions are merely referenced from the +,- menu !oot file.
If there is only one !oot otion referenced in a +,- menu !oot file, the end user does not see the
!oot menu interface?the !oot otion is loaded and e"ecuted automatically.
Boot %mage Editor Troubleshooting
&dit File* File too lar#e.
)his message usually aears when you select a te"t4!ased file within a !oot image file and then
select -dit from the *ile menu. )he te"t editor that is shied with Boot Image -ditor only oens
files under @E ;B. )o edit the selected file, e"tract the file, oen it with a te"t editor or word
rocessor outside of Boot Image -ditor, and then add it to the !oot image file again.
&rror* +ot enou#h space in ima#e to add file
3hen you first create a !oot image file with Boot Image -ditor, you must secify the ma"imum
caacity of the image file. If the si=e of the !oot image file is aroaching the secified ma"imum
when you try to add another file, you receive this message. 0nce an image file has !een created,
you can not increase the si=e of the image. 5ou can solve the ro!lem in two ways' <elete
any unnecessary !ootstra files from within the !oot image file and then try adding the new file
again.
*or e"amle, the user has created a )C+DI+ 9etwor$ Boot Image with the Symantec %host Boot
3i=ard. )his !oot image is automatically created as a 1.EE /B image. If the user wishes to add
other utilities such as ghostwal$er to the image, it will not fit into 1.EE /B of sace. If the
intended client +C has enough memory to suort a larger !oot image file, create a !oot dis$
from the image and then create an e"tended image from the !oot dis$. )o do this'
1. :aunch the 3Com Boot Image -ditor.
2. Clic$ on -dit an -"isting Image.
3. 0en the !oot image created !y the %host Boot 3i=ard.
E. Clic$ on the floy !utton on the tool!ar. )his will create a !oot dis$ from the image. 5ou
may need to ta$e the floy out and ut it !ac$ in for the 3indows 0S to recogni=e the
image.
)o create an e"tended image from the !oot dis$'
A. Clic$ on Create a 9ew Boot Image *ile from the main window.
@. +rovide a name for the image and select an e"tended caacity.
F. If using 3com7s "B&&T utility, select the +re40S otion. & re4oerating system 1+re40S2
connection can !e esta!lished !etween the client +C and the networ$. )his +re40S
connection ena!les a client +C to download and e"ecute centrally administered des$to
management agents from a networ$ server !efore loading the end user7s referred oerating
system from the local hard drive. Client +Cs terminate the +re40S connection 1or conduct a
very soft CtrlJ&ltJ<el2 with the +B00) utility and continue to !oot from the local hard drive.
G. Clic$ 0;. 5ou will now !e a!le to add files to this new image.
If the !oot image file is larger than a standard floy dis$ette, you must create a new image from
scratch.
You receive a messa#e related to the ,.-Y- file e.tension.
S5S is the default e"tension for 9et3are !oot image files. )his e"tension usually generates a
message !ecause 3indows normally registers the I.S5S e"tension without associating it with a
articular alication.
'indo(s 2000 Server 'ith )emote %nstallation Services *)%S+ %nstalled
Troubleshooting
An error has occurred when indin# the window soc!et.
/icrosoft7s )*)+ service is running. Sto the /icrosoft)*)+ service !efore starting the 3Com
Boot Services )*)+ service or alication.
&rror /001)* 2nale to ind soc!et to $ort 10//.
)he /icrosoft BI9: service is running. Sto the /icrosoft BI9: service !efore starting the 3Com
+,- service or alication.
Using B&&T"
3hen creating a )C+DI+ 9etwor$ Boot Image with the %host Boot 3i=ard, you can secify that
you are using static I+ addresses. 5ou must rovide the address and it gets hard coded in the
wattc.cfg in the !oot image. )herefore, the !oot image is secific to 1 client. & !oot image will
need to !e created for each client in order to rovide uni.ue I+ addresses.