<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>article Private Synthetic Location Not Available for TCP (NAM) Monitors in Troubleshooting</title>
    <link>https://community.dynatrace.com/t5/Troubleshooting/Private-Synthetic-Location-Not-Available-for-TCP-NAM-Monitors/ta-p/300882</link>
    <description>&lt;H2&gt;Summary&lt;/H2&gt;
&lt;P&gt;This article focuses on Dynatrace Synthetic Monitoring, specifically &lt;STRONG&gt;Network Availability Monitors (NAM) using TCP&lt;/STRONG&gt;, and explains why a private Synthetic location may not be selectable when creating TCP monitors.&lt;/P&gt;
&lt;P&gt;It helps you understand the platform prerequisites and system‑level dependencies that determine whether &lt;STRONG&gt;TCP monitoring is available from a private location&lt;/STRONG&gt;, and how to validate TCP connectivity using ActiveGate diagnostics and host-level testing.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;LI-TOC indent="15" liststyle="disc" maxheadinglevel="3"&gt;&lt;/LI-TOC&gt;&lt;/P&gt;
&lt;DIV&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H2&gt;Problem&lt;/H2&gt;
&lt;P&gt;After deploying &lt;STRONG&gt;Synthetic‑enabled ActiveGates&lt;/STRONG&gt; and assigning them to a new private Synthetic location, the location appears as &lt;STRONG&gt;Not supported&lt;/STRONG&gt; when attempting to create a TCP Network Availability Monitor.&lt;/P&gt;
&lt;H3&gt;In the Dynatrace UI&lt;/H3&gt;
&lt;P&gt;You may observe one or more of the following:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;In &lt;STRONG&gt;Synthetic → Private locations&lt;/STRONG&gt;, the private location shows a &lt;STRONG&gt;Compatibility health alert&lt;/STRONG&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Network Availability (TCP)&lt;/STRONG&gt; is missing from the available monitor types under:&lt;BR /&gt;&lt;EM&gt;Classic Settings → Web and mobile monitoring → Private Synthetic locations → Edit location&lt;/EM&gt;&lt;/LI&gt;
&lt;LI&gt;The private location is marked as &lt;STRONG&gt;Not supported&lt;/STRONG&gt;, with a message indicating that the location is not configured to execute this type of monitor&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H2&gt;Evidence in ActiveGate logs&lt;/H2&gt;
&lt;P&gt;The ActiveGate diagnostic logs (&lt;CODE&gt;vuc-status.log&lt;/CODE&gt;) indicate that TCP capability is unavailable, even though other protocols may still be operational.&lt;/P&gt;
&lt;P&gt;Example:&lt;/P&gt;
&lt;PRE&gt;&lt;CODE&gt;MULTIPROTOCOL = {
  MULTIPROTOCOL_TCP = DiagnosticCaseDetail[isAvailable=false],
  MULTIPROTOCOL_DNS = DiagnosticCaseDetail[isAvailable=true],
  MULTIPROTOCOL_ICMP = DiagnosticCaseDetail[isAvailable=true]
}
&lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;When &lt;CODE&gt;MULTIPROTOCOL_TCP&lt;/CODE&gt; is reported as &lt;CODE&gt;isAvailable=false&lt;/CODE&gt;,&lt;BR /&gt;&lt;STRONG&gt;TCP NAM monitors are automatically disabled for the private location&lt;/STRONG&gt;.&lt;/P&gt;
&lt;P&gt;This behavior is consistent with how Dynatrace enables NAM monitor types only when the required protocol capability is validated on the ActiveGate host.&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;For information on finding the log see&amp;nbsp;&lt;/SPAN&gt;&lt;A id="link_6" class="page-link lia-link-navigation lia-custom-event" href="https://community.dynatrace.com/t5/Troubleshooting/Useful-Synthetic-ActiveGate-logs/ta-p/214478" target="_blank"&gt;Useful Synthetic ActiveGate logs&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H2&gt;Troubleshooting steps&lt;/H2&gt;
&lt;P&gt;Use the following steps to determine whether the limitation is due to Dynatrace configuration or host/network constraints.&lt;/P&gt;
&lt;H3&gt;1. Review ActiveGate diagnostic results&lt;/H3&gt;
&lt;UL&gt;
&lt;LI&gt;Check &lt;CODE&gt;vuc-status.log&lt;/CODE&gt; for multi-protocol diagnostics&lt;/LI&gt;
&lt;LI&gt;Confirm whether:
&lt;PRE&gt;&lt;CODE&gt;MULTIPROTOCOL_TCP = isAvailable=false
&lt;/CODE&gt;&lt;/PRE&gt;
&lt;/LI&gt;
&lt;LI&gt;If false, the issue originates from the ActiveGate environment rather than Dynatrace configuration&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H3&gt;2. Understand how TCP availability is validated&lt;/H3&gt;
&lt;P&gt;A TCP NAM monitor works by &lt;STRONG&gt;establishing a TCP connection to a specific port on a target host.&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;The ActiveGate must be able to:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Open an outbound TCP connection&lt;/LI&gt;
&lt;LI&gt;Reach the target host over the network&lt;/LI&gt;
&lt;LI&gt;Successfully complete a TCP handshake on the specified port&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;If this fails during diagnostics, TCP monitoring will be disabled.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H3&gt;3. Verify TCP connectivity from the ActiveGate host&lt;/H3&gt;
&lt;P&gt;Run connectivity tests directly from the ActiveGate host to the target endpoint.&lt;/P&gt;
&lt;P&gt;Examples:&lt;/P&gt;
&lt;DIV class="___77lcry0 f10pi13n"&gt;
&lt;DIV class="___1hewfwb f10pi13n f7oukh6 f5p0z4x" tabindex="0" role="group" aria-label="Code Preview"&gt;
&lt;DIV class="fui-FluentProvider codeBlock-2215fui-FluentProviderr0 ___1jk74h0 fzk5nv6 f6n0el9 f7x6x6c f1a9mlr7 flj889f f13g0yyb ffzn0d2" dir="ltr" data-testid="ComponentFluentProviderId"&gt;
&lt;DIV class="scriptor-component-code-block NhtKn7PZLzk24rduw4FJVQ== scriptor-codeblock-virtualized" tabindex="-1"&gt;
&lt;DIV class="CDXiecnD7ekDByb7Z+4oEA=="&gt;
&lt;DIV class="r14iuplo fui-AriaLive__assertive" aria-live="assertive"&gt;&lt;LI-CODE lang="markup"&gt;nc -vz &amp;lt;hostname&amp;gt; &amp;lt;port&amp;gt;&lt;/LI-CODE&gt;&lt;/DIV&gt;
&lt;DIV class="r14iuplo fui-AriaLive__polite" aria-live="polite"&gt;or&lt;/DIV&gt;
&lt;DIV class="r14iuplo fui-AriaLive__polite" aria-live="polite"&gt;&lt;LI-CODE lang="markup"&gt;telnet &amp;lt;hostname&amp;gt; &amp;lt;port&amp;gt;&lt;/LI-CODE&gt;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;DIV class="___77lcry0 f10pi13n"&gt;
&lt;DIV class="___1hewfwb f10pi13n f7oukh6 f5p0z4x" tabindex="0" role="group" aria-label="Code Preview"&gt;
&lt;DIV class="fui-FluentProvider codeBlock-1659fui-FluentProviderrg ___1jk74h0 fzk5nv6 f6n0el9 f7x6x6c f1a9mlr7 flj889f f13g0yyb ffzn0d2" dir="ltr" data-testid="ComponentFluentProviderId"&gt;
&lt;DIV class="scriptor-component-code-block NhtKn7PZLzk24rduw4FJVQ== scriptor-codeblock-virtualized" tabindex="-1"&gt;
&lt;DIV class="_47QlA7XYWbfK2INfVvTUjg=="&gt;
&lt;DIV class="iVmNpJv5Hu1Eu0ev0L3Ffg=="&gt;
&lt;DIV class="KU8Z3uOm5OU11Ica53+OVA=="&gt;
&lt;DIV class="fui-Overflow Ye6tJij6H1xMCTdS6F25rA== ___s5d2bt0 f3x039c facid5"&gt;
&lt;DIV class="vCHKFE0-MqMN20DBXhx6Ow=="&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;P&gt;Expected outcome:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Successful connection → TCP should be available&lt;/LI&gt;
&lt;LI&gt;Connection refused / timeout → indicates network or service issue&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H3&gt;4. Check firewall and network restrictions&lt;/H3&gt;
&lt;P&gt;Ensure that:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Outbound traffic to the target port is &lt;STRONG&gt;allowed&lt;/STRONG&gt;&lt;/LI&gt;
&lt;LI&gt;Intermediate firewalls are not blocking TCP handshake traffic&lt;/LI&gt;
&lt;LI&gt;Network routing between ActiveGate and target is correctly configured&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;Common issues:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Denied outbound rules&lt;/LI&gt;
&lt;LI&gt;Missing return route&lt;/LI&gt;
&lt;LI&gt;Segmented networks without proper allowlisting&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H3&gt;5. Validate service availability on the target&lt;/H3&gt;
&lt;P&gt;Confirm that:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;The target host is reachable&lt;/LI&gt;
&lt;LI&gt;The specified port is open and listening&lt;/LI&gt;
&lt;LI&gt;The service supports TCP connections&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;Example checks:&lt;/P&gt;
&lt;DIV class="___77lcry0 f10pi13n"&gt;
&lt;DIV class="___1hewfwb f10pi13n f7oukh6 f5p0z4x" tabindex="0" role="group" aria-label="Code Preview"&gt;
&lt;DIV class="fui-FluentProvider codeBlock-148fui-FluentProviderrp ___1jk74h0 fzk5nv6 f6n0el9 f7x6x6c f1a9mlr7 flj889f f13g0yyb ffzn0d2" dir="ltr" data-testid="ComponentFluentProviderId"&gt;
&lt;DIV class="scriptor-component-code-block NhtKn7PZLzk24rduw4FJVQ== scriptor-codeblock-virtualized" tabindex="-1"&gt;
&lt;DIV class="CDXiecnD7ekDByb7Z+4oEA=="&gt;
&lt;DIV class="r14iuplo fui-AriaLive__assertive" aria-live="assertive"&gt;&lt;LI-CODE lang="markup"&gt;ss -tuln | grep &amp;lt;port&amp;gt;&lt;/LI-CODE&gt;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;DIV class="scriptor-code-scroll-proxy"&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;P&gt;If the service is not listening, the TCP diagnostic will fail.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H2&gt;Resolution&lt;/H2&gt;
&lt;P&gt;Once the issue is identified and resolved:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Ensure TCP connectivity from the ActiveGate host is successful&lt;/LI&gt;
&lt;LI&gt;Restart the ActiveGate service (if required to refresh diagnostics)&lt;/LI&gt;
&lt;LI&gt;Re-check &lt;STRONG&gt;Synthetic → Private locations&lt;/STRONG&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;Expected result:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;The private location no longer shows compatibility errors&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Network Availability (TCP)&lt;/STRONG&gt; becomes selectable&lt;/LI&gt;
&lt;LI&gt;TCP NAM monitors can be created successfully&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H2&gt;After resolving the cause of the failure&lt;/H2&gt;
&lt;UL&gt;
&lt;LI&gt;Re-run diagnostics via ActiveGate logs to confirm:
&lt;PRE&gt;&lt;CODE&gt;MULTIPROTOCOL_TCP = isAvailable=true
&lt;/CODE&gt;&lt;/PRE&gt;
&lt;/LI&gt;
&lt;LI&gt;Trigger an &lt;STRONG&gt;on-demand execution&lt;/STRONG&gt; to validate monitor success&lt;/LI&gt;
&lt;LI&gt;Confirm results in the Synthetic app&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H2&gt;What’s next&lt;/H2&gt;
&lt;UL&gt;
&lt;LI&gt;Consider creating multiple TCP requests within a single NAM monitor to validate multiple endpoints efficiently&lt;/LI&gt;
&lt;LI&gt;Define appropriate thresholds for connection success or failure&lt;/LI&gt;
&lt;LI&gt;Combine TCP NAM monitoring with ICMP or DNS checks for deeper network visibility&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H3&gt;Related reading&lt;/H3&gt;
&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":open_book:"&gt;📖&lt;/span&gt;&amp;nbsp; &lt;A class="fui-Link ___w5et180 f2hkw1w f3rmtva f1ewtqcl fyind8e f1k6fduh f1w7gpdv f1mo0ibp fjoy568 ff5ikls f1s184ao f1mk8lai fnbmjn9 f1o700av f13mvf36 f1cmlufx f9n3di6 f1ids18y f1tx3yz7 f1deo86v f1eh06m1 f1iescvh fhgqx19 f1olyrje f1p93eir f1nev41a" tabindex="0" href="https://docs.dynatrace.com/docs/observe/digital-experience/synthetic-monitoring/network-availability-monitors/create-a-nam-monitor" target="_blank" rel="noopener noreferrer" data-tabster="{&amp;quot;restorer&amp;quot;:{&amp;quot;type&amp;quot;:1}}"&gt;Create a NAM monitor (Dynatrace Docs)&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":open_book:"&gt;📖&lt;/span&gt;&amp;nbsp; &lt;A class="fui-Link ___w5et180 f2hkw1w f3rmtva f1ewtqcl fyind8e f1k6fduh f1w7gpdv f1mo0ibp fjoy568 ff5ikls f1s184ao f1mk8lai fnbmjn9 f1o700av f13mvf36 f1cmlufx f9n3di6 f1ids18y f1tx3yz7 f1deo86v f1eh06m1 f1iescvh fhgqx19 f1olyrje f1p93eir f1nev41a" tabindex="0" href="https://docs.dynatrace.com/docs/observe/digital-experience/synthetic-monitoring/network-availability-monitors/network-availability-monitoring" target="_blank" rel="noopener noreferrer" data-tabster="{&amp;quot;restorer&amp;quot;:{&amp;quot;type&amp;quot;:1}}"&gt;Network availability monitoring overview&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":open_book:"&gt;📖&lt;/span&gt;&amp;nbsp; &lt;A href="https://community.dynatrace.com/t5/Troubleshooting/Synthetic-Troubleshooting-Map/ta-p/250426" target="_self"&gt;Synthetic Monitoring Troubleshooting Map&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":open_book:"&gt;📖&lt;/span&gt;&amp;nbsp; &lt;A href="https://docs.dynatrace.com/docs/observe/digital-experience/synthetic-on-grail/synthetic-app/private-locations/manage-private-locations#health-status" target="_blank" rel="noopener noreferrer"&gt;Manage Private locations&lt;/A&gt;&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":open_book:"&gt;📖&lt;/span&gt;&amp;nbsp; &lt;A id="link_6" class="page-link lia-link-navigation lia-custom-event" href="https://community.dynatrace.com/t5/Troubleshooting/Useful-Synthetic-ActiveGate-logs/ta-p/214478" target="_blank"&gt;Useful Synthetic ActiveGate logs&lt;/A&gt;&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;/DIV&gt;</description>
    <pubDate>Fri, 19 Jun 2026 12:00:38 GMT</pubDate>
    <dc:creator>HannahM</dc:creator>
    <dc:date>2026-06-19T12:00:38Z</dc:date>
    <item>
      <title>Private Synthetic Location Not Available for TCP (NAM) Monitors</title>
      <link>https://community.dynatrace.com/t5/Troubleshooting/Private-Synthetic-Location-Not-Available-for-TCP-NAM-Monitors/ta-p/300882</link>
      <description>&lt;P&gt;&lt;LI-TOC indent="15" liststyle="disc" maxheadinglevel="2"&gt;&lt;/LI-TOC&gt;&lt;/P&gt;
