Hi All,

I am having problems accessing live meeting on my mac.  (It was working). 

I can activate a live meeting, and the additional screen is activated that says 'Welcome to Microsoft Office Live Meeting Web Access'... 'Downloading web console....' and it hangs there.  I do get before the pop-up screen the security java check, which I authorise the running of the app... but it will not connect to the meeting (the downloading web console...' just keep progressing..

I am on the latest version of Java 7.45 and 10.9.1 of OSX. 

Any ideas ??

Thanks

Not for me. I am trying this in Firefox on MacOSX, have Java 1.7_u51, and it gives me the "downloading web console" pane, forever. For a long time anyway.  I've waited 10 minutes and that's not enough. There's no apparent progress, no way that I can see to evaluate whether it is really downloading or is just stuck. 

any hints?

I had similar issues today and resolved by performing the following:

1) From Java Preferences - go to the Advanced Tab, enable - hide warning and run with protections, under Sandbox vs trusted security option.

2) Under the Security tab in Java, added the livemeeting and fwd137 livemeeting sites to the Exception site list.

I'm running OS X - 10.9.1 and Java 7 update 51 (build 1.7.0_51-b13).

Good luck!

Thanks for the tip.  I tried your suggestion, still no joy. 

OS X - 10.9.1 and Java 7 update 51 (build 1.7.0_51-b13).

I don't know what to try, or how to diagnose this.

I tried hooking the browser up to a debugging proxy, I can see the request go out for

https://fwd125.livemeeting.com/etc/fwd/ca1yanpws001.rtc.local$9003/pod/4AE62002-3DC2-58E4-B118-2284EEEA4821/console.html

That request returns with a 200.  Then there is a request to

https://fwd125.livemeeting.com/etc/fwd/ca1yanpws001.rtc.local$9003/pod/4AE62002-3DC2-58E4-B118-2284EEEA4821/main.html

also successful (200). Then a request for

https://fwd125.livemeeting.com/etc/fwd/ca1yanpws001.rtc.local$9003/pod/4AE62002-3DC2-58E4-B118-2284EEEA4821/extMain.js

also successful.  then no more requests, nothing further happens. The next step on this diagnostic journey is to debug the extMain.js code.  This is ridiculous.

On IE, I can see a bunch of subsequent requests - for secondary.html, newarea.html, url-leap, extSecondary.js, slidearea.html and so on. The Firefox on Mac does not send those requests out.

• Edited by cheeso Thursday, January 30, 2014 11:16 PM

Thanks for the tip.  I tried your suggestion, still no joy. 

OS X - 10.9.1 and Java 7 update 51 (build 1.7.0_51-b13).

I don't know what to try, or how to diagnose this.

I tried hooking the browser up to a debugging proxy, I can see the request go out for

https://fwd125.livemeeting.com/etc/fwd/ca1yanpws001.rtc.local$9003/pod/4AE62002-3DC2-58E4-B118-2284EEEA4821/console.html

That request returns with a 200.  Then there is a request to

https://fwd125.livemeeting.com/etc/fwd/ca1yanpws001.rtc.local$9003/pod/4AE62002-3DC2-58E4-B118-2284EEEA4821/main.html

also successful (200). Then a request for

https://fwd125.livemeeting.com/etc/fwd/ca1yanpws001.rtc.local$9003/pod/4AE62002-3DC2-58E4-B118-2284EEEA4821/extMain.js

also successful.  then no more requests, nothing further happens. The next step on this diagnostic journey is to debug the extMain.js code.  This is ridiculous.

On IE, I can see a bunch of subsequent requests - for secondary.html, newarea.html, url-leap, extSecondary.js, slidearea.html and so on. The Firefox on Mac does not send those requests out.

• Edited by cheeso Thursday, January 30, 2014 11:16 PM

Thanks for the tip.  I tried your suggestion, still no joy. 

OS X - 10.9.1 and Java 7 update 51 (build 1.7.0_51-b13).

I don't know what to try, or how to diagnose this.

