Search the Community
Showing results for tags 'fqdn'.
Found 1 result
Hello all, I am trialing a VPN solution for my workplace. We are using the in built CISCO Meraki VPN Client Server to setup and maintain the VPN. The main goal of the VPN is to allow sales and technical staff access to network mapped resources back at HQ, and to allow the technicians to remotely enter customers sites. We setup all sites so that only our HQ IP address can access them remotely for security purposes. One of the key requirements of this VPN is to have FQDN (Fully Qualified Domain Name) resolve correctly both onsite and offsite of HQ. Onto the issue at hand. On clients not running Malwarebytes, I can successfully connect to the VPN, ping network resources by both their IP and FQDN, and map network drives. On my test laptop running Windows 10 and Malwarebytes 3, I cannot ping FQDN and as a result cannot map network drives. I can ping network resources via their IP, however this is not ideal due to possible IP changes in the near future then requiring that all client PC's have their network mappings updated. After some troubleshooting I was able to narrow the issue down to Malwarebytes by first disabling it and been able to successfully ping FQDN, and then further narrowed down to Web Protection by following the same process. I have tried adding an exclusion for the external IP of the VPN server but this has not helped. Details of the type of VPN used are below: VPN Server: Cisco Meraki Firewall Type: IPsec2 / Pre-shared Key VPN Server using onsite nameserver as DNS. We are currently investigating antivirus solutions to role out to our whole team and unfortunately this is painting a black spot on Malwarebytes as been the choosen solution. I have used Malwarebytes for years and hold it in high regard, hopefully this can be resolved with the communities help Thanks, Lord_LolzWorth