![cannot connect to the jamf pro server try connecting again cannot connect to the jamf pro server try connecting again](https://venturebeat.com/wp-content/uploads/2017/12/echospot-3.jpg)
- #CANNOT CONNECT TO THE JAMF PRO SERVER TRY CONNECTING AGAIN PATCH#
- #CANNOT CONNECT TO THE JAMF PRO SERVER TRY CONNECTING AGAIN FULL#
- #CANNOT CONNECT TO THE JAMF PRO SERVER TRY CONNECTING AGAIN MAC#
But as a pleasant surprise, for that specific Secondary site with the re-configured WAN accelerator, it had after 2 days still not stopped working. When they had re-configured one of the WAN accelerators and I had restart the SMS_Executive service once again, it worked (as expected of course, since it worked every time after a service restart). Could they have something to do with it? I talked to our network team and asked them to let my Primary site to Secondary site traffic pass-through the WAN accelerator.
#CANNOT CONNECT TO THE JAMF PRO SERVER TRY CONNECTING AGAIN MAC#
It hit me that we’re using WAN accelerators on our local office locations. mobile device management (Apple MDM) protocol is a framework that allows Jamf to help you manage devices at scale The Mac doesnt have a device manager. This was really giving me a headache, because I couldn’t really understand why it wouldn’t work.Īt this point I started to see a pattern for my problem. Every time I initiated a new session to the share by either browsing or restarting the SMS_Executive service, it worked but then stopped working after a while.
![cannot connect to the jamf pro server try connecting again cannot connect to the jamf pro server try connecting again](https://forum.cfx.re/uploads/default/optimized/4X/4/3/a/43a9a851b8ec1b1d2e1b46e4176c9bca3c67f2ec_2_500x500.png)
Based off another script I've seen somewhere but I can't, for the life of me, remember who the original author was. When I opened up Windows Explorer and tried browsing to the \\\SMS_SITE share, it worked out just fine. That way we don't get the pop-up for connection attempt/failure if a staff member is off the network (eg. That didn’t do the trick, the problem still occurred intermittently. Support says they are escalating - at this time Self Service is not.
#CANNOT CONNECT TO THE JAMF PRO SERVER TRY CONNECTING AGAIN PATCH#
As part of this weeks April 2021 Patch Tuesday, Microsoft In Windows 10. I have checked the firewall and tried at home and get the same result. So, when activated, Globalprotect obstructs all network connections. Then when I open the app after spinning for 5 minutes I get the 'Unable to connect to server'.
#CANNOT CONNECT TO THE JAMF PRO SERVER TRY CONNECTING AGAIN FULL#
I added the Primary site computer account explicitly with Full Permissions for troubleshooting purposes. The only way I can get the Self Service App to load is wipe the device. There I found out that the SMS_SiteToSiteConnection_ group was indeed there. But why would it work after a restart of the SMS_Executive service, and then suddenly stop working? So I started looking into the permissions on C:\Program Files\Microsoft Configuration Manager\inboxes\despooler.box\receive to double check everything was in order. My first suspicion was that the Primary site account was not added to the local group SMS_SiteToSiteConnection_. Okey, problem solved? No, it would after a random time stop to work again, and the same error appeared. Suddenly all queued up sending packages started to go out to the Secondary sites. Cannot connect to server at remote site, won't try send requests going to site for an hour or until there are no active send requests.Įvery time I saw the problem, I tried to restart the SMS_Executive service on the Primary site. There is no existing connection, Win32 error = 53Įrror during connection to \\\SMS_SITE (53). When I looked in the sender.log I found the following: A few weeks ago I saw that applications and packages was intermittently not being pushed over to our Secondary sites.