Windows Server

Nate · Guest

I get this error for all communication. We have an internal deployment only.
We used to have LCS 2003 working perfectly, but wanted to test the
scalability of 2005. Now the users can login fine but cannot send messages?

can the pool address be the same as the first server?

Bob Christian · Guest

Nate:

You are correct.

My assumption is that you are using a single-server LCS 2005 Enterprise
Edition environment. If you create an A record, for the pool, with the
server's IP address, and then have your clients connect to the A record for
the pool, then you should be fine. LCS will not function properly if you
point the clients to the IP address or to the server name. Using the IP or
the server name is hit or miss in presence information, keyboard activity
notifications, and IMs. Generally, however, you can always log in and your
presence will be posted and visible to you.

I will outline two examples of an LCS 2005 Enterprise Edition configuration
below:
Note: I cleaned up a previous post and added the single-server scenario, so
if it seems generic..."that is by design", as they say.

LCS 2005 Enterprise Edition setup (Single Server):

LCSServer1.ADDomain.ADForest 10.10.10.100
SQLBackEnd.ADDomain.ADForest 10.10.10.90
LCSPool1.ADDomain.ADForest 10.10.10.100 (Note: IP for LCSServer1)
ADGC.ADDomain.ADForest 10.10.10.50
ADGC.ADForest 10.10.10.10
Client 1 10.10.10.201 (DHCP)
Client 2 10.10.10.202 (DHCP)

Even in an LCS 2005 Enterprise Edition deployment, the LCSPoo1 A record must
be placed in DNS (or in a hosts file...note: DNS is preferred). Note that
this IP is the same as the IP for the LCS Server. Clients, however, must be
pointed to the Enterprise Pool A record and not directly to the server.

Though a single-server LCS 2005 EE implementation is not recommended by
Microsoft, it will work just fine. Obviously, the redundancies that a
second server and a network load balancer extend are not present in a
single-server implemenation.

LCS 2005 Enterprise Pool (2 Servers):

LCSServer1.ADDomain.ADForest 10.10.10.100
LCSServer2.ADDomain.ADForest 10.10.10.101
SQLBackEnd.ADDomain.ADForest 10.10.10.90
LCSPool1.ADDomain.ADForest 10.10.10.110 (F5 or similar device)
ADGC.ADDomain.ADForest 10.10.10.50
ADGC.ADForest 10.10.10.10
Client 1 10.10.10.201 (DHCP)
Client 2 10.10.10.202 (DHCP)

The IP 10.10.10.110 would be assigned to a load balancer device, such as an
F5 Big-IP. This is also called the Virtual IP, or VIP. It is possible to
utilize Windows NLB is possible, but there are several caveats...please see
the Microsoft documentation regarding Windows NLB and LCS. The LCSPoo1 VIP
address must be placed in DNS. Clients must be pointed to this
address and not directly to either of the two servers.

It is possible to have a single-server LCS 2005 EE deployment, but it is not
recommended. In the case of a single-server LCS 2005 EE deployment, the
LCSPool1 address would be pointed to the IP of Server1 and not a VIP.

Last additional note: White Board, Voice, and Video features are, though
initiated through LCS, are peer-to-peer functions.

Bob

"Nate" <Nate@discussions.microsoft.com> wrote in message
news:1735D2DC-F61E-4496-A8FF-489A4386038D@microsoft.com...

The following message could not be delivered to all recipien

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