RSA giving ERROR: Unable to mount shares at \\10.X.X.X\peinst

I've setup RSA's before and they worked fine - but now we've switched them to new boxes. VM is hosted with virtual box. They are linked correctly, but when I use KBE Manipulator to create a new RSA KBE, I get this error:


System error 86 has occured

The specified network password is not correct.

ERROR: Unable to mount shares at \\X.X.X.X\peinst


Any ideas? Do I need to update drivers for RSA's too? It boots fine on our main K2000 box. 

0 Comments   [ + ] Show comments

Answers (3)

Answer Summary:
Posted by: dugullett 9 years ago
Red Belt

Rebuild your boot environment.

Posted by: SMal.tmcc 9 years ago
Red Belt

If the X's are just for our benefit:

Test the your login for this mount by booting with a pxe and on the main screen go into recovery, command prompt and try to manually map this share with the user and password and see what happens.

If the X' are real do what dugullett says

  • If you just recently upgraded to 3.4 the shares now use security. - SMal.tmcc 9 years ago
  • Sorry - yes, the X's is an actual IP address. I just put X's because I didn't remember the IP address off hand.

    I'm going to sound like a complete noob here - but what commands should I run to map the share?

    I thought the default password as "admin", which is why I did used KBE manipulator to do it and it never asked for any passwords other than my main K2000 box? - sfigg 9 years ago
Posted by: SMal.tmcc 9 years ago
Red Belt

to test the share

do a "net use" and make sure there are no current connections to the RSA, then to make a connection:

net use x: \\\petemp password /user:admin

password is what you set here


admin if you never did set one.

  • Note:
    if your boot environments for the RSA were created prior to 3.4 they have no password in the startnet.cmd on the map command compiled in them. - SMal.tmcc 9 years ago
  • The RSA is on 3.3.X, however the main K2000 is on 3.4.X

    If I do the net use command without a password, it works - but if I use the password set in the driver restore box in the k2000, it gives the same password error. I've made the RSA how I did the other ones - with the KBE Manipulator, but it's not working? Am I missing something? - sfigg 9 years ago
  • Update the RSA and rebuild your boot environment.

    Are you sure you entered a password under "step 2" using the manipulator? - dugullett 9 years ago
  • Yes, I entered the password under step. I try to update the RSA, and it says no updates area available. - sfigg 9 years ago
  • Sorry I was looking at the RSA for the update, which it says is not available. I just tried forcing an update from the K2000, so we'll see if this fixes it. - sfigg 9 years ago
    • After the update make sure to rebuild the KBE. - dugullett 9 years ago
  • Makes sense with your problem 3.3 does not require a p/w on the petemp and 3.4 does. You want all your 2000's on the same version because of the major changes between 3.3 and 3.4. If you cannot get them all to auto upgrade open a ticket with Kace they can give you a download of the update which you can upload to each RSA and force run it. - SMal.tmcc 9 years ago
  • I just setup two k2000 RSA's and am having trouble getting the USB pxe boot drives to work. I used KBE Manipulator to create the KBE that points to the IP address of the RSA. When it boots it says

    System error 86 has occured

    The specified network password is not correct.

    ERROR: Unable to mount shares at \\X.X.X.X\peinst

    I can mount the share of the RSA, but it uses the default password of 'admin'. I have changed the driver/restore share password on the main k2000 box and am wondering how I can get the RSA driver/restore share password to be the same or how to get the KBE pxe boot stick to use the default 'admin' password.

    Thanks! - sburkey2 8 years ago
    • Just ran into this issue, you have to sync the RSA to the K2000 once so the file share can sync the password with the K2000. - pitterchi 8 years ago
      • I was able to resolve my issue by changing my share password to something that did not have special characters in it. (@, #, $, etc.) Then when I sync'd the RSA everything copied over and I was able to PXE boot to the RSA. Thanks! - sburkey2 8 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


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