Установка Teamviewer Host на Ubuntu 17.04

Question 1

Попытка установить Teamviewer Host в соответствии с инструкциями, но столкнуться с проблемой. Установщик программного обеспечения Ubuntu после нажатия кнопки «Установить», похоже, запускает процесс установки, но затем ничего не делает, и программное обеспечение не установлено. Ничем не отображается индикатор выполнения под кнопкой в течение нескольких секунд, а затем не пропускает никакого запроса на auth ничего. Если вы попробуете запустить его снова, значок по умолчанию, то есть серый отображается в панели слева, а индикатор выполнения помещен в него, но ничего не делает и не может быть закрыт.

Question 2

Teamviewer 12 установлен отлично на моем 17.04. У меня отключен брандмауэр. Вы можете попробовать, так как Teamviewer хочет использовать свои собственные порты или проверить свои порты брандмауэра. OUTGOING CONNECTIONS.

* Однако в некоторых ситуациях, например, в корпоративной среде со строгими политиками безопасности, может быть установлен брандмауэр чтобы заблокировать все неизвестные исходящие подключения, и в этом случае вам необходимо настроить брандмауэр, чтобы TeamViewer мог подключиться через него. Blockquote

TCP/UDP Port 5938: TeamViewer prefers to make outbound TCP and UDP connections over port 5938 – this is the primary port it uses, and TeamViewer performs best using this port. Your firewall should allow this at a minimum.
TCP Port 443: If TeamViewer can’t connect over port 5938, it will next try to connect over TCP port 443.
Note: port 443 is also used by our custom modules which are created in the Management Console. If you’re deploying a custom module, eg. through Group Policy, then you need to ensure that port 443 is open on the computers to which you’re deploying. Port 443 is also used for a few other things, including TeamViewer update checks.


TCP Port 443: If TeamViewer can’t connect over port 5938, it will next try to connect over TCP port 443.

Note: port 443 is also used by our custom modules which are created in the Management Console. If you’re deploying a custom module, eg. through Group Policy, then you need to ensure that port 443 is open on the computers to which you’re deploying. Port 443 is also used for a few other things, including TeamViewer update checks.
TCP Port 80: If TeamViewer can’t connect over port 5938 or 443, then it will try on port TCP 80. The connection speed over this port is slower and less reliable than ports 5938 or 443, due to the additional overhead it uses, and there is no automatic reconnection if the connection is temporarily lost. For this reason port 80 is only used as a last resort.
TCP Port 80: If TeamViewer can’t connect over port 5938 or 443, then it will try on port TCP 80. The connection speed over this port is slower and less reliable than ports 5938 or 443, due to the additional overhead it uses, and there is no automatic reconnection if the connection is temporarily lost. For this reason port 80 is only used as a last resort.*

Question 3

Question 4

Teamviewer 12 установлен отлично на моем 17.04. У меня отключен брандмауэр. Вы можете попробовать, так как Teamviewer хочет использовать свои собственные порты или проверить свои порты брандмауэра. OUTGOING CONNECTIONS.

* Однако в некоторых ситуациях, например, в корпоративной среде со строгими политиками безопасности, может быть установлен брандмауэр чтобы заблокировать все неизвестные исходящие подключения, и в этом случае вам необходимо настроить брандмауэр, чтобы TeamViewer мог подключиться через него. Blockquote

TCP/UDP Port 5938: TeamViewer prefers to make outbound TCP and UDP connections over port 5938 – this is the primary port it uses, and TeamViewer performs best using this port. Your firewall should allow this at a minimum.
TCP Port 443: If TeamViewer can’t connect over port 5938, it will next try to connect over TCP port 443.
Note: port 443 is also used by our custom modules which are created in the Management Console. If you’re deploying a custom module, eg. through Group Policy, then you need to ensure that port 443 is open on the computers to which you’re deploying. Port 443 is also used for a few other things, including TeamViewer update checks.


TCP Port 443: If TeamViewer can’t connect over port 5938, it will next try to connect over TCP port 443.

Note: port 443 is also used by our custom modules which are created in the Management Console. If you’re deploying a custom module, eg. through Group Policy, then you need to ensure that port 443 is open on the computers to which you’re deploying. Port 443 is also used for a few other things, including TeamViewer update checks.
TCP Port 80: If TeamViewer can’t connect over port 5938 or 443, then it will try on port TCP 80. The connection speed over this port is slower and less reliable than ports 5938 or 443, due to the additional overhead it uses, and there is no automatic reconnection if the connection is temporarily lost. For this reason port 80 is only used as a last resort.
TCP Port 80: If TeamViewer can’t connect over port 5938 or 443, then it will try on port TCP 80. The connection speed over this port is slower and less reliable than ports 5938 or 443, due to the additional overhead it uses, and there is no automatic reconnection if the connection is temporarily lost. For this reason port 80 is only used as a last resort.*

