The GoToMeeting was dead. The teacher couldn’t even be heard. What went wrong? It could be a number of things. A computer participating in a webinar can easily become too busy to perform well. Some of the relevant activity is indicated here.
In the end, we got a usable session on a different computer with a new installation of Windows and Java, a better USB headset, and wired rather than wireless peripherals. The most plausible explanation involves Policy applied to Windows by corporate IT administrators who prioritised security of data at head-office and did not optimise configurations for remote workers.
GoToMeeting was not in the service catalogue when the computer was configured. On the other hand, almost every academic will be a remote user at some time, and we must plan for teachers and learners to experiment, innovate and recover, far away and relatively independently.