UNSOLVED

Sammyc53

updated

20 years ago

S

Sammyc53

52 Posts

0

30916

April 20th, 2006 20:00

Error with Re-install Console - Can't create NASuser.

I have tried this on two XP Pro sp2 machines. Must I use Server 2003?

I have admin rights.

Thanks.
  • Sammyc53

    52 Posts

    320

    0

    Posted April 20th, 2006 20:00

    Nope, none of those things worked.
  • Sammyc53

    52 Posts

    320

    0

    Posted April 20th, 2006 20:00

    I'll try this. Just say it:
    http://forums.us.dell.com/supportforums/board/message?board.id=pv_nas&message.id=1966&query.id=40394#M1966
  • Storagetalk

    221 Posts

    320

    0

    Posted April 21st, 2006 14:00

    Make sure the system is NOT sitting on domain settings.  It has to be in workgroup settings and you must be an admin.

    Also, before you re-run the console make sure the previous NASUser, NASGroup and NASTemp items are deleted.

    If all else fails...do everything manually:

    When you run the Reinstallation Console, the installation process will perform the following tasks on your Windows 200x/XP system:

    • Create a local group called NASGroup
    • Create a local user called NASUser
    • Place the user NASUser into the group NASGroup
    • Create a directory on a specified hard drive called NAStemp
    • Share the NAStemp directory as NASShare (with permissions of Everyone with Full Control AND the NASUser account)
    • Copy the Windows Storage Server 2003 operating system from the three CDs into the NAStemp directory
    • Boot from the prepped USB key
  • Sammyc53

    52 Posts

    320

    0

    Posted April 21st, 2006 15:00

    Thanks again. I tried most of those already.

    I have the share and user created. I didn't realize that the machine I was usign was actually once part of the domian.

    Now, I can't the usb boot to connect to the share. I tried dhcp and hard code.

    Time will tell,

    I will post here if I need more help.

    Thanks.

    Sam
  • Sammyc53

    52 Posts

    320

    0

    Posted April 21st, 2006 17:00

    I even tried setting the guest password to powervault. (found that in another thread).

    I can connect to \\pcname\nasshare just fine from other machine using the same credentials.

    Message Edited by Sammyc53 on 04-21-200601:51 PM

  • Storagetalk

    221 Posts

    320

    0

    Posted April 21st, 2006 17:00

    This means your client system is denying access to the share.  Client issue.  I would go to make sure simple file sharing is disabled...

    To reinstall a PowerVault 745N, disable simple file sharing on a Microsoft® Windows® XP system that is not part of a domain by performing the following steps.

    1. Double-click My Computer.
      My Computer opens.
    2. Select Tools menu, click Folder Options, and click the View tab.
      The View tab of Folder Options opens.
    3. Clear the Use simple file sharing (Recommended) check box.  

      NOTE: In Windows XP with no Service Pack installed, the Use Simple File Sharing (Recommended) option is in the Advanced Settings section.
    Click OK.
    Simple file sharing is disabled.

    NOTE: The change takes effect immediately.

     

    Try again.

  • Storagetalk

    221 Posts

    320

    0

    Posted April 21st, 2006 17:00

    Sorry if I'm missing something....
     
    What's the problem you have now?  I assume you got past the NASUser issue.
  • Sammyc53

    52 Posts

    320

    0

    Posted April 21st, 2006 17:00

    Still no avail. Tried everything!!!!!!!!!!!!!

    What gives!?!?!?! What a weird setup system.

    What's wrong with CDs or DVDs? I would have been done ages ago!
  • Sammyc53

    52 Posts

    320

    0

    Posted April 21st, 2006 17:00

    sorry. The nas, now with the usb key as boot device, says:

    "Unabel to map share "\\pcname\NASShare" with
    Account "NASUser" and password "powervault"

    Installation Aborted.
  • Storagetalk

    221 Posts

    112

    0

    Posted April 21st, 2006 17:00

    Oh, I didn't know that 2003 didn't have an option for 'simple file shares'.

    Well that error means your client isn't allowing access...it's blocking the script from touching the share.  Hmmmmmmmmmm