Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 2 replies
  • Subscribers 0 subscribers
  • Views 26729 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Go To Meeting - Being Blocked Through Sophos Web Appliance

slee

Hi Sophos Support,

I’m having issues with accessing Go To Meeting with the following error message:

A connection could not be started established. Please verify:

  • You are connected to the Internet
  • A personal firewall such as ZoneAlarm, Norton Firewall etc has blocked GoToMeeting. If so, go to your firewall program controls, unblock GoToMeeting and try again

I use the following link to test go to meeting: https://www3.gotomeeting.com/join/406552062.

I’ve done the following suggested on your KB article:

https://www.sophos.com/en-us/support/knowledgebase/110604.aspx

I’ve added the IP CIDR as suggested from Citrix in Local Site List in Sophos Web Appliance

When I turn on the Allow public IP access it works fine.  I’ve turned it off now

Do you have a solution to the issue?



This thread was automatically locked due to age.
Parents
  • 0
    The 'Allow public IP access' option is designed to stop connections where a non-private IP address appears in the URL instead of the DNS hostname/domain name. For example, "http://8.8.8.8/". It will block any requests of this type, unless the IP address is listed as Trusted.

    However, this only works where the IP address is listed in the Local Site List specifically, not as part of a CIDR range.

    This feature was originally intended as a way to prevent users substituting the IP address of a blocked site in the URL in order to get around web policy restrictions. Current web practices, including hosting multiple sites on a single server, using the HTTP1.1 Host header, along with improvements in categorization, mean that this feature is a lot less important than it used to be.

    Following the steps in the knowledge base article will ensure that GoToMeeting traffic to the IP address ranges listed by Citrix will bypass other policy and security filtering measures, which can some times get in the way. But they do not allow GoToMeeting to overcome disabling 'Allow public IP access'.

    I'm afraid the only way to make GoToMeeting work is to enable 'Allow public IP access'.
Reply
  • 0
    The 'Allow public IP access' option is designed to stop connections where a non-private IP address appears in the URL instead of the DNS hostname/domain name. For example, "http://8.8.8.8/". It will block any requests of this type, unless the IP address is listed as Trusted.

    However, this only works where the IP address is listed in the Local Site List specifically, not as part of a CIDR range.

    This feature was originally intended as a way to prevent users substituting the IP address of a blocked site in the URL in order to get around web policy restrictions. Current web practices, including hosting multiple sites on a single server, using the HTTP1.1 Host header, along with improvements in categorization, mean that this feature is a lot less important than it used to be.

    Following the steps in the knowledge base article will ensure that GoToMeeting traffic to the IP address ranges listed by Citrix will bypass other policy and security filtering measures, which can some times get in the way. But they do not allow GoToMeeting to overcome disabling 'Allow public IP access'.

    I'm afraid the only way to make GoToMeeting work is to enable 'Allow public IP access'.
Children
No Data
Unfiltered HTML