/build/static/layout/Breadcrumb_cap_w.png

allowing kace to update via public ip

Hi All.

In our environment kace agents can be updated only when machines are connected to domain network that is office network.. It cannot update when user is working from home and connected to public networks..we are planning to make kace agents communicate and update in both office and public networks ..is there any risk in setting up kace to communicate both in  public ineternet and office network???? What's the risk in opening up the port 52230 when it is given access over internet ?? That is making  kace agents to update or  communicate over internet ???thanks

0 Comments   [ + ] Show comments

Answers (3)

Posted by: jegolf 8 years ago
Red Belt
0
Just enable and get SSL working (if not already) before opening any ports, NATing, and exposing the kbox to the Internet. The benefit of tracking and updating your laptops is nice. We found missing hardware once we did so.
Posted by: Nico_K 8 years ago
Red Belt
0
many customers do this. 
Using VPN would be a good thing,
You can also do it as you planned it.
You need a few more ports than 52230, btw.
Full list here:
https://support.software.dell.com/kb/111775
Important are 52230 and 80/443 (depending on SSL or not)
Posted by: BarcelllosBC1982 2 years ago
White Belt
0

Good evening!
I am from Brazil and found the link on the site of Quest Brazil.
I hope it helps.

https://support.quest.com/pt-br/kb/111775/quais-portas-de-rede-e-urls-s%c3%a3o-necess%c3%a1rios-para-que-o-k1000-funcione


Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