Getting error " DOS error SYS0006 occurred trying to load "A:\NET\NET.EXE". The REQUESTER service is not started." - PowerEdge General HW Forum - Servers - Dell Community

Getting error " DOS error SYS0006 occurred trying to load "A:\NET\NET.EXE". The REQUESTER service is not started."

Servers

Servers
Information and ideas on Dell PowerEdge rack, tower and blade server solutions.

Getting error " DOS error SYS0006 occurred trying to load "A:\NET\NET.EXE". The REQUESTER service is not started."

  • Hi,

    I am using symantec Ghost to take the image of my disk on Dell Power Edge 6650 server but unfortunately while booting it from either lan or diskette I am getting error "DOS error SYS0006 occurred trying to load "A:\NET\NET.EXE". The REQUESTER service is not started.".

    If anybody is having any idea ..help me.

    Server is having Broadcom Netxtreme gigabit ethernet card.

    Pls Help..

     

    Jay

  • Do a DIR A: /B /S>FILES.TXT

    And post the file list.

    Also post the config.sys, autoexec.bat, protocol.ini files.

    NET cannot run because network drivers arent loaded.

    Report Unresolved Customer Service Issues here
    I do not work for Dell. I too am a user.
    The forum is primarily user to user, with Dell employees moderating
    Contact USA Technical Support

    Get Support on Twitter @DellCaresPro

  • I run the command  dir A:/B/S>Files.txt

    I could not understand the thing Post the file list and Post the Config.Sys,Autoexec.bat,Protocol.INI.

    So I opened the files,txt and pasted all three files in the Files.txt.

    Still I am getting this error. May be I am not doing the right thing as per suggestion.

    Please elaborate this in detail.

    Thanks for the reply and looking for the next reply too.

    Thanks

    Jay

  • Here is the file which You were asking for

    ******************************************************************************************************************************

    A:\IBMBIO.COM
    A:\IBMDOS.COM
    A:\COMMAND.COM
    A:\MOUSE.COM
    A:\HIMEM.SYS
    A:\AUTOEXEC.BAT
    A:\CONFIG.SYS
    A:\NET
    A:\files.txt
    A:\NET\DHCP
    A:\NET\PROTMAN.DOS
    A:\NET\NTSTS.DOS
    A:\NET\DLSHELP.SYS
    A:\NET\PROTMAN.EXE
    A:\NET\NET.MSG
    A:\NET\NETH.MSG
    A:\NET\CMDS16.EXE
    A:\NET\NETXP.MSG
    A:\NET\NET.EXE
    A:\NET\PROTOCOL.INI
    A:\NET\NETWORK.INI
    A:\NET\B57.dos
    A:\NET\B57.INS
    A:\NET\NET.CFG
    A:\NET\readme.txt
    A:\NET\release.txt
    A:\NET\b57.com

    ***************************************************************************************************************************

    CONFIG.SYS

    DEVICEHIGH=A:\HIMEM.SYS
    DOS=HIGH,UMB
    LASTDRIVE=Z
    DEVICEHIGH=A:\NET\PROTMAN.DOS /i:A:\NET
    DEVICEHIGH=A:\NET\B57.dos
    DEVICEHIGH=A:\NET\NTSTS.DOS
    DEVICEHIGH=A:\NET\DLSHELP.SYS

    **************************************************************************************************************************

    AUTOEXEC.BAT

    @ECHO OFF
    SET PATH=A:\NET\;a:\;%PATH%;
    SET TEMP=A:\
    SET TCPHELP=A:\NET
    SET ETCDIR=A:\NET
    REM \MOUSE.COM
    A:\NET\NET START
    A:\NET\NET.EXE USE G: \\m2g2dhcp\ghost
    g:\ghost

    *******************************************************************************************************************************

    PROTOCOL.INI

    [network.setup]
    version=0x3100
    netcard=NIC,1,NIC
    transport=nts$ntst2,NTS$NTST2
    transport=ibm$netbeui,IBM$NETBEUI
    lana0=NIC,1,ibm$netbeui
    lana1=NIC,1,nts$ntst2

    [NTS$NTST2]
    DefaultDomain=trishul_domain
    BOOTPFLAG=DHCP
    DriverName=ntsts$
    VCs=16
    VCReceiveLarge=6
    VCSends=6
    RcvWindow=2920
    UseMemory=UMB
    BINDINGS=NIC
    LANABASE=1

    [protman]
    DriverName=PROTMAN$
    PRIORITY=ibm$netbeui

    [IBM$NETBEUI]
    DriverName=netbeui$
    SESSIONS=20
    NCBS=20
    BINDINGS=NIC
    LANABASE=0

    [nic]
    drivername = B57$
    ; (optional) FUll Duplex(0=HalfDuplex,1=FullDuplex)

    ; FULLDUPLEX = 0

    ; (optional) SPEED(10=10M bts,100=100M bts)

    ; SPEED = 100

    ; (optional) AUTO(1=AUTO-Negotiation,0=ForceMode)

    ; AUTO = 1

    ; (optional) Slot number

    ; SLOT = 1

    **********************************************************************************************************

     

     

  • You seem to be running netbeui and arent doing netbind.

    Here is my GX270 disk.

    A:\IBMBIO.COM
    A:\IBMDOS.COM
    A:\COMMAND.COM
    A:\MOUSE.COM
    A:\AUTOEXEC.BAT
    A:\CONFIG.SYS
    A:\GHOST
    A:\NET
    A:\MOUSE.INI
    A:\GHOST\GHOST.EXE
    A:\GHOST\GHOSTERR.TXT
    A:\NET\e1000.dos
    A:\NET\PROTMAN.DOS
    A:\NET\PROTMAN.EXE
    A:\NET\NETBIND.COM
    A:\NET\DIS_PKT.DOS
    A:\NET\PROTOCOL.INI
    A:\NET\E1000NT5.SYS

    CONFIG.SYS
    DEVICE=\net\protman.dos /I:\net
    DEVICE=\net\dis_pkt.dos
    DEVICE=\net\e1000.dos


    AUTOEXEC.BAT
    @echo off
    prompt $p$g
    \net\netbind.com
    MOUSE.COM
    cd \ghost
    echo Loading...
    GHOST.EXE -fni


    Protocol.ini
    [protman]
    drivername=PROTMAN$

    [pktdrv]
    drivername=PKTDRV$
    bindings=nic
    intvec=0x60
    chainvec=0x66

    [nic]
    drivername = E1000$

    Report Unresolved Customer Service Issues here
    I do not work for Dell. I too am a user.
    The forum is primarily user to user, with Dell employees moderating
    Contact USA Technical Support

    Get Support on Twitter @DellCaresPro

  • But it is working with other Dell server 2450 . So if that is the case how should i proceed.Please let me know.

    Thanks

  • You may be having a problem that is discussed in this Symantec Support Document. (Please follow the link below):

    Symantec Ghost Support Document ID 2003062409503825.

    PowerEdge 6650 has an onboard Broadcom NIC and the file names that you pasted seems to have the correct driver files specified for the Broadcom NIC. These are:

    A:\NET\B57.dos and A:\NET\B57.INS

    The Symantec KB article that I have included above has a resolution provided and instructions to Adding or modifying NIC templates in the Ghost Boot Wizard

    You may have to follow their instructions.

  • Im getting the same thing.. i tried different version of teh b57.dos driver.. old versions said card not found, new version loads the driver but gets requester service is not started.. gonna try sometihng else. let me know if you have a working boot disk... thanks
  • Well if you are booting it from floppy ..u just say N on the prompt while it is saying Requester is not found .Is it oK to start. then go to the directory NET and type net start basic  after that it will ask for the ghost user name and password.after that u can continue.

     

  • interesting.. ill try that.. I used barts boot disk @ http://www.nu2.nu/bootdisk/ with the broadcomm driver, except I got 8gb memory, I need to go into BIOS and enable OSBoot mode to get it working..  also I dropped in an intel card and have that working also..
  • Hi Tariq,

    I have a very similar issue.

    I have an inspiron 1100 with the Broadcom440 NIC inside.  I need to ghost the laptop across the network either to an image on a HD or to a set of DVDRs.

    In creating a ghost boot disk to map to a shared drive over the network on another PC, I went to the broadcom site and downloaded their NDIS2 driver for msdos. ("B44.dos")  This was used to make a ghost boot disk.

    Now that I have the driver name right :-)  ("drivername = B44$")

    When I boot up on that boot disk in the inspiron, I see the following

    ...Many things succeeding...

    including NTS$NTST2: Initialization succeeded

    ...

    IBM Netbind Version 2.1

    NTS$NTST2: NTS0101:

    WARNING: "Since the MAC driver does not support Loopback, the NTSNX driver may be necessary NTS$NTST2"

    Waiting for DHCP Server...

    IBM Dos Netbeui 3.00

    A:\>_

     

    I don't understand this warning.  I also don't understand what NTS$NTST2 is.

    Any suggestions for next steps in getting this to work?

     

    Thanks

    Greg.