I tried hooking the browser up to a debugging proxy, I can see the request go out for

https://fwd125.livemeeting.com/etc/fwd/ca1yanpws001.rtc.local$9003/pod/4AE62002-3DC2-58E4-B118-2284EEEA4821/console.html

That request returns with a 200.  Then there is a request to

https://fwd125.livemeeting.com/etc/fwd/ca1yanpws001.rtc.local$9003/pod/4AE62002-3DC2-58E4-B118-2284EEEA4821/main.html

also successful (200). Then a request for

https://fwd125.livemeeting.com/etc/fwd/ca1yanpws001.rtc.local$9003/pod/4AE62002-3DC2-58E4-B118-2284EEEA4821/extMain.js

also successful.  then no more requests, nothing further happens. The next step on this diagnostic journey is to debug the extMain.js code.  This is ridiculous.

On IE, I can see a bunch of subsequent requests - for secondary.html, newarea.html, url-leap, extSecondary.js, slidearea.html and so on. The Firefox on Mac does not send those requests out.

• Edited by cheeso Thursday, January 30, 2014 11:16 PM

Thanks for the tip.  I tried your suggestion, still no joy. 

OS X - 10.9.1 and Java 7 update 51 (build 1.7.0_51-b13).

I don't know what to try, or how to diagnose this.

I tried hooking the browser up to a debugging proxy, I can see the request go out for

https://fwd125.livemeeting.com/etc/fwd/ca1yanpws001.rtc.local$9003/pod/4AE62002-3DC2-58E4-B118-2284EEEA4821/console.html

That request returns with a 200.  Then there is a request to

https://fwd125.livemeeting.com/etc/fwd/ca1yanpws001.rtc.local$9003/pod/4AE62002-3DC2-58E4-B118-2284EEEA4821/main.html

also successful (200). Then a request for

https://fwd125.livemeeting.com/etc/fwd/ca1yanpws001.rtc.local$9003/pod/4AE62002-3DC2-58E4-B118-2284EEEA4821/extMain.js

also successful.  then no more requests, nothing further happens. The next step on this diagnostic journey is to debug the extMain.js code.  This is ridiculous.

On IE, I can see a bunch of subsequent requests - for secondary.html, newarea.html, url-leap, extSecondary.js, slidearea.html and so on. The Firefox on Mac does not send those requests out.

• Edited by cheeso Thursday, January 30, 2014 11:16 PM

Thanks for the tip.  I tried your suggestion, still no joy. 

OS X - 10.9.1 and Java 7 update 51 (build 1.7.0_51-b13).

I don't know what to try, or how to diagnose this.

I tried hooking the browser up to a debugging proxy, I can see the request go out for

https://fwd125.livemeeting.com/etc/fwd/ca1yanpws001.rtc.local$9003/pod/4AE62002-3DC2-58E4-B118-2284EEEA4821/console.html

That request returns with a 200.  Then there is a request to

https://fwd125.livemeeting.com/etc/fwd/ca1yanpws001.rtc.local$9003/pod/4AE62002-3DC2-58E4-B118-2284EEEA4821/main.html

also successful (200). Then a request for

https://fwd125.livemeeting.com/etc/fwd/ca1yanpws001.rtc.local$9003/pod/4AE62002-3DC2-58E4-B118-2284EEEA4821/extMain.js

also successful.  then no more requests, nothing further happens. The next step on this diagnostic journey is to debug the extMain.js code.  This is ridiculous.

On IE, I can see a bunch of subsequent requests - for secondary.html, newarea.html, url-leap, extSecondary.js, slidearea.html and so on. The Firefox on Mac does not send those requests out.

• Edited by cheeso Thursday, January 30, 2014 11:16 PM

Thanks for the tip.  I tried your suggestion, still no joy. 

OS X - 10.9.1 and Java 7 update 51 (build 1.7.0_51-b13).

I don't know what to try, or how to diagnose this.

I tried hooking the browser up to a debugging proxy, I can see the request go out for

