This website uses cookies essential to its operation, for analytics, and for personalized content. By continuing to browse this site, you acknowledge the use of cookies.
For details on cookie usage on our site, read our Privacy Policy
For details on cookie usage on our site, read our Privacy Policy
About ArnelManalo
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- LIVEcommunity
- About ArnelManalo
08-18-2015
2Posts
0Likes
0Solutions
Aug 18, 2015Last Visited
User
Activity
User
Profile
Latest posts by ArnelManalo
| Subject | Views | Posted |
|---|---|---|
| 6696 | 07-29-2013 02:55 PM | |
| 6803 | 07-29-2013 02:40 PM |
Posts I Liked
| Subject | Likes | Author | Latest Post |
|---|---|---|---|
| 2 Likes | |||
| 2 Likes |
User Badges
Community Statistics
| Member Since | 07-16-2013 03:24 PM |
| Date Last Visited | 08-18-2015 09:07 AM |
| Posts | 2 |
07-29-2013
02:55 PM
Hi John, Thanks for the info. That would explain to me why it shows up as not-applicable when blocked. However, I suppose I am still curious as to why it is not seeing it as MS-RDP and being allowed through... Thanks, Arnel
... View more
07-29-2013
02:40 PM
Hi, I have a few rules that only permit ms-rdp and t.120. A new rule was implemented last week that permits ms-rdp and t.120, just different source addresses. The other rule can see the ms-rdp application but for the new rule, it shows up as application not-applicable and the traffic is being blocked. I looked around here for some answers and have found that something before in the rule, the zone/source, etc. could be causing the tcp handshake not complete, thus not allowing the PA to pick up the application. However, the other rule which is working has the same zones set up, just the source address is different (same subnet). So I do not think it is anything to the left in the rule and the other rule is just above it so I do not think that is it either. Just looking for some thoughts/ideas. Thanks!
... View more
Labels:
- Labels:
-
Configuration
-
Troubleshooting
LEGAL NOTICES
Copyright 2007 - 2023 - Palo Alto Networks