Default password not working admin / admin

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Please sign in to see details of an important advisory in our Customer Advisories area.

Default password not working admin / admin

L1 Bithead

cccccc.PNGiso version = PA-VM-ESX-10.0.4.vm_eval
trying root / root  

and admin/admin 

showing this message 

pls help me

13 REPLIES 13

Cyber Elite
Cyber Elite

Hello @MAlif

 

thanks for the post.

 

You will have to wait until: "login" is displayed. With PA-HDF firewall is not accepting credentials yet. Details are in KB:

https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000CloQCAS

 

Kind Regards

Pavel

Help the community: Like helpful comments and mark solutions.

222.PNG

almost passing 2hours but staill same. cloud u tell me pls what is the issues.. not coming login promopt 

Cyber Elite
Cyber Elite

I am sorry for late response @MAlif

 

2 hours is far too long. Something is not right.

 

Could you try to attach serial port to VM? Could you also de-select floppy/optical disk from boot menu if it is there. 

After this, try to boot PA VM again.

 

Kind Regards

Pavel 

Help the community: Like helpful comments and mark solutions.

Hi Pavel,

 

I´m having exactly this same issue. VM booted and waited for login to be prompted but with no success.

AlexandreSousa_0-1684254674964.png

 

It almost seems like the username database or something is missing.

 

Any help?

Regards,

Alex

L1 Bithead

Hello @MAlif 

 

This appears to be the same issue that @TodorPetkov and I were experiencing. I believe the below steps will get you to the desrired "PA-VM login:" prompt:

 

I had the same issue when installing trial VM in VMware ESXi. I understand that there are 3 "login" prompts:

 

vm login:

PA-HDF login:

PA-VM login:

 

Ultimately you want to get the "PA-VM login" prompt to log in with the admin/admin credentials. However, it does not go past the first prompt when installing in VMware ESXi. The workaround I tried and was able to get working was by stopping the VM bootup process by typing "maint" immediately after startup. This has to be done rather quick as the VM boots up fast.

 

If successful, you must give it time as it is booting into Maintenance Mode.

Spiterman_0-1685148081879.jpeg

 

Once in Maintenance Mode, select "Continue --> Disk Image --> Reinstall 10.x.x.

Spiterman_1-1685148081850.png

 

Spiterman_2-1685148081852.png

 

 

After some time it will display a successful result. Scroll all the way down to select Reboot option. After this you should be able to get the "PA-VM login:" prompt and you can proceed to log in with the default credentials.

 

Also, make sure to first add enough Network Adapters to your VM to connect to your virtual environment and to assign different Zones to those interfaces. Basically every NA will correspond to an interface on the FW.

 

Hope this helps!

Hello,

 

unfortunately even after reset I have the same error - Sysd is unavailable. I tried to run the KVM flavour as well, but it's the same there.

 

Regards

Hello,

 

Did you do a Factory reset or did you reinstall the disk image?

 

The factory reset alone will not work unless the disk image is reinstalled.

 

Regards 

Hello,

 

it was reinstall, yes:

 

TodorPetkov_0-1685387148304.png

 

Are you still getting the "PA-HDF login:" prompt or did it change to "PA-VM login:"?

 

Also, the reinstall disk image only worked for me when I spun up the VM in ESXi. Unfortunately, the same procedure didn't work on the KVM image.

 

Regards

L1 Bithead

I was getting this prompt even before the reset:

TodorPetkov_0-1685396648178.png

 

After typing "admin", I am getting this message. Same is with brand new VM and after reinstall:

TodorPetkov_1-1685396774169.png

That was the exact message I was getting when I installed my the PA-VM in ESXi 6.7. The log in prompt must be "PA-VM login" in order to gain access into the VM. I was able to get the 3rd login prompt after reinstalling the disk image.

L4 Transporter

That can sometimes happen if there is a resource issue when building, the image (if I remember rightly) configures 5.5Gb mem as default, when the firewall really needs 6Gb they start to behave then!

PCCSA PCNSA PCNSE PCSAE

Thanks a lot ! You saved it ! 😊

 

  • 9641 Views
  • 13 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!