To obtain trusted flair for your account please message the mods of /r/HomeNetworking with the following info Trusted user flair has been added as a means of verification that a user has a substantial knowledge of networking. Please flair your posts as Solved, Unsolved, or simply Advice.
If you can't find what you're looking for with the search function please feel free to post a new question after reading the posting guidelines I took your grammar literally and it means TeamViewer "WILL also run" (there are no qualifying conditions) over the same ports as web traffic if you are doing outbound filtering, and for that reason ("which is why"), it "almost always connects." Had it read "TeamViewer can also run over the same ports under certain conditions" or "TeamViewer sometimes also runs over the same ports," it would have been clear.Please use the search function to look for keywords related to what you want to ask before posting since most common issues have been answered. However, you are correct most web proxies will block the TeamViewer traffic. Not everyone employes HTTPS scanning and filtering. I have to open 5938 outbound to TeamViewer's domain.
Yes, it may TRY to go out (I assume) port 443, but that would not be HTTPS-compliant traffic and would get dropped. With my WatchGuard firewalls and HTTPS/DPI enabled, TeamViewer will not work. It MAY work if one's outbound filtering firewall does not do HTTPS deep packet inspection. "TeamViewer will also run over the same ports as web traffic if you are doing outbound filtering" is not entirely correct. You will also fail most compliance tests by doing so. There are automated attacks that attack 3389 leaving your networks vulnerable. You should either be using a VPN or an RDGateway for this. It is not secure to expose 3389 to the internet. Justin1250 wrote:TeamViewer will also run over the same ports as web traffic if you are doing outbound filtering, which is why it almost always connects.Īs for RDP, you should not be forwarding 3389 from the internet to any device inside a FW.
0 kommentar(er)
