OK, team, I'm baffled here. Last night, a firewall issue restricted all devices from connecting to Traveler (14.0 FP1 WIN). Once resolved, 80% of the devices have synced but others (mostly iPhones) haven't since yesterday. Nothing changed on server or clients, any ideas? The users are getting a cannot connect to server error on devices. The server is clearly up and servicing most users.
I did reset one user (now state is "Not registered") but he cannot complete setup. He was able to successfully (on mobile device + desktop) login to traveler.test.com and status was 100%, able to generate profile (and download .mobileconfig)... but received a "The account cannot be verified" DAErrorDomain Error:0 and Cannot Get Mail due to server being unreachable (even though he logged in to get profile...) during install. I looked up the DADomain error and it mentions possible HTTP OPTIONS not being allowed (but it is enabled) then mentions firewall having issue with OPTIONS?!? Doesn't make sense, honestly, the other 80% is working.
In the Traveler DB, the working users show "Online" state, while non-working show "Offline." Direct connect... nothing has changed. Devices access via port 443 and server accesses mail files via NRPC (1352).
Thanks in advance. This one's causing issues, as you can imagine.
Update:: I'm still reviewing the logs. I see 4 lock files (NTSActivityAudit/Errors/Usage***.lck), these normal I assume? Also, just curious, why is "tell traveler Active" showing 0 users when I see all the successful connections via the Traveler DB?
Update: Most all disconnected devices started connecting within the last hour, almost 24 hours after last sync. While happy to see connections, makes me feel uncomfortable that I couldn't locate source of issue. I performed some basic maintenance, etc... but nothing that would alter Traveler configuration.
tell traveler Active only reports the number of users that are actually in the process of syncing when the command is run. It does not show how many devices have been connected.
Yes the .lck files are normal.
This sounds like it is all client side (Apple) connectivity issues. Likely after the firewall issue was fixed the devices are in some mismatched state. Did you try rebooting any iPhones? A lot of times rebooting the Apple device will solve connectivity issues. Though I would have thought recreating the profile would have worked, but with Apple who knows.
The Traveler server is just waiting for the devices to connect, so I don't believe there are any issues with the server.
What might be the mismatched state: It probably is the HTTP OPTIONS request from the device that is failing, but can't tell why some devices would get in and others would not (maybe they still have the result cached and haven't done OPTIONS again yet).
Hello Timothy, just wanted (albeit overdue) to close this post out. While I provided an earlier update, before your response, I should have commented. Thanks, appreciate the additional context.