| Author |
Message |
DragonWoman
Guest
|
Posted:
Wed Nov 02, 2005 1:51 am Post subject:
Diagnostic Connect OK, but Not with Communicator |
|
|
I am having trouble connecting to my LCS 2005 via Communicator. I feel
like I've read every post on the internet regarding this issue.
Everything looked right so I downloaded and installed the ResKit
Diagnostics Console.
I ran the TCP (port 5060) Connectivity Test: Success!
I ran the Diagnostic Client Test: Success!
But, when I try to use Communicator and sign into the same server with
the same SIP/User info, no luck! I get the annoying "service is
unavailable" error.
Can't figure out why the diagnostic works but not the real thing.
Any suggestions?
Thank you.
-Diana |
|
| Back to top |
|
 |
Guest
|
Posted:
Wed Nov 02, 2005 5:51 pm Post subject:
Re: Diagnostic Connect OK, but Not with Communicator |
|
|
You may have tried this already, but make sure in the server that the
domain matches the SIP. We had the same problem and our domain was
internal.domainname.com but the sip was assigned as the email address
first.last@domainname.com. We had to go into the LCS 2005 settings and
do the following:
1. right click on the forest part of the tree and click properties
2. By default internal.domainname.com was listed we removed that and
added domainname.com (without the internal part as that is how the SIP
URI was setup) and then click OK.
3. Restart the LCS service just to be safe, and then try to connect
with your communicator client.
Also can you connect with Windows Messenger 5.1? I had an issue where
Messenger would connect, but communicator wouldn't. That was in a test
environment. Luckily it didn't exhibit that issue when we went live. |
|
| Back to top |
|
 |
DragonWoman
Guest
|
Posted:
Wed Nov 02, 2005 9:51 pm Post subject:
Re: Diagnostic Connect OK, but Not with Communicator |
|
|
Thanks for the reply. The domain does match the SIP and I just can't
figure it out.
I uninstalled Communicator and installed WM5.1. WM can connect using
the same SIP and login information, but the users all seem offline even
though they're not.
Argh! |
|
| Back to top |
|
 |
|
|
|
|