| Author |
Message |
Bernard
Guest
|
 Posted:
Tue Jan 11, 2005 2:09 pm Post subject:
TLS Connection |
|
|
Hi there
I am unable to log into my LCS 2005 server using Windows Messanger 5.1, and
using TLS as the protocol. I would very much appreciate it if someone could
give me a hint on what could be wrong.
I have LCS running on a server, certificates have been installed and I have
setup the DNS entries to be able to resolve the pool. The clients are
configured manually (I have tried setting the server to the FQDN of the pool
and the server, and attempted to use the IP address, all resulting in the
same error).
Here is the error I get from windows messanger:
An HTTPS or TCP connection could not be made. Please wait for your network
administrator to correct this problem, and try again later.
The reason I am using TLS is because I am unable to send IMs if I specify
TCP (I am, however, able to log in with TCP...)
Thanks in advance!
Bermard |
|
| Back to top |
|
 |
Dhigha D Sekara
Guest
|
| Posted:
Wed Jan 12, 2005 12:30 pm Post subject:
Re: TLS Connection |
|
|
While using TLS you cannot use configure the client to point at the server
using IP Address. you would require to point the client to the pool FQDN.
The certificate issued to the server should have the pool name as the
subject name.
With the symptoms you are that you are able to login using TCP but IM fails
seems like the pool FQDN is not resolvable from the client.
Can you verify that please...
If the problem persists can you please post the client side logs..
To enable client side logging on a PC set the
"HKEY_CURRENT_USER\Software\Microsoft\Tracing\RTCDLL\EnableFileTracing"
registry key to 1 and then restart Windows messenger. A log file is then
created in the users %USERPROFILE%\Tracing directory (unless you configure
another location)
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send email to this address, post a reply to this newsgroup
"Bernard" <Bernard@discussions.microsoft.com> wrote in message
news:0CD7E332-F283-4552-A3B2-F7E1673573A1@microsoft.com...
| Quote: | Hi there
I am unable to log into my LCS 2005 server using Windows Messanger 5.1,
and
using TLS as the protocol. I would very much appreciate it if someone
could
give me a hint on what could be wrong.
I have LCS running on a server, certificates have been installed and I
have
setup the DNS entries to be able to resolve the pool. The clients are
configured manually (I have tried setting the server to the FQDN of the
pool
and the server, and attempted to use the IP address, all resulting in the
same error).
Here is the error I get from windows messanger:
An HTTPS or TCP connection could not be made. Please wait for your
network
administrator to correct this problem, and try again later.
The reason I am using TLS is because I am unable to send IMs if I specify
TCP (I am, however, able to log in with TCP...)
Thanks in advance!
Bermard |
|
|
| Back to top |
|
|
Bernard
Guest
|
| Posted:
Wed Jan 12, 2005 12:41 pm Post subject:
Re: TLS Connection |
|
|
Thank you so much for your reply!
I have tried pointing the client to various addresses, including the pool.
The name of my pool is pool1.labs.local. It is located on a server with
FQDN which is lcs.labs.local and IP address 10.1.0.50
From the client machine, I can ping any of these names and get a proper
response. So to answer your question, the FQDN of the pool
(pool1.labs.local) resolves to 10.1.0.50. This is correct as far as I
understand.
FYI - we have a single LCS 2005 EE server setup.
I hope this may help...
Just a question - what impact will the subject name of the certificate have
on the workings of TLS?
"Dhigha D Sekaran<msft>" wrote:
| Quote: | While using TLS you cannot use configure the client to point at the server
using IP Address. you would require to point the client to the pool FQDN.
The certificate issued to the server should have the pool name as the
subject name.
With the symptoms you are that you are able to login using TCP but IM fails
seems like the pool FQDN is not resolvable from the client.
Can you verify that please...
If the problem persists can you please post the client side logs..
To enable client side logging on a PC set the
"HKEY_CURRENT_USER\Software\Microsoft\Tracing\RTCDLL\EnableFileTracing"
registry key to 1 and then restart Windows messenger. A log file is then
created in the users %USERPROFILE%\Tracing directory (unless you configure
another location)
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send email to this address, post a reply to this newsgroup
"Bernard" <Bernard@discussions.microsoft.com> wrote in message
news:0CD7E332-F283-4552-A3B2-F7E1673573A1@microsoft.com...
Hi there
I am unable to log into my LCS 2005 server using Windows Messanger 5.1,
and
using TLS as the protocol. I would very much appreciate it if someone
could
give me a hint on what could be wrong.
I have LCS running on a server, certificates have been installed and I
have
setup the DNS entries to be able to resolve the pool. The clients are
configured manually (I have tried setting the server to the FQDN of the
pool
and the server, and attempted to use the IP address, all resulting in the
same error).
Here is the error I get from windows messanger:
An HTTPS or TCP connection could not be made. Please wait for your
network
administrator to correct this problem, and try again later.
The reason I am using TLS is because I am unable to send IMs if I specify
TCP (I am, however, able to log in with TCP...)
Thanks in advance!
Bermard
|
|
|
| Back to top |
|
|
Dhigha D Sekara
Guest
|
| Posted:
Thu Jan 13, 2005 1:26 pm Post subject:
Re: TLS Connection |
|
|
In that case can you please capture tracing from the cleint and post it..
for details on cert configuration for LCS hope you have seen this document
Live Communications Server 2005 Document: Configuring Certificates
http://teams/sites/liveplan/Shared%20Documents/Forms/AllItems.aspx?RootFolder=%2fsites%2fliveplan%2fShared%20Documents%2fDesign%20Specifications&View=%7b6F33217F%2dE956%2d412F%2dB02C%2dD8F7DD21E286%7d
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send email to this address, post a reply to this newsgroup
"Bernard" <Bernard@discussions.microsoft.com> wrote in message
news:7171FB63-5F89-4780-A048-3BEFC623BF45@microsoft.com...
| Quote: | Thank you so much for your reply!
I have tried pointing the client to various addresses, including the pool.
The name of my pool is pool1.labs.local. It is located on a server with
FQDN which is lcs.labs.local and IP address 10.1.0.50
From the client machine, I can ping any of these names and get a proper
response. So to answer your question, the FQDN of the pool
(pool1.labs.local) resolves to 10.1.0.50. This is correct as far as I
understand.
FYI - we have a single LCS 2005 EE server setup.
I hope this may help...
Just a question - what impact will the subject name of the certificate
have
on the workings of TLS?
"Dhigha D Sekaran<msft>" wrote:
While using TLS you cannot use configure the client to point at the
server
using IP Address. you would require to point the client to the pool FQDN.
The certificate issued to the server should have the pool name as the
subject name.
With the symptoms you are that you are able to login using TCP but IM
fails
seems like the pool FQDN is not resolvable from the client.
Can you verify that please...
If the problem persists can you please post the client side logs..
To enable client side logging on a PC set the
"HKEY_CURRENT_USER\Software\Microsoft\Tracing\RTCDLL\EnableFileTracing"
registry key to 1 and then restart Windows messenger. A log file is then
created in the users %USERPROFILE%\Tracing directory (unless you
configure
another location)
--
This posting is provided "AS IS" with no warranties, and confers no
rights.
Please do not send email to this address, post a reply to this newsgroup
"Bernard" <Bernard@discussions.microsoft.com> wrote in message
news:0CD7E332-F283-4552-A3B2-F7E1673573A1@microsoft.com...
Hi there
I am unable to log into my LCS 2005 server using Windows Messanger 5.1,
and
using TLS as the protocol. I would very much appreciate it if someone
could
give me a hint on what could be wrong.
I have LCS running on a server, certificates have been installed and I
have
setup the DNS entries to be able to resolve the pool. The clients are
configured manually (I have tried setting the server to the FQDN of the
pool
and the server, and attempted to use the IP address, all resulting in
the
same error).
Here is the error I get from windows messanger:
An HTTPS or TCP connection could not be made. Please wait for your
network
administrator to correct this problem, and try again later.
The reason I am using TLS is because I am unable to send IMs if I
specify
TCP (I am, however, able to log in with TCP...)
Thanks in advance!
Bermard
|
|
|
| Back to top |
|
|
Dhigha D Sekara
Guest
|
| Posted:
Fri Jan 14, 2005 3:56 am Post subject:
Re: TLS Connection |
|
|
sorry the correct link is
http://www.microsoft.com/downloads/details.aspx?FamilyId=779DEDAA-2687-4452-901E-719CE6EC4E5A&displaylang=en
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send email to this address, post a reply to this newsgroup
"Dhigha D Sekaran<msft>" <dhigha@online.microsoft.com> wrote in message
news:u7SS4EU%23EHA.3932@TK2MSFTNGP10.phx.gbl...
| Quote: | In that case can you please capture tracing from the cleint and post it..
for details on cert configuration for LCS hope you have seen this document
Live Communications Server 2005 Document: Configuring Certificates
http://teams/sites/liveplan/Shared%20Documents/Forms/AllItems.aspx?RootFolder=%2fsites%2fliveplan%2fShared%20Documents%2fDesign%20Specifications&View=%7b6F33217F%2dE956%2d412F%2dB02C%2dD8F7DD21E286%7d
--
This posting is provided "AS IS" with no warranties, and confers no
rights.
Please do not send email to this address, post a reply to this newsgroup
"Bernard" <Bernard@discussions.microsoft.com> wrote in message
news:7171FB63-5F89-4780-A048-3BEFC623BF45@microsoft.com...
Thank you so much for your reply!
I have tried pointing the client to various addresses, including the
pool.
The name of my pool is pool1.labs.local. It is located on a server with
FQDN which is lcs.labs.local and IP address 10.1.0.50
From the client machine, I can ping any of these names and get a proper
response. So to answer your question, the FQDN of the pool
(pool1.labs.local) resolves to 10.1.0.50. This is correct as far as I
understand.
FYI - we have a single LCS 2005 EE server setup.
I hope this may help...
Just a question - what impact will the subject name of the certificate
have
on the workings of TLS?
"Dhigha D Sekaran<msft>" wrote:
While using TLS you cannot use configure the client to point at the
server
using IP Address. you would require to point the client to the pool
FQDN.
The certificate issued to the server should have the pool name as the
subject name.
With the symptoms you are that you are able to login using TCP but IM
fails
seems like the pool FQDN is not resolvable from the client.
Can you verify that please...
If the problem persists can you please post the client side logs..
To enable client side logging on a PC set the
"HKEY_CURRENT_USER\Software\Microsoft\Tracing\RTCDLL\EnableFileTracing"
registry key to 1 and then restart Windows messenger. A log file is then
created in the users %USERPROFILE%\Tracing directory (unless you
configure
another location)
--
This posting is provided "AS IS" with no warranties, and confers no
rights.
Please do not send email to this address, post a reply to this newsgroup
"Bernard" <Bernard@discussions.microsoft.com> wrote in message
news:0CD7E332-F283-4552-A3B2-F7E1673573A1@microsoft.com...
Hi there
I am unable to log into my LCS 2005 server using Windows Messanger
5.1,
and
using TLS as the protocol. I would very much appreciate it if someone
could
give me a hint on what could be wrong.
I have LCS running on a server, certificates have been installed and I
have
setup the DNS entries to be able to resolve the pool. The clients are
configured manually (I have tried setting the server to the FQDN of
the
pool
and the server, and attempted to use the IP address, all resulting in
the
same error).
Here is the error I get from windows messanger:
An HTTPS or TCP connection could not be made. Please wait for your
network
administrator to correct this problem, and try again later.
The reason I am using TLS is because I am unable to send IMs if I
specify
TCP (I am, however, able to log in with TCP...)
Thanks in advance!
Bermard
|
|
|
| Back to top |
|
|
Bernard
Guest
|
| Posted:
Fri Jan 14, 2005 12:13 pm Post subject:
Re: TLS Connection |
|
|
Thanks for the info. I'll be reading it now...
The RTC log is a bit big, must I post the whole file here?
"Dhigha D Sekaran<msft>" wrote:
| Quote: | sorry the correct link is
http://www.microsoft.com/downloads/details.aspx?FamilyId=779DEDAA-2687-4452-901E-719CE6EC4E5A&displaylang=en
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send email to this address, post a reply to this newsgroup
"Dhigha D Sekaran<msft>" <dhigha@online.microsoft.com> wrote in message
news:u7SS4EU%23EHA.3932@TK2MSFTNGP10.phx.gbl...
In that case can you please capture tracing from the cleint and post it..
for details on cert configuration for LCS hope you have seen this document
Live Communications Server 2005 Document: Configuring Certificates
http://teams/sites/liveplan/Shared%20Documents/Forms/AllItems.aspx?RootFolder=%2fsites%2fliveplan%2fShared%20Documents%2fDesign%20Specifications&View=%7b6F33217F%2dE956%2d412F%2dB02C%2dD8F7DD21E286%7d
--
This posting is provided "AS IS" with no warranties, and confers no
rights.
Please do not send email to this address, post a reply to this newsgroup
"Bernard" <Bernard@discussions.microsoft.com> wrote in message
news:7171FB63-5F89-4780-A048-3BEFC623BF45@microsoft.com...
Thank you so much for your reply!
I have tried pointing the client to various addresses, including the
pool.
The name of my pool is pool1.labs.local. It is located on a server with
FQDN which is lcs.labs.local and IP address 10.1.0.50
From the client machine, I can ping any of these names and get a proper
response. So to answer your question, the FQDN of the pool
(pool1.labs.local) resolves to 10.1.0.50. This is correct as far as I
understand.
FYI - we have a single LCS 2005 EE server setup.
I hope this may help...
Just a question - what impact will the subject name of the certificate
have
on the workings of TLS?
"Dhigha D Sekaran<msft>" wrote:
While using TLS you cannot use configure the client to point at the
server
using IP Address. you would require to point the client to the pool
FQDN.
The certificate issued to the server should have the pool name as the
subject name.
With the symptoms you are that you are able to login using TCP but IM
fails
seems like the pool FQDN is not resolvable from the client.
Can you verify that please...
If the problem persists can you please post the client side logs..
To enable client side logging on a PC set the
"HKEY_CURRENT_USER\Software\Microsoft\Tracing\RTCDLL\EnableFileTracing"
registry key to 1 and then restart Windows messenger. A log file is then
created in the users %USERPROFILE%\Tracing directory (unless you
configure
another location)
--
This posting is provided "AS IS" with no warranties, and confers no
rights.
Please do not send email to this address, post a reply to this newsgroup
"Bernard" <Bernard@discussions.microsoft.com> wrote in message
news:0CD7E332-F283-4552-A3B2-F7E1673573A1@microsoft.com...
Hi there
I am unable to log into my LCS 2005 server using Windows Messanger
5.1,
and
using TLS as the protocol. I would very much appreciate it if someone
could
give me a hint on what could be wrong.
I have LCS running on a server, certificates have been installed and I
have
setup the DNS entries to be able to resolve the pool. The clients are
configured manually (I have tried setting the server to the FQDN of
the
pool
and the server, and attempted to use the IP address, all resulting in
the
same error).
Here is the error I get from windows messanger:
An HTTPS or TCP connection could not be made. Please wait for your
network
administrator to correct this problem, and try again later.
The reason I am using TLS is because I am unable to send IMs if I
specify
TCP (I am, however, able to log in with TCP...)
Thanks in advance!
Bermard
|
|
|
| Back to top |
|
|
Dhigha D Sekara
Guest
|
| Posted:
Fri Jan 14, 2005 1:25 pm Post subject:
Re: TLS Connection |
|
|
for TLS Just the last portion where you fail to login would be good...
for TCP you can post the portion where the IM sessions are failing..
thanks, dhigha
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send email to this address, post a reply to this newsgroup
"Bernard" <Bernard@discussions.microsoft.com> wrote in message
news:CB371747-55AB-4121-B931-405AFAE7A5F6@microsoft.com...
| Quote: | Thanks for the info. I'll be reading it now...
The RTC log is a bit big, must I post the whole file here?
"Dhigha D Sekaran<msft>" wrote:
sorry the correct link is
http://www.microsoft.com/downloads/details.aspx?FamilyId=779DEDAA-2687-4452-901E-719CE6EC4E5A&displaylang=en
--
This posting is provided "AS IS" with no warranties, and confers no
rights.
Please do not send email to this address, post a reply to this newsgroup
"Dhigha D Sekaran<msft>" <dhigha@online.microsoft.com> wrote in message
news:u7SS4EU%23EHA.3932@TK2MSFTNGP10.phx.gbl...
In that case can you please capture tracing from the cleint and post
it..
for details on cert configuration for LCS hope you have seen this
document
Live Communications Server 2005 Document: Configuring Certificates
http://teams/sites/liveplan/Shared%20Documents/Forms/AllItems.aspx?RootFolder=%2fsites%2fliveplan%2fShared%20Documents%2fDesign%20Specifications&View=%7b6F33217F%2dE956%2d412F%2dB02C%2dD8F7DD21E286%7d
--
This posting is provided "AS IS" with no warranties, and confers no
rights.
Please do not send email to this address, post a reply to this
newsgroup
"Bernard" <Bernard@discussions.microsoft.com> wrote in message
news:7171FB63-5F89-4780-A048-3BEFC623BF45@microsoft.com...
Thank you so much for your reply!
I have tried pointing the client to various addresses, including the
pool.
The name of my pool is pool1.labs.local. It is located on a server
with
FQDN which is lcs.labs.local and IP address 10.1.0.50
From the client machine, I can ping any of these names and get a
proper
response. So to answer your question, the FQDN of the pool
(pool1.labs.local) resolves to 10.1.0.50. This is correct as far as I
understand.
FYI - we have a single LCS 2005 EE server setup.
I hope this may help...
Just a question - what impact will the subject name of the certificate
have
on the workings of TLS?
"Dhigha D Sekaran<msft>" wrote:
While using TLS you cannot use configure the client to point at the
server
using IP Address. you would require to point the client to the pool
FQDN.
The certificate issued to the server should have the pool name as the
subject name.
With the symptoms you are that you are able to login using TCP but IM
fails
seems like the pool FQDN is not resolvable from the client.
Can you verify that please...
If the problem persists can you please post the client side logs..
To enable client side logging on a PC set the
"HKEY_CURRENT_USER\Software\Microsoft\Tracing\RTCDLL\EnableFileTracing"
registry key to 1 and then restart Windows messenger. A log file is
then
created in the users %USERPROFILE%\Tracing directory (unless you
configure
another location)
--
This posting is provided "AS IS" with no warranties, and confers no
rights.
Please do not send email to this address, post a reply to this
newsgroup
"Bernard" <Bernard@discussions.microsoft.com> wrote in message
news:0CD7E332-F283-4552-A3B2-F7E1673573A1@microsoft.com...
Hi there
I am unable to log into my LCS 2005 server using Windows Messanger
5.1,
and
using TLS as the protocol. I would very much appreciate it if
someone
could
give me a hint on what could be wrong.
I have LCS running on a server, certificates have been installed
and I
have
setup the DNS entries to be able to resolve the pool. The clients
are
configured manually (I have tried setting the server to the FQDN of
the
pool
and the server, and attempted to use the IP address, all resulting
in
the
same error).
Here is the error I get from windows messanger:
An HTTPS or TCP connection could not be made. Please wait for your
network
administrator to correct this problem, and try again later.
The reason I am using TLS is because I am unable to send IMs if I
specify
TCP (I am, however, able to log in with TCP...)
Thanks in advance!
Bermard
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in