Google Meet - Network Error

[Mr_Jiminy]

 

Has anyone experienced this issue with Google Meet?

 

I have one user complaining they get booted out of Google Meet.

[BKGarry]

Is this onsite or offsite?

 

I had this before I added the ports needed into our Firewall for the networks that needed it. Used to look like it was connecting, but never show the camera and kick out after about a minute or so.

[SteveB_NI]

I have the exact same issue on our network - looks like it runs ok for several minutes but no video connection, then boots out to that.

 

I looked at the logs on PFSense (essentially what we use to connect to BT) and allowed the several ports / IP addresses it attempted to UDP too, but still no success.

 

Would be brilliant to get this working - @BKGarry - could you let me know what ports you enabled etc please, and was this done on your internet router, or Windows server?

[BKGarry]

No problems, this is our configuration for outbound traffic.

 

[SteveB_NI]

No problems, this is our configuration for outbound traffic.

 

[ATTACH=CONFIG]60647[/ATTACH]

 

Sorry if this is a silly question, but where do I input that rule? Is the firewall based within Windows Server, or our internet connection router, in this case PFSense? I've confirmed with CensorNet - our proxy server, that it's not a rule on their system

 

Thanks

[BKGarry]

This is on our router itself, we use a SophosXG for firewall and filtering. This is a firewall rule, as it is a port opening and not a filter unblock (if that makes sense)

[SteveB_NI]

This is on our router itself, we use a SophosXG for firewall and filtering. This is a firewall rule, as it is a port opening and not a filter unblock (if that makes sense)

 

Thanks - this is very strange. If I join the meet via an unfiltered Internet connection, then it works perfectly & video is transferred ok. If I switch to the proxy filtered connection, then it doesn't display video stream, and boots back to the error screen within minutes.

 

Firewall therefore doesn't seem to be stopping it, but it now appears to be filtering related. Strangely enough though nothing is showing in the filtering logs, as blocked. Arrgh!