Answered by:
an other Live-meeting Connection failure

Question
-
Hi
I have setup a standard edition server.1 front , 1edge, 1Web server, 1Isa reverse proxy. Every thing is working find internally, from exterior communicator working perfectly, but I have a big problem with Live-meeting console from exterior.
I have correctly set the permissions for external users so my live meeting interface has the meet now button in its interfaces.
But when I try to create a meeting with a meet now button I have the following error on my Live-meeting:
Live meeting cannot connect to the meeting.
Wait a few moments, then try to join the meeting again.
If you still cannot connect, contact your administrator or technical support.
Error on edge server :
Over the past 23 minutes Office Communication Server has disconnected clients 1 time(s) as a result of invalid data being received on client connections. The last such client which was disconnected is “84.102.242.129:1244”.
Cause: Failed to process data received from the client
Resolution:
Check and make sure that the connection came from a trustworthy client.
Error in PWconsole (clien) :
SslSocket::connect end OK
[MC] 16:43:03:574 GMT [THREAD 2284]
TunnelSocket::connect ProxyHeader sent.
[MC] 16:43:03:574 GMT [THREAD 2284]
SSLTunnelStream: Established SSL Tunnel Stream to mocs.exakis.com
[MC] 16:43:03:574 GMT [THREAD 2284]
Forwarded TCP probe succeeded
[MC] 16:43:03:574 GMT [THREAD 3004]
Best mode for Client RPC is : 1
[MC] 16:43:03:574 GMT [THREAD 3004]
Best mode is fwdtls. Reusing stream in probe.
[MC] 16:43:03:589 GMT [THREAD 2564]
PWS Handshake sent.
[MC] 16:43:03:667 GMT [THREAD 1228]
Error reading data. ErrCode = 10054
[MC] 16:43:03:714 GMT [THREAD 1228]
Socket error while reading.
[MC] 16:43:03:746 GMT [THREAD 1228]
SslSocket::close: socket is not connected
[MC] 16:43:03:808 GMT [THREAD 1228]
PWException being thrown: placeware:
WException: Invalid handshake response from server
Does somebody have an idea?
Thanks
Tuesday, April 24, 2007 7:39 AM
Answers
-
Finally
I remember checking the clock on my servers many times, but not the Time zone.
The problem was coming from a bad time zone on my Edge server, which create a time referential issue.
Wednesday, April 25, 2007 8:18 AM
All replies
-
Finally
I remember checking the clock on my servers many times, but not the Time zone.
The problem was coming from a bad time zone on my Edge server, which create a time referential issue.
Wednesday, April 25, 2007 8:18 AM -
Your saying switching the time zone fixed your issue? I am having the same issue with External Web Conferencing, but its not a time zone problem.. I to have configured everything and have gone over the config about a hundred times, but I still get the same error as you... What did you use to pull the connection attempts.. LM log??
Friday, September 21, 2007 4:48 PM -
Hi sorry for the delay.
Yes I Use the LM log By ennable log with the corect registration Key I don't remenber it exactly but I foud it in the Beta forum.
Good luck
Edit: I foud it :
[HKEY_CURRENT_USER\Software\Microsoft\Tracing\uccp\
LiveMeeting]"EnableFileTracing"= DWORD:00000001
"Tracing"= DWORD:00000001
It is in OCS_Console_Deployment_Guide.doc
Thursday, October 11, 2007 4:11 PM -
Any update on this? I am seeing the same error on my edge server when try to connect an external LM session.
ThanksThursday, October 25, 2007 7:31 PM -
Hi JCPC
Could you give us more details on your error please ?
If it was the same proble as mine checking clock and time zone on each computeurs should have been enough.
Aparently it's not the same probleme.
Monday, November 5, 2007 11:03 AM