https://fwd125.livemeeting.com/etc/fwd/ca1yanpws001.rtc.local$9003/pod/4AE62002-3DC2-58E4-B118-2284EEEA4821/console.html

That request returns with a 200.  Then there is a request to

https://fwd125.livemeeting.com/etc/fwd/ca1yanpws001.rtc.local$9003/pod/4AE62002-3DC2-58E4-B118-2284EEEA4821/main.html

also successful (200). Then a request for

https://fwd125.livemeeting.com/etc/fwd/ca1yanpws001.rtc.local$9003/pod/4AE62002-3DC2-58E4-B118-2284EEEA4821/extMain.js

also successful.  then no more requests, nothing further happens. The next step on this diagnostic journey is to debug the extMain.js code.  This is ridiculous.

On IE, I can see a bunch of subsequent requests - for secondary.html, newarea.html, url-leap, extSecondary.js, slidearea.html and so on. The Firefox on Mac does not send those requests out.

• Edited by cheeso Thursday, January 30, 2014 11:16 PM

Thanks for the tip.  I tried your suggestion, still no joy. 

OS X - 10.9.1 and Java 7 update 51 (build 1.7.0_51-b13).

I don't know what to try, or how to diagnose this.

I tried hooking the browser up to a debugging proxy, I can see the request go out for

https://fwd125.livemeeting.com/etc/fwd/ca1yanpws001.rtc.local$9003/pod/4AE62002-3DC2-58E4-B118-2284EEEA4821/console.html

That request returns with a 200.  Then there is a request to

https://fwd125.livemeeting.com/etc/fwd/ca1yanpws001.rtc.local$9003/pod/4AE62002-3DC2-58E4-B118-2284EEEA4821/main.html

also successful (200). Then a request for

https://fwd125.livemeeting.com/etc/fwd/ca1yanpws001.rtc.local$9003/pod/4AE62002-3DC2-58E4-B118-2284EEEA4821/extMain.js

also successful.  then no more requests, nothing further happens. The next step on this diagnostic journey is to debug the extMain.js code.  This is ridiculous.

On IE, I can see a bunch of subsequent requests - for secondary.html, newarea.html, url-leap, extSecondary.js, slidearea.html and so on. The Firefox on Mac does not send those requests out.

• Edited by cheeso Thursday, January 30, 2014 11:16 PM

Thanks for the tip.  I tried your suggestion, still no joy. 

OS X - 10.9.1 and Java 7 update 51 (build 1.7.0_51-b13).

I don't know what to try, or how to diagnose this.

I tried hooking the browser up to a debugging proxy, I can see the request go out for

https://fwd125.livemeeting.com/etc/fwd/ca1yanpws001.rtc.local$9003/pod/4AE62002-3DC2-58E4-B118-2284EEEA4821/console.html

That request returns with a 200.  Then there is a request to

https://fwd125.livemeeting.com/etc/fwd/ca1yanpws001.rtc.local$9003/pod/4AE62002-3DC2-58E4-B118-2284EEEA4821/main.html

also successful (200). Then a request for

https://fwd125.livemeeting.com/etc/fwd/ca1yanpws001.rtc.local$9003/pod/4AE62002-3DC2-58E4-B118-2284EEEA4821/extMain.js

also successful.  then no more requests, nothing further happens. The next step on this diagnostic journey is to debug the extMain.js code.  This is ridiculous.

On IE, I can see a bunch of subsequent requests - for secondary.html, newarea.html, url-leap, extSecondary.js, slidearea.html and so on. The Firefox on Mac does not send those requests out.

• Edited by cheeso Thursday, January 30, 2014 11:16 PM

Thanks for the tip.  I tried your suggestion, still no joy. 

OS X - 10.9.1 and Java 7 update 51 (build 1.7.0_51-b13).

I don't know what to try, or how to diagnose this.

I tried hooking the browser up to a debugging proxy, I can see the request go out for

https://fwd125.livemeeting.com/etc/fwd/ca1yanpws001.rtc.local$9003/pod/4AE62002-3DC2-58E4-B118-2284EEEA4821/console.html

