I'm running v184.108.40.2061 of Kaspersky PVN (paid version). The VPn seems to be working just fine. But, when I run a DNS leak test on https://dnsleaktest.com/results.html, it confirms that DNS is routed via my local ISP provider, AT&T, through their DNS servers. I can also confirm that while the DNS address is listed as 220.127.116.11 and 18.104.22.168 for "wi-fi" and is 22.214.171.124 and 126.96.36.199 for the Kaspersky Data Escort... the DNS Name is attlocal.net. This is the AT&T DNS server. My PC is connected to the AT&T router and that router can not be configured to change the DNS settings.
How do I enable a DNS tunnel to protect DNS queries from going to AT&T? There's little point in using a VPN service if my traffic is visible to my ISP.
Estoy generando un paquete de instalación para MAC desde Cloud Console
pero al generarlo me descarga un archivo con extension .sh
Yo esperaba un archivo con extension .dmg para que el usuario pudiera ejecutarlo isn problemas en su mac, pero el archivo .sh no ubico como se podria instalar.
Saben como seria posible generar el archivo DMG, en la version 12 de KSC on premise si se genera.
Thanks for the reply.
The 'trusted addresses' option is greyed out, as I had "Do not scan encrypted connections" selected. This was due to previous issues with web development and the certificate. It appears that even with this selected, some issues can still happen.
I've kept 443 disabled for now, as I don't have time to further troubleshoot.
This issue now seems to be hitting more than just Slack however. Battle.net from Blizzard is now experiencing the same issue. It it unable to update games (connection failing). Disabling Kaspersky instantly resolves the issue, and games can be downloaded and updated. Port 443 scanning is still disable as mentioned above.
I'll look into what ports Battle.net is using and see what options I have. Much like Slack, I've used Battle.net and Kaspersky together for years without issue. It's a shame to see multiple applications suddenly having issues.
We are running Security Center 12, and using policy to push an additional network rule for making a specific network range a trusted network, and this portion of the policy is failing to get pushed to endpoints in Firewall->Additional Networks where is has previously. All other parts of the policy appear to get applied to the endpoint as expected, and shift when we test that other things getting applied to the Firewall are applied. Clients where we are seeing this are new installs of Endpoint Security for Windows 12.7 or 12.8 using Network Agent 12.2. This seems to only have started in the last few weeks.
Do anyone have any idea what may be causing this? I've looked around and haven't found any immediate patches or anything else that we may be missing.
That's really a weird situation. I'm very sorry for your kid's photos. I also own a Xiaomi phone with KSK. I only use it with one space. So far, I haven't had any issue with Kaspersky Safe Kids. I use it on my phone to monitor my daughter's phone. I'm surprised by the answers Kasperky support gave you. I hope you could recover these photos.
Personally, I save all my photos on my cloud storage.