I have an issue where certain end user's Communicator program will not reconnect back to the Shoretel server (version 14.2) after it either runs a full backup which restarts the services, or after a reboot. In order to reconnect the user has to restart the Communicator program or log off and back on the workstation.
What I have noticed in the logs is that on these workstations (Windows 7 Pro) that fail to reconnect there will be multiple errors showing that it is only trying to reconnect back to the Shoretel server by using the workstations IPv6 address, which I am not using on my network at all. On workstations that don't have this issue the logs show that it uses the normal IPv4 address first which works fine. This issue isn't limited to the same workstation either, any workstation could potentially have this issue, but then work fine the next time the server is either rebooted or runs it's backup that restarts the services.
I am curious if anyone has seen this before. I don't necessarily want to disable IPv6 on all workstation since this can cause issues with other Microsoft products and isn't recommended to do, and I don't think by simply disabling IPv6 on the Shoretel server would have any effect since it's the workstations Communicator program that is trying to connect back to the server via IPv6. Is there any way to change the Communicator program to force only IPv4?
Any information is appreciated.