/build/static/layout/Breadcrumb_cap_w.png

Error trying to boot to KBE - The password is invalid for \\x.x.x.x.\peinst.

Trying to boot to KBE to image a machine and now get this error message: The password is invalid for  \\x.x.x.x.\peinst.  I haven't changed anything on the system in relation to passwords or settings.  I did upgrade the server a couple weeks ago but have imaged a few machines since then with no issues - until now.  I understand the peinst file is hidden and read-only.  Has anyone else seen this?  I'm the only working administrator for the KBOX so I'm sure no one else has changed anything.


0 Comments   [ + ] Show comments

Answers (5)

Answer Summary:
Ensure that you are using the 3.4 media manager, create a new KBE with the proper driver/restore share password (also set in General Settings) in the Host Login Password field, and set your new KBE as the default KBE.
Posted by: warmep 12 years ago
Third Degree Green Belt
3

Were you using boot actions? It's possible that the wrong KBE is set as the defaults. You can change the defaults in Settings and Maintenance > General Settings > Default K2000 Boot Environments.

Otherwise, ensure that you are using the 3.4 media manager, create a new KBE with the proper driver/restore share password (also set in General Settings) in the Host Login Password field, and set your new KBE as the default KBE. 


Comments:
  • That seems to work for x86. Now building the x64 KBE. Thanks. - rjobe 12 years ago
  • I had this error and what mpace said is correct.

    however, now I have the problem that when one of our machines in our remote offices tries to load anything from our RSAs we are met with the error

    'the specified network password is not correct'.

    only on the Remote boxes. I upgraded all RSAs to the same version and the KBE replicated successfully. - dogfish182 12 years ago
Posted by: mpace 12 years ago
Red Belt
1

After upgrading to 3.4 you will need to download and install the new Media Manager from the K2000 Home page (second link, upper left corner). With the new Media Manager, create a new KBE and use that to boot to the K2. Notice that you now have a "Host Login Password" field on the upper right of the Media Manager. This needs to be filled in with the correct password for the drivers/restore samba shares (not the password you use to login to the Web UI). 


Comments:
  • Can you give the link address for the K2000 home page? I can't find it or anything with a Media Manger download link. - rjobe 12 years ago
  • Got it! You were referring to my K2000 system main page. - rjobe 12 years ago
    • Yes, sorry. The page that is first displayed when you log in or when you click on the Home module in the navigation bar of the K2. - mpace 12 years ago
Posted by: omallem 12 years ago
Senior Yellow Belt
0

Although maybe not the best answer.. but I have seen an alternative way around this problem.  When loading the KBE and it stops to ask you to enter the correct username and password... enter the hostname of your Kbox in front of your username e.g.,   kboxhostname\username

Posted by: Aaron Cool 12 years ago
Red Belt
0

is this an old KBE that you try to deploy that has been around before you upgrade to 3.4? 

Posted by: rjobe 12 years ago
Fourth Degree Green Belt
-1

I have tried the new KBE's (KBE_x86_33 / 34) that were installed as part of the update but I get the same thing.  I've updated every password I know of in the system also but still no luck.


Comments:
  • Have you try your network permission on the Samba Share? - Aaron Cool 12 years ago

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