- Products
- Learn
- Local User Groups
- Partners
- More
Stop Babysitting Rules.
Go Agentic
Step Into the Future of
AI-Powered Cyber Security
The State of Ransomware Q1 2026
Key Trends and Their Impact
AI Security Masters E8:
Claude Mythos: New Era in Cyber Security
Blueprint Architecture for Securing
The AI Factory & AI Data Center
Call For Papers
Your Expertise. Our Stage
CheckMates Go:
CheckMates Fest
Hello. Not 100% sure if we experienced the same issue, but maybe this is helpful for you:
Starting this October we had a few clients not able to resolve internal hostnames and home printers. Like "ping wsus01" was "not resolveable". But "ping -4 wsus01" was successful. After a lot of investigation we figured out, that a GPO was causing the issue. This is the reg-key which we deleted now: HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows NT\DNSClient\ - DisableSmartNameResolution
About CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY