Hello!
This is similar to this entry. The exception is that instead of an explicitly permitted user receiving a "no connection" notification, a user that should fall under Default "Free/Busy" gets "no connection" on shared calendars. Here's some pertinent information:
- The user is on a personal, non-domain joined machine.
- The user is connecting via HTTP (with msstd defined for proxy connections) from Outlook to Exchange 2007.
- The user connects to shared calendars WITHOUT ERRORS when logging into the domain on a DJ'ed computer.
- Per the aforementioned article, adding him as an editor to the calendar allows him error-free connection.
- Interestingly enough, removing that permission allows him to continue the connection for a time, but he still sees everything instead of reverting to default free/busy.
Here's what I've done so far:
- Added Editor rights manually to a shared calendar, which allowed connection, but then removed, which maintained connection and then removed it after about 15 mins.
- Toggled Cached mode, without success.
- Resynced his profile, without success.
- Removed and recreated his profile, without success.
- Turned on logging, which created ETL files in the OKCalLog directory in normal logging location (%temp% etc. etc.), but which ETLs yielded event codes for which Google had no useful input (and very little user friendly information besides). Codes 120 and
170 were most pertinent.
This user was previously working on domain-joined machines only. As I mentioned, when he logs in to a domain-joined machine, he has no issues.
Help! What am I missing?