Windows Server

BrianD · Guest

I went through the "autorun" steps successfully.

I also went under the Forest properties and made sure that not only was our
FQDN in there, but our email domain name too.

I downloaded Office Communicator and it tells me "Cannot connect to the
communications service. Please wait for your system administrator to correct
this problem and try again later. If the problem persists, contact your
system administrator."

I also tried downloading Messenger 5.1. According to the deployment
document, messenger 5.1 should have an option under Accounts for LCS. I see
only ".NET passport" and "Exchange" as account types.

I can ping the LCS by name, no problem.
I can telnet to the LCS on port 5060.
If I try port 5061 it says it can't open the connection to the host.

Thanks for the assistance...
Brian

Tim · Guest

Brian,
How is your Communicator client setup? If the advanced connection settings
is set to Automatic configuration then you'll need to have a DNS SRV record
created. You can manually configure the settings in the client to your pool
name using TCP. It should be able to connect using TCP without the SRV record.

Tim

"BrianD" wrote:

Bob Christian · Guest

I agree with Tim. Try configuring the pool DNS name and TCP and see if you
can connect. From there, try creating the SRV record (I can provide a few
links to articles by Jeremy Buch and Joe Schurman) and then connecting.
Additionally, there is a KB article that goes over the autopopulation of the
sign-on information:
http://support.microsoft.com/kb/842296

--
Bob Christian II
MVP - LCS
http://bobchristian.blogspot.com - Blog

"Tim" <Tim@discussions.microsoft.com> wrote in message
news:5E0600DD-2BE3-4E58-B10A-C4E469A954CA@microsoft.com...

BrianD · Guest

Let's focus on Communicator for now because that's our priority here.

I created the SRV record, an A record had already been there. I flushed all
DNS caches.

Still nothing. I did the "diags" recommended in the deploy doc. I used
nslookup, set type=srv, etc and it did return the correct server, TCP, and
Port being 5060.

There is no load balancer in our environment, and no certificate authority.

Now, I learned that a different server had been used a while ago to test
LCS. I made sure there was no SRV record for the other server any longer,
and that LCS had been removed from that server. It does not show up when I
run the nslookup checks mentioned above.

Manual configuration works like a charm.

Any other ideas? Thanks,
BrianD

BrianD · Guest

Guys-

Got it working. In DNS, we had an entry for our FQDN but not a domain for our
"email" domain. Put that in and the auto detect works.

Thanks for all the suggestions that got me thinking!

BrianD

	Windows Server Forum Index -> Live Communications Server	All times are GMT
Page 1 of 1