Palo blocks on login step

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Palo blocks on login step

L1 Bithead

my PA-410 remains stuck on the login. It refuses my password and prevents me from doing the configurations.

6 REPLIES 6

Cyber Elite
Cyber Elite

Is it new or existing setup?

If existing is traffic flowing as expected but management part has issues?

 

Enterprise Architect, Security @ Cloud Carib Ltd
Palo Alto Networks certified from 2011

L1 Bithead

Is this an existing configuration? In addition, existing traffic is not flowing as expected.

Cyber Elite
Cyber Elite

Are you connected over console cable?

Any errors on the console screen?

If traffic is not flowing anyway can you reboot firewall?

Enterprise Architect, Security @ Cloud Carib Ltd
Palo Alto Networks certified from 2011

PA-410 login: admin
Password:
Login incorrect

PA-410 login: admin
Password:
Last login: Fri May 26 14:43:24 on ttyS0
Enter old password :
Enter new password :
Confirm password :
Password changed

 


Number of failed attempts since last successful login: 1

There have been failed attempted logins from your username, which could mean someone is trying to brute-force your login. If t his is not expected, consider contacting your system administrator.


Avertissement : Votre appareil est toujours configuré avec les informations d’identification de compte administrateur par défaut. Veuillez changer votre mot de passe avant le départ.
admin@PA-410> ping hôte 192.168.1.1 PING 192.168.1.1 (192.168.1.1
) 56(84) octets de données.
64 octets à partir de 192.168.1.1 : icmp_seq=1 ttl=64 temps=0,080 ms 64 octets à partir de 192.168.1.1 : icmp_seq=2 ttl=64 temps=0,089 ms 64 octets à partir de 192.168.1.1 : icmp_seq=3 ttl=64 temps=0,086 ms 64 octets à partir de 192.168.1.1 : icmp_seq=4 ttl=64 temps=0,098 ms 64 octets à partir de 192.168.1.1 : icmp_seq=5 ttl=64 temps=0,267 ms




64 octets à partir de 192.168.1.1 : icmp_seq=6 ttl=64 temps=0.122 ms 64 octets à partir de 192.168.1.1: icmp_seq=7 ttl=64 temps=0.060 ms 64 octets à partir de 192.168.1.1: icmp_seq=8 ttl=64 temps=0.083 ms 64 octets à partir de 192.168.1.1: icmp_seq=9 ttl=64 temps=0.076 ms



64 octets à partir de 192.168.1.1: icmp_seq=10 ttl=64 temps=0.115 ms
^C
--- 192.168.1.1 statistiques ping ---
10 paquets transmis, 10 reçus, 0% de perte de paquets, temps 9194ms
rtt min/avg/max/mdev = 0,060/0,107/0,267/0,057 ms
admin@PA-410> ping hôte 172.16.100.2 PING 172.16.100.2 (172.16.100.2
) 56(84) octets de données.
À partir de 192.168.1.1 icmp_seq=1 hôte de destination inaccessible à partir de 192.168.1.1 icmp_seq=2 hôte de destination inaccessible à partir de 192.168.1.1 icmp_seq=3 hôte de destination inaccessible à partir de 192.168.1.1 icmp_seq=4 hôte de destination inaccessible à partir de 192.168.1.1 icmp_seq=5 hôte de destination inaccessible




à partir de 192.168.1.1 icmp_seq=6 hôte de destination inaccessible
^C
--- 172.16.100.2 statistiques ping ---
7 paquets transmis, 0 reçu, +6 erreurs, 100% de perte de paquets, temps 6157ms
pipe 4
admin@PA-410>

Cyber Elite
Cyber Elite

Seems issue is solved?

Enterprise Architect, Security @ Cloud Carib Ltd
Palo Alto Networks certified from 2011

Cyber Elite
Cyber Elite

@PA-410,

It seems like you simply didn't wait for the device to finish booting. It's a bit deceptive since it'll give you a login prompt prior to the device actually being booted enough to login, but that's a normal thing whenever you restart a PAN firewall. It generally won't take that long to complete and become accessible again, especially on a newer 410, but there is a delay that's expected. 

  • 1601 Views
  • 6 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!