cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
New Contributor

Gotomeeting Not screen sharing

I was in a Meeting, I screen shared to user 1, He shared and we could see his screen. Later I tried to Share to user 2, nothing happened when I made him presenter, the original presenter remained the Presenter. Then that same user (user1) was able to allow user 2 to to share his screen with User 1, I I as the moderator never saw the screen. I cant speak to what happened there, but why does gotomeeting completely stop responding to commands, I could no longer swich presenters, and when I shared my screen, It did not share with anyone else and it still showed user1 as the presenter. I had to End the session, then kill the gotomeeing task via Task manager (Because it wont end the session otherwise) Start a new session, Share one screen and then repeat whole process over.

 

This started happening yesterday after a reboot. No new Updates were installed @ reboot (No win updates at least)

 

Please advise

3 REPLIES 3
LogMeIn Contributor

Re: Gotomeeting Not screen sharing

Hi @c0rwin007 ,

I'm afraid it's difficult to say why GoToMeeting became unresponsive without looking into the local log files there.

 

If you can help us understand the environmental factors such as the affected operating system, internet connection type, and GoToMeeting version, then we can also try recreating the issue internally.  Anything other hardware being utilized like a wireless mouse or external displays can be variables too. It would also help to know how your attendees were connected, through which devices or web browsers.

 

New Contributor

Re: Gotomeeting Not screen sharing

Im using a windows 10 PC, and have been for a couple of years, This just started happening after the recent Gotomeeting update. I have since uninstalled the Program and Reinstalled to no avail. Looking at your logs I see this at the bottom: 

 

2020-01-27 15:53:25.211 PST d: [g2mcomm] <15896/IINet.probe_0X3E18> Probe connect: Connect timeout
2020-01-27 15:53:25.211 PST d: [g2mcomm] <15896/IINet.probe_0X3E18> sockets::jinet::JConnectBinderBase::handleConnectionFailed() - connect failure, code=2024
2020-01-27 15:53:25.211 PST d: [g2mcomm] <15896/IINet.probe_0X3E18> Probe:Smiley Tonguerobe: Connect failed for target: 173.199.0.254:80,443,8200
2020-01-27 15:53:25.211 PST d: [g2mlauncher] <Probe_20> ProbeManager:Smiley TonguerobeThread:Smiley Tonguerobe::run() - probe returned error (173.199.0.254:80,443,8200).
(2010) "ECError::eIOError"
Error returned at , inetipcadapter.cpp:346
Error returned at , inetipcproxy.cpp:258
2020-01-27 15:53:27.212 PST d: [g2mcomm] <15896/IINet.probe_0X3E18> Probe connect: Start connect to 173.199.0.254
2020-01-27 15:53:47.224 PST d: [g2mcomm] <15896/IINet.probe_0X3E18> sockets::jscheduler::JTimedTaskScheduler::TimedTask::logFireDetails() - Due time: 1580169227212, present: 1580169227224
2020-01-27 15:53:47.224 PST d: [g2mcomm] <15896/IINet.probe_0X3E18> Probe connect: Connect timeout
2020-01-27 15:53:47.224 PST d: [g2mcomm] <15896/IINet.probe_0X3E18> sockets::jinet::JConnectBinderBase::handleConnectionFailed() - connect failure, code=2024
2020-01-27 15:53:47.224 PST d: [g2mcomm] <15896/IINet.probe_0X3E18> Probe:Smiley Tonguerobe: Connect failed for target: 173.199.0.254:80,443,8200
2020-01-27 15:53:47.224 PST d: [g2mlauncher] <Probe_20> ProbeManager:Smiley TonguerobeThread:Smiley Tonguerobe::run() - probe returned error on retry (173.199.0.254:80,443,8200). Aborting.
(2010) "ECError::eIOError"
Error returned at , inetipcadapter.cpp:346
Error returned at , inetipcproxy.cpp:258

LogMeIn Contributor

Re: Gotomeeting Not screen sharing

I don't see anything here that would cause that behavior.

 

If you are still able to reproduce this failure on demand, then I would ask that you call into Customer Support at your convenience so we can fully document the environmental factors:  https://support.goto.com/meeting/help/how-do-i-contact-gotomeeting-customer-support-g2m090151