LCS2005 Fresh Install Problem

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!
cardscompAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

inbarasanCommented:
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
cardscompAuthor Commented:
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
mohdabsarCommented:
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

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
cardscompAuthor Commented:
i accepted his solution as that fixed the problem .the FQDN was wrong in my SIP settings. thanks!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.