That request returns with a 200.  Then there is a request to

https://fwd125.livemeeting.com/etc/fwd/ca1yanpws001.rtc.local$9003/pod/4AE62002-3DC2-58E4-B118-2284EEEA4821/main.html

also successful (200). Then a request for

https://fwd125.livemeeting.com/etc/fwd/ca1yanpws001.rtc.local$9003/pod/4AE62002-3DC2-58E4-B118-2284EEEA4821/extMain.js

also successful.  then no more requests, nothing further happens. The next step on this diagnostic journey is to debug the extMain.js code.  This is ridiculous.

On IE, I can see a bunch of subsequent requests - for secondary.html, newarea.html, url-leap, extSecondary.js, slidearea.html and so on. The Firefox on Mac does not send those requests out.

• Edited by cheeso Thursday, January 30, 2014 11:16 PM

Thanks for the tip.  I tried your suggestion, still no joy. 

OS X - 10.9.1 and Java 7 update 51 (build 1.7.0_51-b13).

I don't know what to try, or how to diagnose this.

I tried hooking the browser up to a debugging proxy, I can see the request go out for

https://fwd125.livemeeting.com/etc/fwd/ca1yanpws001.rtc.local$9003/pod/4AE62002-3DC2-58E4-B118-2284EEEA4821/console.html

That request returns with a 200.  Then there is a request to

https://fwd125.livemeeting.com/etc/fwd/ca1yanpws001.rtc.local$9003/pod/4AE62002-3DC2-58E4-B118-2284EEEA4821/main.html

also successful (200). Then a request for

https://fwd125.livemeeting.com/etc/fwd/ca1yanpws001.rtc.local$9003/pod/4AE62002-3DC2-58E4-B118-2284EEEA4821/extMain.js

also successful.  then no more requests, nothing further happens. The next step on this diagnostic journey is to debug the extMain.js code.  This is ridiculous.

On IE, I can see a bunch of subsequent requests - for secondary.html, newarea.html, url-leap, extSecondary.js, slidearea.html and so on. The Firefox on Mac does not send those requests out.

• Edited by cheeso Thursday, January 30, 2014 11:16 PM

Thanks for the tip.  I tried your suggestion, still no joy. 

OS X - 10.9.1 and Java 7 update 51 (build 1.7.0_51-b13).

I don't know what to try, or how to diagnose this.

I tried hooking the browser up to a debugging proxy, I can see the request go out for

https://fwd125.livemeeting.com/etc/fwd/ca1yanpws001.rtc.local$9003/pod/4AE62002-3DC2-58E4-B118-2284EEEA4821/console.html

That request returns with a 200.  Then there is a request to

https://fwd125.livemeeting.com/etc/fwd/ca1yanpws001.rtc.local$9003/pod/4AE62002-3DC2-58E4-B118-2284EEEA4821/main.html

also successful (200). Then a request for

https://fwd125.livemeeting.com/etc/fwd/ca1yanpws001.rtc.local$9003/pod/4AE62002-3DC2-58E4-B118-2284EEEA4821/extMain.js

also successful.  then no more requests, nothing further happens. The next step on this diagnostic journey is to debug the extMain.js code.  This is ridiculous.

On IE, I can see a bunch of subsequent requests - for secondary.html, newarea.html, url-leap, extSecondary.js, slidearea.html and so on. The Firefox on Mac does not send those requests out.

• Edited by cheeso Thursday, January 30, 2014 11:16 PM

Thanks for the tip.  I tried your suggestion, still no joy. 

OS X - 10.9.1 and Java 7 update 51 (build 1.7.0_51-b13).

I don't know what to try, or how to diagnose this.

I tried hooking the browser up to a debugging proxy, I can see the request go out for

https://fwd125.livemeeting.com/etc/fwd/ca1yanpws001.rtc.local$9003/pod/4AE62002-3DC2-58E4-B118-2284EEEA4821/console.html

That request returns with a 200.  Then there is a request to

