Avatar of Manish Kumar
Manish Kumar
 asked on

users of two lync pool are not able to chat with each other- Lync 2010

IM Communication is not working between two Lyncpool users
When we try to send a message, user get the little thinking about it wheel, then a red cross next to the message.
Chat / IMMicrosoft Applications

Avatar of undefined
Last Comment
Manish Kumar

8/22/2022 - Mon
Mohammed Hamada

Are all the services working on both pool front ends? is there any errors logged in the event viewer in the Lync part? please post it here
Manish Kumar

ASKER
Lync sevices are working fine on all Lync servers

error showing at user's end
"the callee's primary pool failed to respond in a timely manner"
Mohammed Hamada

No please try to check the front end servers for errors related to the connectivity or latest errors in general.

there must be something related to the IM service or probably port connectivity.
This is the best money I have ever spent. I cannot not tell you how many times these folks have saved my bacon. I learn so much from the contributors.
rwheeler23
Manish Kumar

ASKER
i looked into all front end servers but didn't find any relevant logs. I have copied all event source name.  Let me know if any specific source we need to look.

Source
LS Protocol Stack
LS Routing Data Sync Agent
LS File Transfer Agent Service
LS Audio-Video Conferencing Server
LS User Services
LS User Replicator
LS Address Book and Distribution List Expansion Web Service
LS Web Components Server
LS Location Information Service
LS InterCluster Routing
LS UserPin Service
LS Remote PowerShell
ASKER CERTIFIED SOLUTION
Manish Kumar

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
GET A PERSONALIZED SOLUTION
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.
Manish Kumar

ASKER
HI All,

This issue has been resolved by rebooting all front end servers one by one.

i didn't get any appropriate help so at last i rebooted all the servers one by one