Ghost Solution Suite

 View Only
  • 1.  Error 87: A parameter is not valid

    Posted Feb 10, 2009 11:41 AM

    I'm using GSS 2.0 with a drive-mapping boot disk to restore an image that is stored on a server. Upon booting, I receive the following message shortly after the IP address is renewed with the DHCP server:

     

    Error 87: A parameter is not valid

     

    The only thing I can think of that has changed is that our DHCP scope options no longer include a WINS server, and NetBIOS is disabled (we're removing these services from out network environment). Is that the cause of the error above? If so, is there any way I can get around this in GSS 2.0? If not, is there a new version that does not require WINS/NetBIOS?

     

    Thanks



  • 2.  RE: Error 87: A parameter is not valid

    Posted Feb 10, 2009 04:25 PM

    Hi crhosu,

     

    what is the actual net command you are using? it would be helpful to see the actual command that you are using since Error 87 can be caused by different issues.

     

    if the problem is with the Wins/netbios, you should be able to use ip address rather than machine to access the share.

     

    or

     

    you can use the file called lmhost. it has static entries which maps ip address with netbios name.

    if your machine has dynamic ip address, it might not be the best option though..

     

    regards,

    James Lee



  • 3.  RE: Error 87: A parameter is not valid

    Posted Feb 10, 2009 04:57 PM

    James,

     

    Here's the autoexec.bat file from the floppy boot disk. It's worked fine until I removed WINS/NetBIOS from the scope options of DHCP, but I have no evidence that that's the cause.

    ------------------------

     

    @ECHO OFF
    SET TZ=GHO+05:00
    SET PATH=\NET\;\;j:\;%PATH%;
    SET TEMP=\
    SET TCPHELP=\NET
    SET ETCDIR=\NET
    rem MOUSE.COM

    REM this configures where ghost.exe will look for the wattcp.cfg file
    set wattcp=a:\net\wattcp.cfg

    \NET\NET START
    \NET\NET.EXE USE J: \\server1.domain.edu\images

    mouse

    ghost.exe @switches.txt

    -----------------------

     

     



  • 4.  RE: Error 87: A parameter is not valid

    Posted Feb 10, 2009 05:03 PM

    Hi crhosu,

     

    thanks for the autoexec.bat file.

    I noticed that there is no user logon specified.

    are you manually type in user name and password for the share?

    also since you are using hte dns entry, it could be the problem with Wins/netbios like you mentioned.

    can you try with ip address instead of server1.domain.edu? does it make any difference?

     

    regards,

    James Lee



  • 5.  RE: Error 87: A parameter is not valid

    Posted Feb 11, 2009 11:01 AM

    James,

     

    Yes, I manually type in a username and password.

     

    I substituted the server's IP address for the hostname, but that had no effect. I still get the same error message at the same part of the process.

     

    Any other suggetions would be great. Moving back to WINS/NetBIOS doesn't seem to be a viable alternative on my network.



  • 6.  RE: Error 87: A parameter is not valid

    Posted Feb 11, 2009 10:26 PM

    Hi crhosu,

     

    can you try step by step mode? you can do this by press F8 during dos boot up.

    execute each step and see where exactly the error comes out.

    if ip address is not working either, it might not be the problem with netbios.

    it could be something else as well.

    so it will be useful to identify which line it is exactly failing.

     

    regards,

    James Lee



  • 7.  RE: Error 87: A parameter is not valid
    Best Answer

    Posted Feb 12, 2009 08:04 AM

    Here is what I was getting:

     

    IBM DOS NETBEUI 3.00

    Error 87: A parameter is not valid.

    \net\net.exe use J: \\server1....

     

    The strange thing is, I re-built the boot disk, tried it again, and it started working. I have no clue what the problem was. Strange thing was, I always keep three copies of each boot disk, and all three were giving me the same problem.

     

    We have a WINS server running on this subnet, but the DHCP scope options specifically disable NetBIOS over TCP/IP. Since the boot disks are using DHCP for all IP settings, it seems WINS and NetBIOS aren't necessary for Ghost.

     

    Thanks for your help.