https://fwd125.livemeeting.com/etc/fwd/ca1yanpws001.rtc.local$9003/pod/4AE62002-3DC2-58E4-B118-2284EEEA4821/main.html

also successful (200). Then a request for

https://fwd125.livemeeting.com/etc/fwd/ca1yanpws001.rtc.local$9003/pod/4AE62002-3DC2-58E4-B118-2284EEEA4821/extMain.js

also successful.  then no more requests, nothing further happens. The next step on this diagnostic journey is to debug the extMain.js code.  This is ridiculous.

On IE, I can see a bunch of subsequent requests - for secondary.html, newarea.html, url-leap, extSecondary.js, slidearea.html and so on. The Firefox on Mac does not send those requests out.

• Edited by cheeso Thursday, January 30, 2014 11:16 PM

Thanks for the tip.  I tried your suggestion, still no joy. 

OS X - 10.9.1 and Java 7 update 51 (build 1.7.0_51-b13).

I don't know what to try, or how to diagnose this.

I tried hooking the browser up to a debugging proxy, I can see the request go out for

https://fwd125.livemeeting.com/etc/fwd/ca1yanpws001.rtc.local$9003/pod/4AE62002-3DC2-58E4-B118-2284EEEA4821/console.html

That request returns with a 200.  Then there is a request to

https://fwd125.livemeeting.com/etc/fwd/ca1yanpws001.rtc.local$9003/pod/4AE62002-3DC2-58E4-B118-2284EEEA4821/main.html

also successful (200). Then a request for

https://fwd125.livemeeting.com/etc/fwd/ca1yanpws001.rtc.local$9003/pod/4AE62002-3DC2-58E4-B118-2284EEEA4821/extMain.js

also successful.  then no more requests, nothing further happens. The next step on this diagnostic journey is to debug the extMain.js code.  This is ridiculous.

On IE, I can see a bunch of subsequent requests - for secondary.html, newarea.html, url-leap, extSecondary.js, slidearea.html and so on. The Firefox on Mac does not send those requests out.

• Edited by cheeso Thursday, January 30, 2014 11:16 PM

