?
Solved

LCS2005 Fresh Install Problem

Posted on 2007-03-18
5
Medium Priority
?
372 Views
Last Modified: 2013-11-29
I have installed Microsoft Live Communications Server 2005 on my network. I cannot get any clients (Office Communicator or Windows Messenger 5.1) to connect to the LCS Server. All of the services are running and everything seems to be ok from the server end. I've checked a couple of the diag tools and the server seems to be responding ok. I do get this message when using LCSDiag.exe with the test client:

Response 504
504 Server time-out
The signing failed. There is a connectivity problem on one server
Please go to server servername.domain.local and run LC Diagnostics
to check server connectivity to all server from WMI
if the test passed go to the next server in the chain and run the test again.

I am using TCP, not TLS. I know TLS is more secure but for simplicity, let's make TCP work.

Anyone have any ideas? Everything seemed to be OK during the install, but I cannot connect at all. Thanks!
0
Comment
Question by:cardscomp
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
5 Comments
 
LVL 14

Expert Comment

by:inbarasan
ID: 18754658
Check on which IP, the LCS TCP port(5060 i believe) is listening. Which ever IP it is listening you should make sure client is connecting to that IP.
0
 

Author Comment

by:cardscomp
ID: 18755141
Yes the server does respond. I've used the LCSPing.exe utility to communicate with the server and it responds on 5060. I have no internal firewalls or anything that i would think would be impeding communications on my LAN. thanks,
0
 
LVL 11

Accepted Solution

by:
mohdabsar earned 750 total points
ID: 19148081
I have had faced same issue the LCS 2005 installation was fine....still client were unable to connect...
The issue in my env. was client were trying to connect to sip service through e-mail address and it was failing....
then I tried through username.FQDN (of domain) then it started working fine...

Change the SIP address of users through AD to username.FQDN and try...
0
 

Author Comment

by:cardscomp
ID: 19310802
i accepted his solution as that fixed the problem .the FQDN was wrong in my SIP settings. thanks!
0

Featured Post

Office 365 Training for IT Pros

Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies.  Only from Platform Scholar.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

1. Boot PC and press F10, select storage options and change the compatibility from “AHCI” to “IDE”, save and exit 2. Boot PC and press F12 3. Upon PXE display of searching for DHCP server, press Pause break to obtain MAC address 3. Open Configu…
Issue: One Windows 2008 R2 64bit server on the network unable to connect to a buffalo Device (Linkstation) with firmware version 1.56. There are a total of four servers on the network this being one of them. Troubleshooting Steps: Connect via h…
Michael from AdRem Software explains how to view the most utilized and worst performing nodes in your network, by accessing the Top Charts view in NetCrunch network monitor (https://www.adremsoft.com/). Top Charts is a view in which you can set seve…
Monitoring a network: how to monitor network services and why? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the philosophy behind service monitoring and why a handshake validation is critical in network monitoring. Software utilized …

752 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question