A significant number of authentication or authorization failures have occurred on messages for the account zxxxx.hxxx@xxxx.local and the first attempt was from the IP address 1xx.1xx.6x.1xx. 62716 failures have been identified in the last 180 minutes. There have been 234962 errors in total. Note: the user uri might have been truncated to 64 charac
Hi!
A good test to apply is to use another Lync account in that affected machine. If this account connects, so the issue could be related to the local machine and the information stored in cache for the certificate.
In that case you can delete from the certificate console ( mmc.exe ) as "Current User" the certificate issued by "Communications Server" depending the affected sip address , example:
After that, you can test and let us know the results.
Regards.
Hi Joseph!
Do you have any update about it?.
Regards.
Carlos,
I was finally able to get the local IT support to get over to the users machine and we found that the time was off. Once he corrected the time the user had no problem connecting. What we did find is that the client is having a problem with users syncing their time with the DC...
Thanks you, Joe.
Carlos,
I was finally able to get the local IT support to get over to the users machine and we found that the time was off. Once he corrected the time the user had no problem connecting. What we did find is that the client is having a problem with users syncing their time with the DC...
Thanks you, Joe.
- Proposed as answer by Mark Vale 11 hours 28 minutes ago
Carlos,
I was finally able to get the local IT support to get over to the users machine and we found that the time was off. Once he corrected the time the user had no problem connecting. What we did find is that the client is having a problem with users syncing their time with the DC...
Thanks you, Joe.
- Proposed as answer by Mark Vale Tuesday, July 21, 2015 7:56 PM
Carlos,
I was finally able to get the local IT support to get over to the users machine and we found that the time was off. Once he corrected the time the user had no problem connecting. What we did find is that the client is having a problem with users syncing their time with the DC...
Thanks you, Joe.
- Proposed as answer by Mark Vale Tuesday, July 21, 2015 7:56 PM