how to change the FW administration default SSH port number ?

Hello,

I want to change the default SSH port number for the firewall administration?

any ideas ?

Non logging issue

OK a little background first I'm running 4.1 on a 5050 pair in A/P.  I have a server that is trying to do 80 and 443 out to a specific address and we have some logging wierdness going on.  If we don't have a rule in place allowing the traffic it will

connectivity issue when firewall HA failover

Did anyone encounter such issue?

We noticed that whenever the firewall triggered a failover (FW1 to FW2).

external services seem to be disrupted.

eg1 :Gomes monitoring informed of connection/performance issues (though we test from some countries to be

SSH2 Login Attempt - ID 31914

Name:SSH2 Login AttemptID:31914Severity:Description:This alert indicates a login attempt against the target SSH server. If there are too many login attempts, then it may means an attack is try to brute-force user name and password.

I don't know who wr

connection interrupt

Hi,

An internal application is used for databese.It's default port is 5520

when we saw this behaviour we wrote an application override rule for that tcp port and named a new application.

after that we saw issue behaviour not changed(user is disconnectet

Destination NAT question

In this document is described how the NAT function at the Palo Alto.

https://live.paloaltonetworks.com/docs/DOC-1517

Has anything changed in the 5, in contrast to 4.1er?

So far, the destination NAT zone was generally on the incoming interface as the sou

Panorama 5.1.0 upgrade fails and VM cannot boot on VMware

Hi,

I have upgraded my Panorama residing on VMware using the web interface to 5.1.0 but it is not able boot now.

It is on VMware and it is continuously asking for a login with different names and after a while it reboots.

Any ideas?

GlobalProtect clients logged as PA MGMT

Looking through my logs today and I noticed that connections initiated by clients using GlobalProtect are being logged as sourcing from the PA management interface. Is this expected/intended behavior?  Shouldn't the log show the clients IP address?