No luck for me either. :(

In Firefox it does not even get that far for me as in Safari ("Downloading Web console...").

OS X 10.8.5 / Java 7 update 51 (build 1.7.0_51-b13) / Safari Version 6.1.1 (8537.73.11)

• Proposed as answer by Brit Pack Wednesday, February 05, 2014 9:55 AM
• Unproposed as answer by Brit Pack Wednesday, February 05, 2014 9:55 AM

No luck for me either. :(

In Firefox it does not even get that far for me as in Safari ("Downloading Web console...").

OS X 10.8.5 / Java 7 update 51 (build 1.7.0_51-b13) / Safari Version 6.1.1 (8537.73.11)

• Proposed as answer by Brit Pack Wednesday, February 05, 2014 9:55 AM
• Unproposed as answer by Brit Pack Wednesday, February 05, 2014 9:55 AM

No luck for me either. :(

In Firefox it does not even get that far for me as in Safari ("Downloading Web console...").

OS X 10.8.5 / Java 7 update 51 (build 1.7.0_51-b13) / Safari Version 6.1.1 (8537.73.11)

• Proposed as answer by Brit Pack Wednesday, February 05, 2014 9:55 AM
• Unproposed as answer by Brit Pack Wednesday, February 05, 2014 9:55 AM

No luck for me either. :(

In Firefox it does not even get that far for me as in Safari ("Downloading Web console...").

OS X 10.8.5 / Java 7 update 51 (build 1.7.0_51-b13) / Safari Version 6.1.1 (8537.73.11)

• Proposed as answer by Brit Pack Wednesday, February 05, 2014 9:55 AM
• Unproposed as answer by Brit Pack Wednesday, February 05, 2014 9:55 AM

No luck for me either. :(

In Firefox it does not even get that far for me as in Safari ("Downloading Web console...").

OS X 10.8.5 / Java 7 update 51 (build 1.7.0_51-b13) / Safari Version 6.1.1 (8537.73.11)

• Proposed as answer by Brit Pack Wednesday, February 05, 2014 9:55 AM
• Unproposed as answer by Brit Pack Wednesday, February 05, 2014 9:55 AM

No luck for me either. :(

In Firefox it does not even get that far for me as in Safari ("Downloading Web console...").

OS X 10.8.5 / Java 7 update 51 (build 1.7.0_51-b13) / Safari Version 6.1.1 (8537.73.11)

• Proposed as answer by Brit Pack Wednesday, February 05, 2014 9:55 AM
• Unproposed as answer by Brit Pack Wednesday, February 05, 2014 9:55 AM

No luck for me either. :(

In Firefox it does not even get that far for me as in Safari ("Downloading Web console...").

OS X 10.8.5 / Java 7 update 51 (build 1.7.0_51-b13) / Safari Version 6.1.1 (8537.73.11)

• Proposed as answer by Brit Pack Wednesday, February 05, 2014 9:55 AM
• Unproposed as answer by Brit Pack Wednesday, February 05, 2014 9:55 AM

No luck for me either. :(

In Firefox it does not even get that far for me as in Safari ("Downloading Web console...").

OS X 10.8.5 / Java 7 update 51 (build 1.7.0_51-b13) / Safari Version 6.1.1 (8537.73.11)

• Proposed as answer by Brit Pack Wednesday, February 05, 2014 9:55 AM
• Unproposed as answer by Brit Pack Wednesday, February 05, 2014 9:55 AM

No luck for me either. :(

In Firefox it does not even get that far for me as in Safari ("Downloading Web console...").

OS X 10.8.5 / Java 7 update 51 (build 1.7.0_51-b13) / Safari Version 6.1.1 (8537.73.11)

• Proposed as answer by Brit Pack Wednesday, February 05, 2014 9:55 AM
• Unproposed as answer by Brit Pack Wednesday, February 05, 2014 9:55 AM

No luck for me either. :(

In Firefox it does not even get that far for me as in Safari ("Downloading Web console...").

OS X 10.8.5 / Java 7 update 51 (build 1.7.0_51-b13) / Safari Version 6.1.1 (8537.73.11)

• Proposed as answer by Brit Pack Wednesday, February 05, 2014 9:55 AM
• Unproposed as answer by Brit Pack Wednesday, February 05, 2014 9:55 AM

No luck for me either. :(

In Firefox it does not even get that far for me as in Safari ("Downloading Web console...").

OS X 10.8.5 / Java 7 update 51 (build 1.7.0_51-b13) / Safari Version 6.1.1 (8537.73.11)

• Proposed as answer by Brit Pack Wednesday, February 05, 2014 9:55 AM
• Unproposed as answer by Brit Pack Wednesday, February 05, 2014 9:55 AM

No luck for me either. :(

In Firefox it does not even get that far for me as in Safari ("Downloading Web console...").

OS X 10.8.5 / Java 7 update 51 (build 1.7.0_51-b13) / Safari Version 6.1.1 (8537.73.11)

• Proposed as answer by Brit Pack Wednesday, February 05, 2014 9:55 AM
• Unproposed as answer by Brit Pack Wednesday, February 05, 2014 9:55 AM

No luck for me either. :(

In Firefox it does not even get that far for me as in Safari ("Downloading Web console...").

OS X 10.8.5 / Java 7 update 51 (build 1.7.0_51-b13) / Safari Version 6.1.1 (8537.73.11)

• Proposed as answer by Brit Pack Wednesday, February 05, 2014 9:55 AM
• Unproposed as answer by Brit Pack Wednesday, February 05, 2014 9:55 AM

I feel stupid as well Brit Pack but... THANK YOU, I was very frustrated that I had to use a Windows VM each time to connect to these meetings but clicking on the "lego" brick indeed solved it for me under firefox as well!!

Would have been nice if they made it a bit more clear though :-)

• Edited by noki-online Wednesday, March 05, 2014 8:46 AM

I feel stupid as well Brit Pack but... THANK YOU, I was very frustrated that I had to use a Windows VM each time to connect to these meetings but clicking on the "lego" brick indeed solved it for me under firefox as well!!

Would have been nice if they made it a bit more clear though :-)

• Edited by noki-online Wednesday, March 05, 2014 8:46 AM

I feel stupid as well Brit Pack but... THANK YOU, I was very frustrated that I had to use a Windows VM each time to connect to these meetings but clicking on the "lego" brick indeed solved it for me under firefox as well!!

Would have been nice if they made it a bit more clear though :-)

• Edited by noki-online Wednesday, March 05, 2014 8:46 AM

I feel stupid as well Brit Pack but... THANK YOU, I was very frustrated that I had to use a Windows VM each time to connect to these meetings but clicking on the "lego" brick indeed solved it for me under firefox as well!!

Would have been nice if they made it a bit more clear though :-)

• Edited by noki-online Wednesday, March 05, 2014 8:46 AM

I feel stupid as well Brit Pack but... THANK YOU, I was very frustrated that I had to use a Windows VM each time to connect to these meetings but clicking on the "lego" brick indeed solved it for me under firefox as well!!

Would have been nice if they made it a bit more clear though :-)

• Edited by noki-online Wednesday, March 05, 2014 8:46 AM

I feel stupid as well Brit Pack but... THANK YOU, I was very frustrated that I had to use a Windows VM each time to connect to these meetings but clicking on the "lego" brick indeed solved it for me under firefox as well!!

Would have been nice if they made it a bit more clear though :-)

• Edited by noki-online Wednesday, March 05, 2014 8:46 AM

I feel stupid as well Brit Pack but... THANK YOU, I was very frustrated that I had to use a Windows VM each time to connect to these meetings but clicking on the "lego" brick indeed solved it for me under firefox as well!!

Would have been nice if they made it a bit more clear though :-)

• Edited by noki-online Wednesday, March 05, 2014 8:46 AM

I feel stupid as well Brit Pack but... THANK YOU, I was very frustrated that I had to use a Windows VM each time to connect to these meetings but clicking on the "lego" brick indeed solved it for me under firefox as well!!

Would have been nice if they made it a bit more clear though :-)

• Edited by noki-online Wednesday, March 05, 2014 8:46 AM

I feel stupid as well Brit Pack but... THANK YOU, I was very frustrated that I had to use a Windows VM each time to connect to these meetings but clicking on the "lego" brick indeed solved it for me under firefox as well!!

Would have been nice if they made it a bit more clear though :-)

• Edited by noki-online Wednesday, March 05, 2014 8:46 AM

I feel stupid as well Brit Pack but... THANK YOU, I was very frustrated that I had to use a Windows VM each time to connect to these meetings but clicking on the "lego" brick indeed solved it for me under firefox as well!!

Would have been nice if they made it a bit more clear though :-)

• Edited by noki-online Wednesday, March 05, 2014 8:46 AM

I feel stupid as well Brit Pack but... THANK YOU, I was very frustrated that I had to use a Windows VM each time to connect to these meetings but clicking on the "lego" brick indeed solved it for me under firefox as well!!

Would have been nice if they made it a bit more clear though :-)

• Edited by noki-online Wednesday, March 05, 2014 8:46 AM

I feel stupid as well Brit Pack but... THANK YOU, I was very frustrated that I had to use a Windows VM each time to connect to these meetings but clicking on the "lego" brick indeed solved it for me under firefox as well!!

Would have been nice if they made it a bit more clear though :-)

• Edited by noki-online Wednesday, March 05, 2014 8:46 AM

I feel stupid as well Brit Pack but... THANK YOU, I was very frustrated that I had to use a Windows VM each time to connect to these meetings but clicking on the "lego" brick indeed solved it for me under firefox as well!!

Would have been nice if they made it a bit more clear though :-)

• Edited by noki-online Wednesday, March 05, 2014 8:46 AM

It worked for me. A big thanks. 

Cheers