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

Allow Teamviewer in Web Protection

Teamviewer used to work normally for a long time, but stopped recently. If I turn off web protection ( transparent mode ) it works. Tried every possible exception, but no go. Any ideas, anyone have similar problems ?

This thread was automatically locked due to age.

0 DouglasFoster over 5 years ago

Did you enable any Country Blocking? Teamviewer uses random servers from all over the world.
Cancel
Vote Up 0 Vote Down

Cancel
0 Alexander Busch over 5 years ago

Maybe for your information. Teamviewer performance is at its best if you allow TCP/UDP Port 5938 via Network Protection.

443 and 80 is fallback and then handled by the web protection.

See

Best

Alex

-
Cancel
Vote Up 0 Vote Down

Cancel
0 MiroslavCacija over 5 years ago in reply to DouglasFoster

No country blocking. No one have similar problems ? Teamviewer detects incoming connection, but fails to connect. Very strange, worked for years.
Cancel
Vote Up 0 Vote Down

Cancel
0 MiroslavCacija over 5 years ago in reply to Alexander Busch

Outgoing ports aren't blocked ...
Cancel
Vote Up 0 Vote Down

Cancel
0 Alexander Busch over 5 years ago in reply to MiroslavCacija

Are you using an up to date version?

Have a look in the log file.

See

Best

Alex

-
Cancel
Vote Up 0 Vote Down

Cancel
0 DouglasFoster over 5 years ago
Are you doing https inspection? I have this exception. Do not remember when or why I created it:

Description: "Work around Teamviewer SSL handshake Bug"

Action: Skip SSL Scanning and Refer to Sandstorm

For target domains ^https?://(?:[A-Za-z0-9-]+\.)+teamviewer\.com/?

I also have a Country Blocking override for port TCP 5938. If you are using Standard Mode web, you might need 5938 in the Allowed Target Services list

(Web Protection... Filtering Options... Misc (tab)
Cancel
Vote Up 0 Vote Down

Cancel
0 MiroslavCacija over 5 years ago in reply to DouglasFoster
Unfortunately I have this rule form before ...

Description: "Work around Teamviewer SSL handshake Bug"

Action: Skip SSL Scanning and Refer to Sandstorm

For target domains ^https?://(?:[A-Za-z0-9-]+\.)+teamviewer\.com/?

Country blocking is not used, and outgoing ports are not blocked. If I turn off web filtering, TV works. Nothing touched, working for a long time, just stopped working a month ago. Will try to contact support ... very strange.
Cancel
Vote Up 0 Vote Down

Cancel
0 Alexander Busch over 5 years ago in reply to MiroslavCacija

Did you made any progress?
I got a similar problem and it seems the proxy detection doesn't work well.

Best

Alex

-
Cancel
Vote Up 0 Vote Down

Cancel
0 MiroslavCacija over 5 years ago in reply to Alexander Busch

Unfortunately no progress. It was working for a long time ( with exceptions configured ), and it stopped suddenly. I will have to involve support. If I turn off web protection, it’s working.
Cancel
Vote Up 0 Vote Down

Cancel
0 ChristianBock1 over 5 years ago in reply to MiroslavCacija

Same here. We do have a GPO to force TeamViewer Client to use https by default and manual proxy w/o user.

At Web Protection, we do have RegEx for *.Teamviewer.* for any in port 80 & 443.

At Network Protection, we do have rules, allowing ping3.teamviewer.com and master1 to 16.teamviewer.com Wirth 80, 443 and the 5... mentioned above.

Did worked until this or last week.

No logs in Web Protection, but drops to IPs at Network Protection which are not covered by known hostnames of Teamviewer.

Maybe they have changed there hostnames and/or IPs.
Cancel
Vote Up 0 Vote Down

Cancel