| Author |
Message |
newcomer
Guest
|
 Posted:
Fri Oct 07, 2005 12:50 am Post subject:
communicator clients reporting unknown status |
|
|
I have some communicator clients that are showing unknown status, First off I
have one pool one server all clients connect using a fully qualified domain
name. Mainly this problem is happening with 2 of our users. If I type there
names in my communicator client I get status unknown if anyone else types
there names in communicator they get status unknown. Now if the 2 problem
user’s type there names into there communicator clients it will report them
as being online. What’s the deal with all of this is this communicator bug
show we be using windows messenger 5.1. |
|
| Back to top |
|
 |
bunchas
Joined: 07 Oct 2005
Posts: 5
|
| Posted:
Fri Oct 07, 2005 2:15 pm Post subject:
re:communicator clients reporting unknown status |
|
|
| I am experiencing the same thing. Only three test user on the system all, have the same problem no matter which computer they log into. When trying to send messages or add another use to the contact list, it fails. I'm going to check out the LCS toolkit and see what it has to diagnose problems. |
|
| Back to top |
|
|
Bob Christian
Guest
|
| Posted:
Fri Oct 07, 2005 8:51 pm Post subject:
Re: communicator clients reporting unknown status |
|
|
Are they using the FQDN of the Enterprise Server or the FQDN of the
Enterprise Pool name?
--
Bob Christian II
http://bobchristian.blogspot.com - Blog
"newcomer" <newcomer@discussions.microsoft.com> wrote in message
news:E575997D-72DC-49A0-8237-2F1A6516EE66@microsoft.com...
| Quote: | I have some communicator clients that are showing unknown status, First off
I
have one pool one server all clients connect using a fully qualified
domain
name. Mainly this problem is happening with 2 of our users. If I type
there
names in my communicator client I get status unknown if anyone else types
there names in communicator they get status unknown. Now if the 2 problem
user's type there names into there communicator clients it will report
them
as being online. What's the deal with all of this is this communicator bug
show we be using windows messenger 5.1. |
|
|
| Back to top |
|
|
newcomer
Guest
|
| Posted:
Fri Oct 07, 2005 8:51 pm Post subject:
re:communicator clients reporting unknown status |
|
|
Check this link out
http://www.microsoft.com/events/series/rtccollaboration.mspx
Go ahead and download webcast
TechNet Webcast: Using Microsoft Office Live Communications Server 2005
Technical Troubleshooting Tools and Resource Kit (Level 200)
Its supposed to be other webcast on that page also that can help in
communicator problems
"bunchas" wrote:
| Quote: | I am experiencing the same thing. Only three test user on the system
all, have the same problem no matter which computer they log into.
When trying to send messages or add another use to the contact list,
it fails. I'm going to check out the LCS toolkit and see what it has
to diagnose problems.
|
|
|
| Back to top |
|
|
newcomer
Guest
|
| Posted:
Sat Oct 08, 2005 12:50 am Post subject:
Re: communicator clients reporting unknown status |
|
|
I have one server one pool all clients are configured to go to
lcs.example.com
"Bob Christian" wrote:
| Quote: | Are they using the FQDN of the Enterprise Server or the FQDN of the
Enterprise Pool name?
--
Bob Christian II
http://bobchristian.blogspot.com - Blog
"newcomer" <newcomer@discussions.microsoft.com> wrote in message
news:E575997D-72DC-49A0-8237-2F1A6516EE66@microsoft.com...
I have some communicator clients that are showing unknown status, First off
I
have one pool one server all clients connect using a fully qualified
domain
name. Mainly this problem is happening with 2 of our users. If I type
there
names in my communicator client I get status unknown if anyone else types
there names in communicator they get status unknown. Now if the 2 problem
user's type there names into there communicator clients it will report
them
as being online. What's the deal with all of this is this communicator bug
show we be using windows messenger 5.1.
|
|
|
| Back to top |
|
|
Bob Christian
Guest
|
| Posted:
Mon Oct 10, 2005 12:50 am Post subject:
Re: communicator clients reporting unknown status |
|
|
Is LCS.example.com the FQDN of the Enterprise Server or is it the FQDN of
the Enterprise Pool?
--
Bob Christian II
http://bobchristian.blogspot.com - Blog
"newcomer" <newcomer@discussions.microsoft.com> wrote in message
news:3B0E7D95-8619-4A40-842E-6D5AD78409CF@microsoft.com...
| Quote: | I have one server one pool all clients are configured to go to
lcs.example.com
"Bob Christian" wrote:
Are they using the FQDN of the Enterprise Server or the FQDN of the
Enterprise Pool name?
--
Bob Christian II
http://bobchristian.blogspot.com - Blog
"newcomer" <newcomer@discussions.microsoft.com> wrote in message
news:E575997D-72DC-49A0-8237-2F1A6516EE66@microsoft.com...
I have some communicator clients that are showing unknown status, First
off
I
have one pool one server all clients connect using a fully qualified
domain
name. Mainly this problem is happening with 2 of our users. If I type
there
names in my communicator client I get status unknown if anyone else
types
there names in communicator they get status unknown. Now if the 2
problem
user's type there names into there communicator clients it will report
them
as being online. What's the deal with all of this is this communicator
bug
show we be using windows messenger 5.1.
|
|
|
| Back to top |
|
|
newcomer
Guest
|
| Posted:
Mon Oct 10, 2005 8:07 am Post subject:
Re: communicator clients reporting unknown status |
|
|
Since I only have one server it is both
"Bob Christian" wrote:
| Quote: | Is LCS.example.com the FQDN of the Enterprise Server or is it the FQDN of
the Enterprise Pool?
--
Bob Christian II
http://bobchristian.blogspot.com - Blog
"newcomer" <newcomer@discussions.microsoft.com> wrote in message
news:3B0E7D95-8619-4A40-842E-6D5AD78409CF@microsoft.com...
I have one server one pool all clients are configured to go to
lcs.example.com
"Bob Christian" wrote:
Are they using the FQDN of the Enterprise Server or the FQDN of the
Enterprise Pool name?
--
Bob Christian II
http://bobchristian.blogspot.com - Blog
"newcomer" <newcomer@discussions.microsoft.com> wrote in message
news:E575997D-72DC-49A0-8237-2F1A6516EE66@microsoft.com...
I have some communicator clients that are showing unknown status, First
off
I
have one pool one server all clients connect using a fully qualified
domain
name. Mainly this problem is happening with 2 of our users. If I type
there
names in my communicator client I get status unknown if anyone else
types
there names in communicator they get status unknown. Now if the 2
problem
user's type there names into there communicator clients it will report
them
as being online. What's the deal with all of this is this communicator
bug
show we be using windows messenger 5.1.
|
|
|
| Back to top |
|
|
Bob Christian
Guest
|
| Posted:
Mon Oct 10, 2005 8:51 am Post subject:
Re: communicator clients reporting unknown status |
|
|
Are you using LCS 2005 Standard Edition or LCS 2005 Enterprise Edition? You
mentioned pool earlier, but it was not clear if you were using LCS 2005 SE
or LCS 2005 EE.
If you have a single LCS 2005 SE server, the server name and the pool name
(FQDN) are one in the same...and you are correct.
If you have a single LCS 2005 EE server, then the IP for the server and the
pool can be one in the same, but you will require an A record for the server
and an A record for the pool name. Those two A records can resolve the same
IP address. Each client needs to connect to the pool vial the FQDN of the
pool. (pool.domain.ext).
This is a brief explanation, which I generally send out if the issue is with
LCS 2005 EE and users are connecting via the server's FQDN or the server's
IP address and not the pool name.
When using LCS 2005 Enterprise Edition it is very important to create the
DNS record for the pool address and point the client to the pool address
rather than directly to the server. This is important even in a single
server LCS 2005 EE environment. If you have a single server then you should
create an A record for the pool that has the same IP as Server.
Ex (A Records)
Server1.domain.local - 10.10.10.105
Pool1.domain.local - 10.10.10.105
Ex with a load balancer (F5 or similar device)
Ex (A Records)
Server1.domain.local - 10.10.10.105
Server1.domain.local - 10.10.10.106
Pool1.domain.local - 10.10.10.110 (Note: This would be the virtual IP,
or VIP, assigned to the load balancer.)
Meni's LCS guide site has a quick overview of this process:
http://www.lcs-guides.com/modules.php?name=News&file=article&sid=6
--
Bob Christian II
http://bobchristian.blogspot.com - Blog
"newcomer" <newcomer@discussions.microsoft.com> wrote in message
news:9D81E94C-A18E-44B4-A263-82DFF0BA8B11@microsoft.com...
| Quote: | Since I only have one server it is both
"Bob Christian" wrote:
Is LCS.example.com the FQDN of the Enterprise Server or is it the FQDN of
the Enterprise Pool?
--
Bob Christian II
http://bobchristian.blogspot.com - Blog
"newcomer" <newcomer@discussions.microsoft.com> wrote in message
news:3B0E7D95-8619-4A40-842E-6D5AD78409CF@microsoft.com...
I have one server one pool all clients are configured to go to
lcs.example.com
"Bob Christian" wrote:
Are they using the FQDN of the Enterprise Server or the FQDN of the
Enterprise Pool name?
--
Bob Christian II
http://bobchristian.blogspot.com - Blog
"newcomer" <newcomer@discussions.microsoft.com> wrote in message
news:E575997D-72DC-49A0-8237-2F1A6516EE66@microsoft.com...
I have some communicator clients that are showing unknown status,
First
off
I
have one pool one server all clients connect using a fully qualified
domain
name. Mainly this problem is happening with 2 of our users. If I
type
there
names in my communicator client I get status unknown if anyone else
types
there names in communicator they get status unknown. Now if the 2
problem
user's type there names into there communicator clients it will
report
them
as being online. What's the deal with all of this is this
communicator
bug
show we be using windows messenger 5.1.
|
|
|
| Back to top |
|
|
newcomer
Guest
|
| Posted:
Mon Oct 10, 2005 12:50 pm Post subject:
Re: communicator clients reporting unknown status |
|
|
I'm using standard edtion I think this is a problrm with the communicator
client and not the server. I've already ran server diag from the resource kit
and everything turned out fine. Do you happen to have any guides or links on
trouble shooting communicator I have not been able to find anything on
trouble shooting communicator problems.
"Bob Christian" wrote:
| Quote: | Are you using LCS 2005 Standard Edition or LCS 2005 Enterprise Edition? You
mentioned pool earlier, but it was not clear if you were using LCS 2005 SE
or LCS 2005 EE.
If you have a single LCS 2005 SE server, the server name and the pool name
(FQDN) are one in the same...and you are correct.
If you have a single LCS 2005 EE server, then the IP for the server and the
pool can be one in the same, but you will require an A record for the server
and an A record for the pool name. Those two A records can resolve the same
IP address. Each client needs to connect to the pool vial the FQDN of the
pool. (pool.domain.ext).
This is a brief explanation, which I generally send out if the issue is with
LCS 2005 EE and users are connecting via the server's FQDN or the server's
IP address and not the pool name.
When using LCS 2005 Enterprise Edition it is very important to create the
DNS record for the pool address and point the client to the pool address
rather than directly to the server. This is important even in a single
server LCS 2005 EE environment. If you have a single server then you should
create an A record for the pool that has the same IP as Server.
Ex (A Records)
Server1.domain.local - 10.10.10.105
Pool1.domain.local - 10.10.10.105
Ex with a load balancer (F5 or similar device)
Ex (A Records)
Server1.domain.local - 10.10.10.105
Server1.domain.local - 10.10.10.106
Pool1.domain.local - 10.10.10.110 (Note: This would be the virtual IP,
or VIP, assigned to the load balancer.)
Meni's LCS guide site has a quick overview of this process:
http://www.lcs-guides.com/modules.php?name=News&file=article&sid=6
--
Bob Christian II
http://bobchristian.blogspot.com - Blog
"newcomer" <newcomer@discussions.microsoft.com> wrote in message
news:9D81E94C-A18E-44B4-A263-82DFF0BA8B11@microsoft.com...
Since I only have one server it is both
"Bob Christian" wrote:
Is LCS.example.com the FQDN of the Enterprise Server or is it the FQDN of
the Enterprise Pool?
--
Bob Christian II
http://bobchristian.blogspot.com - Blog
"newcomer" <newcomer@discussions.microsoft.com> wrote in message
news:3B0E7D95-8619-4A40-842E-6D5AD78409CF@microsoft.com...
I have one server one pool all clients are configured to go to
lcs.example.com
"Bob Christian" wrote:
Are they using the FQDN of the Enterprise Server or the FQDN of the
Enterprise Pool name?
--
Bob Christian II
http://bobchristian.blogspot.com - Blog
"newcomer" <newcomer@discussions.microsoft.com> wrote in message
news:E575997D-72DC-49A0-8237-2F1A6516EE66@microsoft.com...
I have some communicator clients that are showing unknown status,
First
off
I
have one pool one server all clients connect using a fully qualified
domain
name. Mainly this problem is happening with 2 of our users. If I
type
there
names in my communicator client I get status unknown if anyone else
types
there names in communicator they get status unknown. Now if the 2
problem
user's type there names into there communicator clients it will
report
them
as being online. What's the deal with all of this is this
communicator
bug
show we be using windows messenger 5.1.
|
|
|
| Back to top |
|
|
Bob Christian
Guest
|
| Posted:
Wed Oct 12, 2005 8:51 pm Post subject:
Re: communicator clients reporting unknown status |
|
|
Newcomer -
I apologize for not answering. No, I do not have any resources handy for
troubleshooting Communicator. I do know that there is a Microsoft guide out
there, but it is either still internal or it has not yet been released.
Bob
--
Bob Christian II
http://bobchristian.blogspot.com - Blog
"newcomer" <newcomer@discussions.microsoft.com> wrote in message
news:28CDF339-5ADF-443E-9357-8DB7C75523CC@microsoft.com...
[quote]I'm using standard edtion I think this is a problrm with the communicator
client and not the server. I've already ran server diag from the resource
kit
and everything turned out fine. Do you happen to have any guides or links
on
trouble shooting communicator I have not been able to find anything on
trouble shooting communicator problems.
"Bob Christian" wrote:
Are you using LCS 2005 Standard Edition or LCS 2005 Enterprise Edition?
You
mentioned pool earlier, but it was not clear if you were using LCS 2005
SE
or LCS 2005 EE.
If you have a single LCS 2005 SE server, the server name and the pool
name
(FQDN) are one in the same...and you are correct.
If you have a single LCS 2005 EE server, then the IP for the server and
the
pool can be one in the same, but you will require an A record for the
server
and an A record for the pool name. Those two A records can resolve the
same
IP address. Each client needs to connect to the pool vial the FQDN of
the
pool. (pool.domain.ext).
This is a brief explanation, which I generally send out if the issue is
with
LCS 2005 EE and users are connecting via the server's FQDN or the
server's
IP address and not the pool name.
When using LCS 2005 Enterprise Edition it is very important to create the
DNS record for the pool address and point the client to the pool address
rather than directly to the server. This is important even in a single
server LCS 2005 EE environment. If you have a single server then you
should
create an A record for the pool that has the same IP as Server.
Ex (A Records)
Server1.domain.local - 10.10.10.105
Pool1.domain.local - 10.10.10.105
Ex with a load balancer (F5 or similar device)
Ex (A Records)
Server1.domain.local - 10.10.10.105
Server1.domain.local - 10.10.10.106
Pool1.domain.local - 10.10.10.110 (Note: This would be the virtual
IP,
or VIP, assigned to the load balancer.)
Meni's LCS guide site has a quick overview of this process:
http://www.lcs-guides.com/modules.php?name=News&file=article&sid=6
--
Bob Christian II
http://bobchristian.blogspot.com - Blog
"newcomer" <newcomer@discussions.microsoft.com> wrote in message
news:9D81E94C-A18E-44B4-A263-82DFF0BA8B11@microsoft.com...
Since I only have one server it is both
"Bob Christian" wrote:
Is LCS.example.com the FQDN of the Enterprise Server or is it the FQDN
of
the Enterprise Pool?
--
Bob Christian II
http://bobchristian.blogspot.com - Blog
"newcomer" <newcomer@discussions.microsoft.com> wrote in message
news:3B0E7D95-8619-4A40-842E-6D5AD78409CF@microsoft.com...
I have one server one pool all clients are configured to go to
lcs.example.com
"Bob Christian" wrote:
Are they using the FQDN of the Enterprise Server or the FQDN of the
Enterprise Pool name?
--
Bob Christian II
http://bobchristian.blogspot.com - Blog
"newcomer" <newcomer@discussions.microsoft.com> wrote in message
news:E575997D-72DC-49A0-8237-2F1A6516EE66@microsoft.com...
I have some communicator clients that are showing unknown status,
First
off
I
have one pool one server all clients connect using a fully
qualified
domain
name. Mainly this problem is happening with 2 of our users. If I
type
there
names in my communicator client I get status unknown if anyone
else
types
there names in communicator they get status unknown. Now if the 2
problem
user's type there names into there communicator clients it will
report
them
as being online. What's the deal with all of this is this
communicator
bug
show we be using windows messenger 5.1.
[/quote] |
|
| Back to top |
|
|
toml@online.microsoft.com
Guest
|
| Posted:
Sat Oct 15, 2005 12:50 am Post subject:
Re: communicator clients reporting unknown status |
|
|
The troubleshooting of communicator has changed only slightly from Windows
Messenger. At this time we only need to worry about enabling tracing in the
registry for LCAPI
I posted this today (as a result of this thread)
http://blogs.technet.com/toml/archive/2005/10/14/412536.aspx
Tom Laciano
“This posting is provided "AS IS" with no warranties, and confers no
rights."
--------------------
From: "Bob Christian" <BobChristian@removethis.gmail.com>
References: <E575997D-72DC-49A0-8237-2F1A6516EE66@microsoft.com>
<efBS6n3yFHA.3256@TK2MSFTNGP09.phx.gbl>
<3B0E7D95-8619-4A40-842E-6D5AD78409CF@microsoft.com>
<O324UWRzFHA.3836@TK2MSFTNGP10.phx.gbl>
<9D81E94C-A18E-44B4-A263-82DFF0BA8B11@microsoft.com>
<uv#hqeWzFHA.3864@TK2MSFTNGP12.phx.gbl>
<28CDF339-5ADF-443E-9357-8DB7C75523CC@microsoft.com>
Subject: Re: communicator clients reporting unknown status
Date: Wed, 12 Oct 2005 15:40:59 -0400
Lines: 148
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2670
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670
X-RFC2646: Format=Flowed; Original
Message-ID: <um4KcT2zFHA.2540@TK2MSFTNGP09.phx.gbl>
Newsgroups: microsoft.public.livecomm.general
NNTP-Posting-Host: dol-65-196-106-190.dol.gov 65.196.106.190
Path:
TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP0
9.phx.gbl
Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.livecomm.general:10297
X-Tomcat-NG: microsoft.public.livecomm.general
Newcomer -
I apologize for not answering. No, I do not have any resources handy for
troubleshooting Communicator. I do know that there is a Microsoft guide
out
there, but it is either still internal or it has not yet been released.
Bob
--
Bob Christian II
http://bobchristian.blogspot.com - Blog
"newcomer" <newcomer@discussions.microsoft.com> wrote in message
news:28CDF339-5ADF-443E-9357-8DB7C75523CC@microsoft.com...
| Quote: | I'm using standard edtion I think this is a problrm with the communicator
client and not the server. I've already ran server diag from the resource
kit
and everything turned out fine. Do you happen to have any guides or links
on
trouble shooting communicator I have not been able to find anything on
trouble shooting communicator problems.
"Bob Christian" wrote:
Are you using LCS 2005 Standard Edition or LCS 2005 Enterprise Edition?
You
mentioned pool earlier, but it was not clear if you were using LCS 2005
SE
or LCS 2005 EE.
If you have a single LCS 2005 SE server, the server name and the pool
name
(FQDN) are one in the same...and you are correct.
If you have a single LCS 2005 EE server, then the IP for the server and
the
pool can be one in the same, but you will require an A record for the
server
and an A record for the pool name. Those two A records can resolve the
same
IP address. Each client needs to connect to the pool vial the FQDN of
the
pool. (pool.domain.ext).
This is a brief explanation, which I generally send out if the issue is
with
LCS 2005 EE and users are connecting via the server's FQDN or the
server's
IP address and not the pool name.
When using LCS 2005 Enterprise Edition it is very important to create the
DNS record for the pool address and point the client to the pool address
rather than directly to the server. This is important even in a single
server LCS 2005 EE environment. If you have a single server then you
should
create an A record for the pool that has the same IP as Server.
Ex (A Records)
Server1.domain.local - 10.10.10.105
Pool1.domain.local - 10.10.10.105
Ex with a load balancer (F5 or similar device)
Ex (A Records)
Server1.domain.local - 10.10.10.105
Server1.domain.local - 10.10.10.106
Pool1.domain.local - 10.10.10.110 (Note: This would be the virtual
IP,
or VIP, assigned to the load balancer.)
Meni's LCS guide site has a quick overview of this process:
http://www.lcs-guides.com/modules.php?name=News&file=article&sid=6
--
Bob Christian II
http://bobchristian.blogspot.com - Blog
"newcomer" <newcomer@discussions.microsoft.com> wrote in message
news:9D81E94C-A18E-44B4-A263-82DFF0BA8B11@microsoft.com...
Since I only have one server it is both
"Bob Christian" wrote:
Is LCS.example.com the FQDN of the Enterprise Server or is it the
FQDN
of
the Enterprise Pool?
--
Bob Christian II
http://bobchristian.blogspot.com - Blog
"newcomer" <newcomer@discussions.microsoft.com> wrote in message
news:3B0E7D95-8619-4A40-842E-6D5AD78409CF@microsoft.com...
I have one server one pool all clients are configured to go to
lcs.example.com
"Bob Christian" wrote:
Are they using the FQDN of the Enterprise Server or the FQDN of the
Enterprise Pool name?
--
Bob Christian II
http://bobchristian.blogspot.com - Blog
"newcomer" <newcomer@discussions.microsoft.com> wrote in message
news:E575997D-72DC-49A0-8237-2F1A6516EE66@microsoft.com...
I have some communicator clients that are showing unknown status,
First
off
I
have one pool one server all clients connect using a fully
qualified
domain
name. Mainly this problem is happening with 2 of our users. If I
type
there
names in my communicator client I get status unknown if anyone
else
types
there names in communicator they get status unknown. Now if the 2
problem
user's type there names into there communicator clients it will
report
them
as being online. What's the deal with all of this is this
communicator
bug
show we be using windows messenger 5.1.
|
|
|
| Back to top |
|
|
joe
Guest
|
| Posted:
Thu Oct 27, 2005 12:52 am Post subject:
Re: re:communicator clients reporting unknown status |
|
|
If your problem got solved please let me know how you solved it, as I
do have the same problem.
Thanks.
Joseph
bunchas wrote:
| Quote: | I am experiencing the same thing. Only three test user on the system
all, have the same problem no matter which computer they log into.
When trying to send messages or add another use to the contact list,
it fails. I'm going to check out the LCS toolkit and see what it has
to diagnose problems. |
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in
