so, I'm working on our mac pilot testing at our offices in the Asia region, and I'm running into weird problems accessing the JSS url from the test boxes that have been built over there. Basically, many macs in that region are telling me that the jss url is not responding when trying to access it from Safari or using the jamf checkJSSConnection command. However, Firefox can access the URL just fine at the same time as the jamf binary and safari are failing.
We're using the same image as we've used in our other regions, and we have not seen this issue in any other regions, either.
Any ideas?
Question
weird issue with some clients not resolving the JSS URL
+19
+19successful- both the IP address and the hostname resolve as expected. traceroutes also succeed while safari and the jamf binary are failing.
+24Proxy settings? If memory serves me, don't the jamf binary and Safari both honor any proxy settings set up in Network > Proxies, but Firefox does not?
+19well, that definitely appears to be part of it. this is all on the corporate WAN, so we shouldn't be going through the proxy for this traffic, but wireshark revealed that firefox was using the proxy and successfully receiving data back from the JSS, while everything else was bypassing it and receiving nothing back- we do set up the proxy to bypass for internal hostnames.
So, removing the proxy bypass setting got telnet, safari, and the jamf checkJSSConnection command working again, but the test machines still don't seem to be able to communicate with the jss fully . . . jamf policy commands result in an unable to contact the JSS error. jamf enroll commands give the same. Running a quickadd package results in a claim that the JSS is not responding. So, progress but not a full solution.
Also, why does firefox ignore the proxy bypass settings? It is configured to use the system proxy settings, so I would have expected it to behave the same as safari.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.