Whitelisting for updating TeamViewer over a Proxy

JohnGuy
JohnGuy Posts: 3
in General questions

Hello, I was wondering if anyone could tell me what addresses I need to whitelist in order for TeamViewer to be able to update itself.

Let me explain.

We have a good number of computers, deployed at multiple locations, that are on very locked down networks. In order for us to be able to use TeamViewer and provide remote assistance, we have TeamViewer going through a proxy. This works like a dream, and we are very happy with it.

However, that proxy is also locked down, so that only certain things can be accessed through it. And it seems like we don't have the right stuff whitelisted in order for TeamViewer to update itself when we tell it to, while logged in (trying to get it to update from version 11 to 13).

We have whitelisted www.teamviewer.com for us to be able to use TeamViewer. And we've tried whitelisting download.teamviewer.com, as well, since I noticed the address in the TeamViewer logs for where it was trying to download the update. When that didn't work, we also tried just whitelisting *.teamviewer.com too, just as a catch-all for anything from the TeamViewer site.

Despite this, though, the logs still report a 403 Forbidden error.

So, my question is, what should I be whitelisting to get the update to work?

(Below is an excert from the log for the update process)

2018/06/29 07:29:11.599 4112 4116 G1 UpdateBase::Start(): Update is already running
2018/06/29 07:29:36.122 2448 3000 S0 Estimated Bandwidth Capacity to 510155584: 79986 kbit/s, Reliability: 3, Carrier: 1
2018/06/29 07:29:48.910 4112 6184 G1!! UpdateBase::OnDownloadFinishedUpdateFile - CInetDownload::ThreadRun - Wrong Status Code: 403 StatusMessage: "Forbidden" Occured while retrieving: download.teamviewer.com/download/update/update_host_13.1.3629.zip
2018/06/29 07:29:54.153 2448 3004 S0 Estimated Bandwidth Capacity to 584973682: 472803 kbit/s, Reliability: 3, Carrier: 1
2018/06/29 07:31:00.262 2448 3012 S0 Estimated Bandwidth Capacity to Router: 2475002 kbit/s, Reliability: 3, Carrier: 1
2018/06/29 07:31:18.622 2448 3012 S0 ReadStreamParameters(): streamID=22 type=6 (StreamType_File), source=[510155584,8962046]

Best Answer

Answers

  • JohnGuy
    JohnGuy Posts: 3

    Hi Scotty,

    Well, that seems to have helped some. However, now instead of getting a 403 error I get the following:

    UpdateBase::OnDownloadFinishedUpdateFile - CInetDownload::ThreadRun - ErrorReceiveResponse 12152

    Any idea what might be causing this?

    Thanks,

    John

  • JohnGuy
    JohnGuy Posts: 3

    We've figured out the second issue that we ran into.

    We basically told our Squid Proxy Server that port 80 and 443 are allowed and to ignore SSL ports ( # http_access deny CONNECT !SSL_ports )

    Thank you for your help, Scotty!

     

Trustpilot

Categories

This Week's Leaders