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 shank
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- LIVEcommunity
- About shank
08-18-2015
8Posts
0Likes
0Solutions
Aug 18, 2015Last Visited
User
Activity
User
Profile
Latest posts by shank
| Subject | Views | Posted |
|---|---|---|
| 1356 | 05-27-2014 12:00 PM | |
| 1245 | 05-22-2014 10:45 AM | |
| 1245 | 05-22-2014 09:40 AM | |
| 3685 | 05-22-2014 09:22 AM | |
| 3685 | 05-22-2014 09:04 AM | |
| 3833 | 05-22-2014 08:32 AM | |
| 3832 | 05-22-2014 08:31 AM | |
| 4404 | 05-22-2014 06:34 AM |
User Badges
Community Statistics
| Member Since | 04-28-2014 07:40 AM |
| Date Last Visited | 08-18-2015 09:06 AM |
| Posts | 8 |
05-27-2014
12:00 PM
Hello, We are a bit confused. It appears that our ip address setting under Network>GlobalProtect>Portals must be set to either an IP Range or IP/Subnet, therefore it is not necessarily a single ip address (which is what I thought it should be). The part that is confusing us, is that the ip address/subnet setting for the portal web service is determining which users (by their ip address) can connect to the vpn web login. If the visitor's ip address does not fall into the same subnet, they are unable to launch the login website (it just times out). It seems that ALL ip addresses should be able to launch the vpn web login screen? example: If my portal web service ip address is (36.8.2.3/16) BOTH 36.8.5.12 AND 36.8.5.23 can launch the vpn login website. If my portal web service ip address is (36.8.2.3/24) 36.8.12.23 can launch the vpn login website, but, 36.12.2.3 can NOT launch the vpn login website? I am confused as to why this TARGET portal web service ip address impacts the visitors based on their ip address? thanks.
... View more
05-22-2014
10:45 AM
The screen comes up now, but, only after the following change of the GlobalProtect Gateway > Network Settings IP Address was: 12.13.14.15/32 now: 12.13.14.15/8 So 12. addresses can bring up the authentication screen in their browser.... still confused...
... View more
05-22-2014
09:22 AM
Security rule appears correct, Detail says app=ssl, NAT source=false, NAT Destination=true. I am actually going from a static computer to the static ip that I defined as the 'gateway web service', so, I am not sure why detail says NAT Destination= True. Flow 1, c2s, looks good. Flow 2 from the IP_Gateway_Web_Service back to the static computer seems ok, I can't tell what else is happening?
... View more
05-22-2014
09:04 AM
We have a L3_Untrust TO L3_Untrust rule that has an action of ALLOW and currently it is any from address/user to a destination of VPN_IncomingAddress. I allowed applications of ssl and web-browsing and during this test phase, this policy is the #1 policy. When we monitor this we do see communication to port 443, with an action of allow. I do see a lot of 0 byte entries as well as 60 byte entries.
... View more
05-22-2014
08:32 AM
Also, I get 'unauthorized' when I try to view the first link you provided. Thanks!
... View more
05-22-2014
06:34 AM
What basic steps have to be complete to allow a remote user to enter an ip address in their browser and get the ssl vpn authentication screen? We currently get an eventual timeout when we try to connect from a browser. We followed the basic GlobalProtect setup steps, but, just wondering if there is something 'dumb' that we are missing. Thanks!
... View more
Contact Me
| Online Status |
Offline
|
| Date Last Visited |
08-18-2015
09:06 AM
|
Latest Tags
No tags yet
LEGAL NOTICES
Copyright 2007 - 2023 - Palo Alto Networks