- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 04-12-2013 02:44 AM
Hi,
We're having a few problems running inventory through Recon's Network Scanner (the error message is "Recon Failed" after installing the JAMF binary). So, it actually installs, but it can't send any information to the JSS.
We (myself and JAMF's support) have troubleshooted the problem for a while and know that the issue is being created due to the proxy (Websense) the machines have configured.
I see all traffic being passed and permitted through our proxy from the machines who are being inventoried.
Has anybody encountered this sort of situation before?
Is there a specific URL or IP that needs to be allowed on the proxy?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 04-19-2013 09:08 AM
The solution was a mix of:
Installing the appliance certificate on the client
Adding the JSS URL to the Websense SSL Decryption Bypass configuration
I'm figuring that when Recon is being processed on the client side, some components need to bypass the SSL Decryption and others require the appliance certificate to be installed in order to reach JSS in HTTPS.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 04-12-2013 04:01 AM
We use web sense, but our proxy is kerberized & we're not seeing issues like this.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 04-12-2013 07:00 AM
Have you also got MACs trying to communicate with a management platform on the cloud (Casper Suite)?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 04-12-2013 07:42 AM
we use websense and kerberised no problems
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 04-19-2013 09:08 AM
The solution was a mix of:
Installing the appliance certificate on the client
Adding the JSS URL to the Websense SSL Decryption Bypass configuration
I'm figuring that when Recon is being processed on the client side, some components need to bypass the SSL Decryption and others require the appliance certificate to be installed in order to reach JSS in HTTPS.
