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 smithp
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- LIVEcommunity
- About smithp
05-16-2017
1Post
0Likes
0Solutions
May 16, 2017Last Visited
User
Activity
User
Profile
Latest posts by smithp
| Subject | Views | Posted |
|---|---|---|
| 1332 | 02-04-2013 10:46 AM |
User Badges
Community Statistics
| Member Since | 11-26-2012 12:48 PM |
| Date Last Visited | 05-16-2017 03:27 PM |
| Posts | 1 |
02-04-2013
10:46 AM
We have our PA-500 setup on our company's public network. This network is used by employee's personal machines and clients machines when they come into our office. We have run into a few situations that we can see someone is most likely infected as the machine has been profiled by the PA-500 as transmitting threat traffic. The problem is we only have an IP address of the machine that is doing the talking. Wondering if there is a way to get things like hostname, OS and version or any other easily identifiable information to find the infected machine. Thanks
... View more
- Tags:
- dhcp
Labels:
- Labels:
-
Configuration
-
Networking
Contact Me
| Online Status |
Offline
|
| Date Last Visited |
05-16-2017
03:27 PM
|
Latest Tags
No tags yet
LEGAL NOTICES
Copyright 2007 - 2023 - Palo Alto Networks