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 rlawsha
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- LIVEcommunity
- About rlawsha
07-10-2020
4Posts
2Likes
0Solutions
Jul 10, 2020Last Visited
User
Activity
User
Profile
Latest posts by rlawsha
| Subject | Views | Posted |
|---|---|---|
| 1838 | 08-07-2014 11:59 AM | |
| 1839 | 08-07-2014 05:21 AM | |
| 1880 | 07-30-2014 04:52 PM | |
| 1306 | 11-25-2013 06:02 AM |
My Liked Posts
| Subject | Likes | Posted |
|---|---|---|
| 2 Likes | 08-07-2014 11:59 AM |
User Badges
Community Statistics
| Member Since | 07-09-2012 03:00 PM |
| Date Last Visited | 07-10-2020 09:37 AM |
| Posts | 4 |
| Total Likes Received | 2 |
08-07-2014
11:59 AM
2 Kudos
The problem seems to be caused when a workstation has multiple ipv6 temp addresses. To test this I did this on my workstation: netsh interface ipv6 set global randomizeidentifiers=disabled netsh interface ipv6 set privacy state=disabled reboot Now the PA box correctly identifies me I will have to test this long term but so far it has worked for me
... View more
08-07-2014
05:21 AM
I checked the 6 steps in the article you provided: 1 - make sure ipv6 is enabled - okay 2 - check ipv6 default route - okay 3 - ping via ipv6 from workstation to firewall internal interface, host name and IP address - okay 4 - ping via ipv6 from firewall external interface to external host - NOT OKAY 5 - ping via ipv6 from firewall internal interface to external host - okay So this is weird, workstations have no trouble with ipv6, they can visit sites, ping sites and all that. The problem is, agentless user-id is inconsistent with ipv6 clients. Not sure why step 4 from above will not work.
... View more
07-30-2014
04:52 PM
We are using an agentless user id system with four domain controllers. IPv4 and IPv6 is used inside and outside our organization. The PA box fails to identify users that run IPv6. Turning off IPv6 on the Windows clients fixes the problem. The problem is intermittent so it is hard to track down. Running 6.0.3 software.
... View more
Labels:
- Labels:
-
User-ID
11-25-2013
06:02 AM
We have a PA5020 and recently enabled IPv6 throughout our network. We have been experiencing extremely slow internet connections and timeouts until we removed IPv6 from the inside and outside PA box Ethernet interfaces. Our ISP is Comcast and we have a one gig fiber directly in to our data center to the internet on that line. The Comcast line connects directly to our Palo Alto. Running the 5.0.9 OS on the PA box and really not doing anything fancy with it, no load balancing or HA. Removing IPv6 from the PA box and all is fine, add IPv6 and everything crawls or times out. Update: After the applied the 6.01 software update this problem went away....
... View more
- Tags:
- ipv6
Labels:
- Labels:
-
Configuration
-
Networking
-
Troubleshooting
Contact Me
| Online Status |
Offline
|
| Date Last Visited |
07-10-2020
09:37 AM
|
Latest Tags
No tags yet
LEGAL NOTICES
Copyright 2007 - 2023 - Palo Alto Networks