How to Disable Shield DNS Protection When Troubleshooting Network Connectivity Issues (Business)

Overview

Some Splashtop Shield protection features use DNS-based filtering to block fraudulent websites and unapproved remote access tools. To provide these features, Shield may modify the device's DNS configuration and route DNS requests through its local DNS resolver.

In certain network environments, this may interfere with existing network or DNS configurations.

If you experience network connectivity issues, DNS resolution problems, or difficulty accessing internal network resources after installing Splashtop Shield, you can temporarily disable Shield's DNS-based protection features to help troubleshoot the issue.

This allows you to keep Splashtop Shield installed and maintain its core antivirus protection while checking whether Shield's DNS handling is contributing to the problem.

This article applies to both Windows and macOS devices.

Common Symptoms

The following symptoms may indicate a DNS-related connectivity issue:

  • Network shares are inaccessible: Internal shared folders, mapped network drives, or file servers cannot be reached, but they may still work when accessed using their IP addresses.
  • Internal websites cannot be opened: Company intranet sites or internal server names fail to resolve, even though public websites are accessible.
  • VPN connectivity issues: Certain internal resources become inaccessible when connected to a corporate VPN.
  • Location-dependent connectivity issues: Network resources work at one office location but cannot be accessed from another location or a remote network.
  • Connectivity improves after uninstalling Shield: Network access returns after Shield is removed from the device.

These symptoms do not necessarily mean that Shield is causing the issue. The following steps can help determine whether its DNS-based protection is involved.


Step 1: Choose How to Change the Settings

This article is for Shield Business devices. Sign in to the Shield Business Console using the Business account owner's email when managing policies.

  • Enforce these settings on every device — ON: Your protection settings are centrally managed. Follow Method A (Business Console) in Step 2.
  • Enforce these settings on every device — OFF: Protection settings are managed in the Shield app on each device. Follow Method B (Local Shield App) in Step 2. Changing the policy in the console will not override the device's local settings while enforcement is off.

Important: Turning on policy enforcement applies that policy's settings to every device using the policy. If only a few devices are affected, consider a separate policy and group before enabling enforcement. This article does not cover Family guardian management or Individual plans.


Step 2: Turn Off Scam Protection and Remote Access Protection

Both features must be disabled. In the current Shield configuration, leaving either feature enabled will continue to require Shield's DNS-based protection.

Disabling these features allows Shield to stop using DNS-based filtering for these protections and return DNS handling to the device's normal network configuration.

Note: Disabling these features does not disable Shield's core antivirus engine or malware scanning.

Method A: Shield Business Console (Enforced Policy)

Use this method for Business plan devices whose policy has Enforce these settings on every device turned on.

A1. Sign In to the Shield Business Console

For Shield Business, open the Business Console:

https://business.shield.splashtop.com/

  1. Open the Shield Business Console login page.
  2. Enter the email address of the corresponding account owner (the Splashtop Remote Access owner if Shield was provisioned through Remote Access).
  3. Request a one-time password (OTP).
  4. Check the account owner's email inbox for the OTP.
  5. Enter the OTP to complete the sign-in process.

You should now have access to your Shield devices, groups, and protection policies.

If you cannot sign in or do not have permission to manage policies, contact your account administrator.

A2. Select the Devices You Want to Troubleshoot

In Splashtop Shield, protection policies are assigned to device groups.

Important: Changes to a policy affect all devices assigned to that policy, including devices in other groups that use the same policy.

We recommend applying the troubleshooting changes only to affected devices whenever possible.

Option 1: Create a Separate Policy and Group (Recommended)

This option limits the changes to affected devices while keeping the original protection settings for other devices.

  1. In the Shield Business Console, go to Policies.
  2. Click + New policy.
  3. Configure the new policy using the same settings as your existing policy, and make sure Enforce these settings on every device is turned on. Keep all other protection settings unchanged. Click Create policy to save the new policy.
  4. Create a new device group using Create group.
  5. Assign the newly created policy to the new group.
  6. Locate the affected devices in the device list.
  7. Use Change group to move the affected devices into the new group.
  8. Continue to A3 to modify the new policy.

This approach allows you to troubleshoot individual devices without changing protection settings for your entire organization.

Option 2: Modify an Existing Policy

If you want to apply the changes to all devices using an existing policy:

  1. Locate the group containing the affected devices.
  2. Identify the protection policy assigned to that group.
  3. Navigate to Policies.
  4. Find the corresponding policy and click Edit.
  5. Continue to A3.

Important: Before changing an existing policy, verify which other devices or groups use it. All devices assigned to that policy may be affected.

A3. Disable the Anti-Scam Features in the Policy

In the policy editor, locate the Anti-Scam section.

Turn off both of the following features:

  • Scam protection: OFF
  • Remote access protection: OFF

You do not need to change the Website allowlist setting.

