@TheVacationStop You are probably correct with your firewall theory: https://support.logmeininc.com/gotomeeting/help/how-do-i-configure-gotomeeting-to-work-with-firewall...
If the desktop and web interface both fail, then it's going to be your local firewall that needs adjustment.
Likely our network firewall, not one on the PC. I've read the firewall docs, and I've given them to our IT staff but haven't heard back yet. It would be nice though, to understand why there is a difference between a real webinar and hte test webinar, and what those differences are. That would make it easier to make the firewall adjustments.
@TheVacationStop Typically a real webinar requires round trip communication, i.e. Inbound and Outbound traffic. Also, each GoToWebinar you join may vary in IP address, connecting through one of the server IP blocks on that firewall document.
The test meeting tests if you meet our system requirements and if you can complete the join process successfully of connecting to our server and downloading the software, for the majority of attendees that is enough. For some more restrictive environments taking part in a live meeting/webinar is the only real way to confirm.
client_type=html5 apparently is no longer supported.
Will Logmein ever support a system that uses only https: and the standard ports?
If not, I will continue to recommend other services that do.
@mencik Can you explain what you mean by "standard ports"? We currently utilize industry standards that can connect through one of 3 available ports: 80, 443 and 8200.
I have no such problems with webcasts.com or on24.com among others. I can join all their webcasts via browser only. gotowebinar.com is the only webcast platform that does not work in my environment, as it is using something non-standard that our firewall blocks. I have no control over that firewall.
You can run the advanced options with the GoTo Connection Wizard, and select to force port 443: https://support.goto.com/meeting/help/install-and-run-the-connection-wizard-windows