&lt;DIV class="lia-message-template-content-zone"&gt;
&lt;P&gt;*&lt;EM&gt;Use a table of contents for longer articles.&amp;nbsp;&lt;/EM&gt;&lt;/P&gt;
&lt;H1&gt;Summary&lt;/H1&gt;
&lt;P&gt;&lt;EM&gt;*This is a mandatory section.&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;Short description of which part of the Dynatrace platform the article refers to and what kind of problem it will help resolve / task it will describe.&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H1&gt;Problem&lt;/H1&gt;
&lt;P&gt;&lt;EM&gt;*This is a mandatory section.&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;Provide a precise description of the problem / task to be described.&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H1&gt;Troubleshooting steps&lt;/H1&gt;
&lt;P&gt;&lt;EM&gt;*This section can be omitted.&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H1&gt;Resolution&lt;/H1&gt;
&lt;P&gt;&lt;EM&gt;*This section can be omitted for ticket‑creation articles.&lt;/EM&gt;&lt;/P&gt;
&lt;H1&gt;What's next&lt;/H1&gt;
&lt;P&gt;&lt;EM&gt;*This is a mandatory section.&lt;/EM&gt;&lt;/P&gt;
&lt;/DIV&gt;</description>
      <pubDate>Fri, 19 Jun 2026 12:00:38 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Troubleshooting/Private-Synthetic-Location-Not-Available-for-TCP-NAM-Monitors/ta-p/300882</guid>
      <dc:creator>HannahM</dc:creator>
      <dc:date>2026-06-19T12:00:38Z</dc:date>
    </item>
  </channel>
</rss>