A4. Save and Apply the Policy Changes

  1. Click Save to save the updated protection policy.
  2. Make sure the affected device is powered on and connected to the network.
  3. Allow the device to receive and apply the updated policy.

Shield devices periodically communicate with the Splashtop service to receive configuration updates.

Shield normally checks for configuration updates approximately every 5 minutes. Allow up to 10 minutes for an online device to receive and apply a console policy change. If the device is offline or cannot connect to Splashtop's servers, the update may be delayed. This is a troubleshooting window, not a guarantee that DNS cleanup will succeed.

Important: If the device cannot communicate with Splashtop's servers because of the network issue, it may not receive the updated policy.

Continue to Step 3.

Method B: Shield App on the Device (Non-Enforced Policy)

Use this method for Business plan devices whose policy has Enforce these settings on every device turned off.

The changes are made locally on the device and take effect immediately. They do not require the device to contact Splashtop's servers.

On the affected device:

  1. Open the Splashtop Shield app.
  2. On the main page, find Protection features and click Configure.
  3. Open the Anti-Scam settings.
  4. Turn off both of the following features:
    • Scam Protection: OFF
    • Remote Access Protection: OFF

If these settings cannot be changed in the app, an enforced organization policy may be managing them. Contact your Business administrator or follow Method A if you manage the policy.

Repeat these steps on each affected device, then continue to Step 3.


Step 3: Check the DNS Configuration on the Affected Device

After the change has been applied, check the device's network configuration to see whether its DNS settings have returned to the expected values. Follow the instructions for the device's operating system.

Note: These checks help identify whether the DNS configuration has been restored, but they do not independently confirm that every DNS-related component has stopped operating.

3.1 Windows

Check the Current DNS Servers

  1. Open Command Prompt or PowerShell.
  2. Run the following command:

    ipconfig /all
  3. Find the active network adapter, such as Ethernet or Wi-Fi.
  4. Locate the DNS Servers field.

The DNS servers should normally match those provided by your organization, network administrator, or router.

For example, if your company uses internal DNS servers, you should see those servers listed under the active network adapter.

The DNS configuration should no longer depend on Shield's local DNS resolver.

If the DNS configuration still appears to be managed by Shield, the change may not have been applied successfully, or the original network configuration may not have been fully restored.

Clear the DNS Cache

After checking the DNS settings, run:

ipconfig /flushdns

This clears cached DNS records so Windows can perform fresh DNS lookups using its current configuration.

You should see a message indicating that the DNS resolver cache was successfully flushed.

3.2 macOS

Check the Current DNS Servers

  1. Open Terminal (in Applications > Utilities).
  2. List the network services on the Mac:

    networksetup -listallnetworkservices

    Identify the network service associated with your current connection, such as Wi-Fi or Ethernet. If you are unsure which service is active, check System Settings > Network.

  3. Check the DNS servers configured for that service, replacing Wi-Fi with the service name if it is different:

    networksetup -getdnsservers Wi-Fi

The result should be one of the following:

  • The DNS servers provided by your organization, network administrator, or router, or
  • The message "There aren't any DNS Servers set on Wi-Fi", which means no DNS servers are manually configured for this network service. macOS may obtain DNS settings automatically from DHCP or other network configurations.

The DNS configuration should no longer point to Shield's local DNS resolver.

To see which DNS servers the Mac is actually using, including those provided automatically by the network, you can also run:

scutil --dns

Review the nameserver entries and any domain-specific resolvers shown in the output. If your organization uses a VPN or split DNS, different DNS servers may be used for different domains. Check the relevant DNS servers against your organization's expected network configuration.

If the DNS configuration still appears to be managed by Shield, the change may not have been applied successfully, or the original network configuration may not have been fully restored.

Clear the DNS Cache

After checking the DNS settings, run the following command. You will be asked for an administrator password:

sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

This clears cached DNS records so macOS can perform fresh DNS lookups using its current configuration. The command does not display a message when it succeeds.

3.3 If DNS Settings Have Not Returned to Normal

If the DNS configuration still appears incorrect:

  1. Confirm that both Scam protection and Remote access protection are turned off in the place that manages the device's settings (see Step 1).
  2. Method A: Confirm that the device is assigned to the intended group and Enforce these settings on every device is ON. Method B: Confirm enforcement is OFF and changes were made in the Shield app.
  3. Method A: Make sure the device can communicate with Splashtop's servers to receive the updated settings.
  4. Method A: Allow up to 10 minutes for an online device to apply the update, then verify the policy or device settings have changed. Method B: Local changes should take effect immediately.
  5. If the settings have applied but DNS remains incorrect, contact Splashtop Support. An applied policy does not necessarily mean that DNS settings were fully restored.

Do not manually change your organization's DNS servers, DNS suffix settings, or search domains unless instructed by your network administrator or Splashtop Support.


Step 4: Test Network Connectivity

Once the change has been applied and you have checked the DNS settings, try accessing the network resources that were previously unavailable.

Examples include:

  • Shared network folders and mapped network drives
  • Internal file servers
  • Company intranet websites
  • Resources hosted at other office locations
  • Resources accessed through a corporate VPN
  • Internal applications that rely on company DNS servers

If Network Connectivity Is Restored

If previously inaccessible resources become available after disabling the two Anti-Scam features, this suggests that Shield's DNS-based protection may have contributed to the connectivity issue.

You can leave the features temporarily disabled while you work with Splashtop Support to investigate the issue.

Please contact Support and describe the behavior you observed so we can investigate the underlying cause.

If Network Connectivity Is Not Restored

If the issue continues:

  1. Confirm that the change has been applied on the affected device.
  2. Review the DNS configuration using the instructions in Step 3.
  3. Check whether the affected resources are accessible from other devices on the same network.
  4. Contact Splashtop Support for further troubleshooting.

A continuing connectivity problem does not necessarily rule out a DNS-related issue. Additional network settings or other components may require investigation.


What Happens When These Features Are Disabled?

Disabling the two Anti-Scam features temporarily reduces some of Shield's security protections.

Feature Status
Scam protection — blocking fraudulent and phishing websites Disabled
Remote access protection — blocking unapproved remote access tools Disabled
Antivirus and malware protection Remains enabled
File scanning Remains enabled

Shield's core antivirus and malware scanning capabilities remain active.

However, fraudulent website blocking and unapproved remote access tool blocking provided by these two features will no longer be active.

We recommend using this configuration temporarily for troubleshooting rather than as a permanent security configuration.


Turning the Features Back On

Once the network issue has been resolved, we recommend re-enabling the disabled protection features.

For example, you can restore the original configuration after:

  • Splashtop Support confirms that the underlying issue has been resolved.
  • Your device has been updated to a Shield version that addresses the issue.
  • Your IT administrator determines that the original protection configuration can be safely restored.

To restore the protection settings, turn Scam protection and Remote access protection back on in the same place you turned them off:

  • Method A (Business Console): Go to Policies, edit the policy you modified, turn both features on, and save. Allow the affected devices to receive the updated policy.
  • Method B (Shield app): On each device, go to Protection features > Configure > Anti-Scam and turn both features on.

If You Created a Temporary Group (Method A)

If you followed Option 1 in A2:

  1. Move the affected devices back to their original group using Change group.
  2. Confirm that the devices have received their original protection policy.
  3. Remove the temporary group and policy if they are no longer needed.

This restores the original protection configuration without requiring you to manually recreate the previous settings.


Still Experiencing Issues?

The Policy Change Does Not Reach the Device (Method A)

Shield devices need to communicate with Splashtop's servers to receive policies changed in the Business Console.

If a device cannot connect because of firewall restrictions, proxy settings, SSL inspection, or other network connectivity problems, the updated settings may not take effect.

Check that the device can access the required Splashtop Shield services.

If immediate recovery is necessary and the settings cannot be updated, you may uninstall Shield from the affected device.

If network connectivity does not recover after uninstalling Shield, contact Splashtop Support for assistance.

The Change Is Applied, but the Network Issue Continues

If both Anti-Scam features are disabled and the device has applied the change, but the issue remains, contact Splashtop Support for further investigation. For console-managed devices, if the change has not appeared after 10 minutes, first investigate policy delivery; if it has appeared but DNS remains incorrect, investigate DNS restoration.

When submitting a support request, please include:

  • Device information: The affected device name, operating system (Windows or macOS), and version.
  • Plan and method: Whether you used Method A (Business Console) or Method B (local Shield app), and whether policy enforcement is enabled.
  • Issue description: Which websites, servers, shared folders, or other network resources cannot be accessed.
  • Network behavior: Whether the issue occurs on all networks or only on specific office or VPN connections.
  • DNS comparison: Whether resources work when accessed by IP address instead of hostname.
  • Troubleshooting results: Whether disabling Scam protection and Remote access protection made any difference.
  • DNS configuration: Preferably captured both before and after the change:
    • Windows: the output of ipconfig /all
    • macOS: the output of scutil --dns
  • Shield debug log: Click the Shield icon in the Windows system tray (right-click) or the macOS menu bar, select About, click the button in the bottom-left corner, and save the debug log.

This information will help our Support Team identify the cause and recommend the appropriate resolution.


Summary

If a Shield Business device experiences DNS or network issues, temporarily disable Scam protection and Remote access protection using the enforced Business Console policy (Method A) or local Shield app (Method B), according to your enforcement setting.

Changes from the Business Console may take up to 10 minutes on an online device; local app changes take effect immediately. Verify the device's DNS configuration, preserve core antivirus and file scanning protection, and re-enable the two features after the issue is resolved.

0 out of 0 found this helpful