- What Proxy Configuration Do I Need For Kindle On Mac Download
- What Proxy Configuration Do I Need For Kindle On Mac Computer
On your Mac, choose Apple menu System Preferences, then click Network. In the list, select the network service you use—for example, Ethernet or Wi-Fi. Click Advanced, then click Proxies. If you want to configure your proxy server settings automatically, do one of the following. Apr 05, 2017 The proxy service is now enabled. On the device which you want to use a proxy server with, enter your MacBook's IP as the proxy and the port (8080) you chose in Step 2. If you have a VPN running on your computer, any device with the IP and port should have its connections passed through the virtual private network.
-->Important
Welcome to Microsoft Defender for Endpoint, the new name for Microsoft Defender Advanced Threat Protection. Read more about this and other updates here. We'll be updating names in products and in the docs in the near future.
Applies to:
Want to experience Defender for Endpoint? Sign up for a free trial.
The Defender for Endpoint sensor requires Microsoft Windows HTTP (WinHTTP) to report sensor data and communicate with the Defender for Endpoint service.
The embedded Defender for Endpoint sensor runs in system context using the LocalSystem account. The sensor uses Microsoft Windows HTTP Services (WinHTTP) to enable communication with the Defender for Endpoint cloud service.
Tip
For organizations that use forward proxies as a gateway to the Internet, you can use network protection to investigate behind a proxy. For more information, see Investigate connection events that occur behind forward proxies.
The WinHTTP configuration setting is independent of the Windows Internet (WinINet) Internet browsing proxy settings and can only discover a proxy server by using the following discovery methods:
Auto-discovery methods:
Transparent proxy
Web Proxy Auto-discovery Protocol (WPAD)
Note
If you're using Transparent proxy or WPAD in your network topology, you don't need special configuration settings. For more information on Defender for Endpoint URL exclusions in the proxy, see Enable access to Defender for Endpoint service URLs in the proxy server.
Manual static proxy configuration:
- Registry based configuration
- WinHTTP configured using netsh command – Suitable only for desktops in a stable topology (for example: a desktop in a corporate network behind the same proxy)
Configure the proxy server manually using a registry-based static proxy
Configure a registry-based static proxy to allow only Defender for Endpoint sensor to report diagnostic data and communicate with Defender for Endpoint services if a computer is not be permitted to connect to the Internet.
The static proxy is configurable through Group Policy (GP). The group policy can be found under:
- Administrative Templates > Windows Components > Data Collection and Preview Builds > Configure Authenticated Proxy usage for the Connected User Experience and Telemetry Service
- Set it to Enabled and select Disable Authenticated Proxy usage:
- Administrative Templates > Windows Components > Data Collection and Preview Builds > Configure connected user experiences and telemetry:
Configure the proxy:
The policy sets two registry values
TelemetryProxyServer
as REG_SZ andDisableEnterpriseAuthProxy
as REG_DWORD under the registry keyHKLMSoftwarePoliciesMicrosoftWindowsDataCollection
.The registry value
TelemetryProxyServer
takes the following string format:For example: 10.0.0.6:8080
The registry value
DisableEnterpriseAuthProxy
should be set to 1.
Configure the proxy server manually using netsh command
Use netsh to configure a system-wide static proxy.
Note
- This will affect all applications including Windows services which use WinHTTP with default proxy.
- Laptops that are changing topology (for example: from office to home) will malfunction with netsh. Use the registry-based static proxy configuration.
Open an elevated command-line:
a. Go to Start and type cmd.
b. Right-click Command prompt and select Run as administrator.
Enter the following command and press Enter:
For example: netsh winhttp set proxy 10.0.0.6:8080
To reset the winhttp proxy, enter the following command and press Enter
See Netsh Command Syntax, Contexts, and Formatting to learn more.
Enable access to Microsoft Defender for Endpoint service URLs in the proxy server
If a proxy or firewall is blocking all traffic by default and allowing only specific domains through, add the domains listed in the downloadable sheet to the allowed domains list.
The following downloadable spreadsheet lists the services and their associated URLs that your network must be able to connect to. You should ensure that there are no firewall or network filtering rules that would deny access to these URLs, or you may need to create an allow rule specifically for them.
Spreadsheet of domains list | Description |
---|---|
Spreadsheet of specific DNS records for service locations, geographic locations, and OS. Download the spreadsheet here. |
If a proxy or firewall has HTTPS scanning (SSL inspection) enabled, exclude the domains listed in the above table from HTTPS scanning.
Note
settings-win.data.microsoft.com is only needed if you have Windows 10 devices running version 1803 or earlier.
Note
URLs that include v20 in them are only needed if you have Windows 10 devices running version 1803 or later. For example, us-v20.events.data.microsoft.com
is needed for a Windows 10 device running version 1803 or later and onboarded to US Data Storage region.
Note Expansion - europa universalis iv: art of war download for mac.
If you are using Microsoft Defender Antivirus in your environment, see Configure network connections to the Microsoft Defender Antivirus cloud service.
If a proxy or firewall is blocking anonymous traffic, as Defender for Endpoint sensor is connecting from system context, make sure anonymous traffic is permitted in the previously listed URLs.
Microsoft Monitoring Agent (MMA) - proxy and firewall requirements for older versions of Windows client or Windows Server
The information below list the proxy and firewall configuration information required to communicate with Log Analytics agent (often referred to as Microsoft Monitoring Agent) for the previous versions of Windows such as Windows 7 SP1, Windows 8.1, Windows Server 2008 R2, Windows Server 2012 R2, and Windows Server 2016.
Agent Resource | Ports | Direction | Bypass HTTPS inspection |
---|---|---|---|
*.ods.opinsights.azure.com | Port 443 | Outbound | Yes |
*.oms.opinsights.azure.com | Port 443 | Outbound | Yes |
*.blob.core.windows.net | Port 443 | Outbound | Yes |
*.azure-automation.net | Port 443 | Outbound | Yes |
Note
What Proxy Configuration Do I Need For Kindle On Mac Download
As a cloud-based solution, the IP range can change. It's recommended you move to DNS resolving setting.
Confirm Microsoft Monitoring Agent (MMA) Service URL Requirements
Please see the following guidance to eliminate the wildcard (*) requirement for your specific environment when using the Microsoft Monitoring Agent (MMA) for previous versions of Windows.
Onboard a previous operating system with the Microsoft Monitoring Agent (MMA) into Defender for Endpoint (for more information, see Onboard previous versions of Windows on Defender for Endpoint and Onboard Windows servers.
Ensure the machine is successfully reporting into the Microsoft Defender Security Center portal.
Run the TestCloudConnection.exe tool from 'C:Program FilesMicrosoft Monitoring AgentAgent' to validate the connectivity and to see the required URLs for your specific workspace.
Check the Microsoft Defender for Endpoint URLs list for the complete list of requirements for your region (please refer to the Service URLs Spreadsheet).
The wildcards (*) used in *.ods.opinsights.azure.com, *.oms.opinsights.azure.com, and *.agentsvc.azure-automation.net URL endpoints can be replaced with your specific Workspace ID. The Workspace ID is specific to your environment and workspace and can be found in the Onboarding section of your tenant within the Microsoft Defender Security Center portal.
The *.blob.core.windows.net URL endpoint can be replaced with the URLs shown in the 'Firewall Rule: *.blob.core.windows.net' section of the test results.
Note
In the case of onboarding via Azure Security Center (ASC), multiple workspaces maybe used. You will need to perform the TestCloudConnection.exe procedure above on an onboarded machine from each workspace (to determine if there are any changes to the *.blob.core.windows.net URLs between the workspaces).
Verify client connectivity to Microsoft Defender ATP service URLs
Verify the proxy configuration completed successfully, that WinHTTP can discover and communicate through the proxy server in your environment, and that the proxy server allows traffic to the Defender for Endpoint service URLs.
Download the MDATP Client Analyzer tool to the PC where Defender for Endpoint sensor is running on.
Extract the contents of MDATPClientAnalyzer.zip on the device.
Open an elevated command-line:
a. Go to Start and type cmd.
b. Right-click Command prompt and select Run as administrator.
Enter the following command and press Enter:
Replace HardDrivePath with the path where the MDATPClientAnalyzer tool was downloaded to, for example
Extract the MDATPClientAnalyzerResult.zip file created by tool in the folder used in the HardDrivePath.
Open MDATPClientAnalyzerResult.txt and verify that you have performed the proxy configuration steps to enable server discovery and access to the service URLs.
The tool checks the connectivity of Defender for Endpoint service URLs that Defender for Endpoint client is configured to interact with. It then prints the results into the MDATPClientAnalyzerResult.txt file for each URL that can potentially be used to communicate with the Defender for Endpoint services. For example:
If at least one of the connectivity options returns a (200) status, then the Defender for Endpoint client can communicate with the tested URL properly using this connectivity method.
However, if the connectivity check results indicate a failure, an HTTP error is displayed (see HTTP Status Codes). You can then use the URLs in the table shown in Enable access to Defender for Endpoint service URLs in the proxy server. The URLs you'll use will depend on the region selected during the onboarding procedure.
Note
The Connectivity Analyzer tool is not compatible with ASR rule Block process creations originating from PSExec and WMI commands. You will need to temporarily disable this rule to run the connectivity tool.
Note
When the TelemetryProxyServer is set, in Registry or via Group Policy, Defender for Endpoint will fall back to direct if it can't access the defined proxy.
Related topics
With Windows, you can easily make your computer to act as a proxy server using CCProxy. CCProxy was one of this things I missed on Windows when I finally fully switched to macOS. This particular software program isn't available for macOS, but there are alternatives. For my specific need, I found out that the best alternative to CCProxy on macOS is SquidMan. Now, SquidMan isn't the real deal, it is only the graphical installer and manager for the Squid proxy cache on macOS.
Most of the time, I surf the internet using a VPN, both on mobile and PC. It's one of the many ways to hide your real identity online, bypass captchas and geo-restriction.
With most IP addresses of Nigerian service providers blacklisted online already, it's becoming even harder accessing the internet without changing your IP address. In this article for instance, I explained how to use PlayStation Network in Nigeria. Even with a US PSN account, it may be difficult at times to access your account due to your blacklisted IP.
You certainly can't use your VPN directly with your PS4, but there's a way out. You may still run the VPN on your Mac, then make every connection from your PS4 go through the VPN on your Mac by setting it up as a proxy server.
In the simplest terms, every connection from the PS4 passes through your computer (with VPN running), bypassing IP restrictions. With this method, you can tunnel every other gadget too on the same local network through your Mac.
How to configure SquidMan to enable Mac as a proxy server
1. Download and install SquidMan. Opening the DMG file should reveal the app. You have to drag this to your applications folder.
2. Start SquidMan. If you're prompted to download and install the main Squid package, you should accept. The the app is finally launched, you should see the config screen:
3. You can leave the port at 8080 unless the port is already in use by another app on your system. Now go to the 'Clients' tab and add your IP range.
Squid gives you a hint here that adding 192.168.1.0/24 will make it work for your whole IP range. It didn't work for me though, I had to find out what my IP range was by going to Network Preferences in macOS settings.
With this above, your need to enter something like 192.168.43.0/24 in your Squid settings. Again, take note of the MacBook IP address, you're still going to need it.
4. Save your settings.
What Proxy Configuration Do I Need For Kindle On Mac Computer
5. On the small SquidMan user interface, hit the Start Squid button.
The proxy service is now enabled. On the device which you want to use a proxy server with, enter your MacBook's IP as the proxy and the port (8080) you chose in Step 2.
If you have a VPN running on your computer, any device with the IP and port should have its connections passed through the virtual private network.