jpezz · Answer 1 · 18 July 2018 в 06:55

Teamviewer 12 установлен отлично на моем 17.04. У меня отключен брандмауэр. Вы можете попробовать, так как Teamviewer хочет использовать свои собственные порты или проверить свои порты брандмауэра. OUTGOING CONNECTIONS.

* Однако в некоторых ситуациях, например, в корпоративной среде со строгими политиками безопасности, может быть установлен брандмауэр чтобы заблокировать все неизвестные исходящие подключения, и в этом случае вам необходимо настроить брандмауэр, чтобы TeamViewer мог подключиться через него. Blockquote

TCP/UDP Port 5938: TeamViewer prefers to make outbound TCP and UDP connections over port 5938 – this is the primary port it uses, and TeamViewer performs best using this port. Your firewall should allow this at a minimum.
TCP Port 443: If TeamViewer can’t connect over port 5938, it will next try to connect over TCP port 443.
Note: port 443 is also used by our custom modules which are created in the Management Console. If you’re deploying a custom module, eg. through Group Policy, then you need to ensure that port 443 is open on the computers to which you’re deploying. Port 443 is also used for a few other things, including TeamViewer update checks.


TCP Port 443: If TeamViewer can’t connect over port 5938, it will next try to connect over TCP port 443.

Note: port 443 is also used by our custom modules which are created in the Management Console. If you’re deploying a custom module, eg. through Group Policy, then you need to ensure that port 443 is open on the computers to which you’re deploying. Port 443 is also used for a few other things, including TeamViewer update checks.
TCP Port 80: If TeamViewer can’t connect over port 5938 or 443, then it will try on port TCP 80. The connection speed over this port is slower and less reliable than ports 5938 or 443, due to the additional overhead it uses, and there is no automatic reconnection if the connection is temporarily lost. For this reason port 80 is only used as a last resort.
TCP Port 80: If TeamViewer can’t connect over port 5938 or 443, then it will try on port TCP 80. The connection speed over this port is slower and less reliable than ports 5938 or 443, due to the additional overhead it uses, and there is no automatic reconnection if the connection is temporarily lost. For this reason port 80 is only used as a last resort.*

jpezz · Answer 2 · 24 July 2018 в 18:42

Teamviewer 12 установлен отлично на моем 17.04. У меня отключен брандмауэр. Вы можете попробовать, так как Teamviewer хочет использовать свои собственные порты или проверить свои порты брандмауэра. OUTGOING CONNECTIONS.

* Однако в некоторых ситуациях, например, в корпоративной среде со строгими политиками безопасности, может быть установлен брандмауэр чтобы заблокировать все неизвестные исходящие подключения, и в этом случае вам необходимо настроить брандмауэр, чтобы TeamViewer мог подключиться через него. Blockquote

TCP/UDP Port 5938: TeamViewer prefers to make outbound TCP and UDP connections over port 5938 – this is the primary port it uses, and TeamViewer performs best using this port. Your firewall should allow this at a minimum.
TCP Port 443: If TeamViewer can’t connect over port 5938, it will next try to connect over TCP port 443.
Note: port 443 is also used by our custom modules which are created in the Management Console. If you’re deploying a custom module, eg. through Group Policy, then you need to ensure that port 443 is open on the computers to which you’re deploying. Port 443 is also used for a few other things, including TeamViewer update checks.


TCP Port 443: If TeamViewer can’t connect over port 5938, it will next try to connect over TCP port 443.

Note: port 443 is also used by our custom modules which are created in the Management Console. If you’re deploying a custom module, eg. through Group Policy, then you need to ensure that port 443 is open on the computers to which you’re deploying. Port 443 is also used for a few other things, including TeamViewer update checks.
TCP Port 80: If TeamViewer can’t connect over port 5938 or 443, then it will try on port TCP 80. The connection speed over this port is slower and less reliable than ports 5938 or 443, due to the additional overhead it uses, and there is no automatic reconnection if the connection is temporarily lost. For this reason port 80 is only used as a last resort.
TCP Port 80: If TeamViewer can’t connect over port 5938 or 443, then it will try on port TCP 80. The connection speed over this port is slower and less reliable than ports 5938 or 443, due to the additional overhead it uses, and there is no automatic reconnection if the connection is temporarily lost. For this reason port 80 is only used as a last resort.*

Установка Teamviewer Host на Ubuntu 17.04

2 ответа

Другие вопросы по тегам:

Похожие вопросы: