<?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>topic Re: Cannot get to https://64.103.37.4 in DevNet Sandbox</title>
    <link>https://community.cisco.com/t5/devnet-sandbox/cannot-get-to-https-64-103-37-4/m-p/3596324#M2763</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Eddie, any news on this. I am on there right now and no routing. I will be there for rest of day,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks,&lt;/P&gt;&lt;P&gt;Padraig&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 29 Jan 2016 14:20:34 GMT</pubDate>
    <dc:creator>pmctiernan</dc:creator>
    <dc:date>2016-01-29T14:20:34Z</dc:date>
    <item>
      <title>Cannot get to https://64.103.37.4</title>
      <link>https://community.cisco.com/t5/devnet-sandbox/cannot-get-to-https-64-103-37-4/m-p/3596317#M2756</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi, is there an issue? I cannot get to it with http or https&lt;/P&gt;&lt;P&gt;thanks,&lt;/P&gt;&lt;P&gt;Padraig&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 04 Jun 2019 09:22:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/devnet-sandbox/cannot-get-to-https-64-103-37-4/m-p/3596317#M2756</guid>
      <dc:creator>pmctiernan</dc:creator>
      <dc:date>2019-06-04T09:22:10Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot get to https://64.103.37.4</title>
      <link>https://community.cisco.com/t5/devnet-sandbox/cannot-get-to-https-64-103-37-4/m-p/3596318#M2757</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Padraig- &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your inquiry! Could you let us know what sandbox you are trying to connect to? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;Jacob &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Jan 2016 16:18:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/devnet-sandbox/cannot-get-to-https-64-103-37-4/m-p/3596318#M2757</guid>
      <dc:creator>jacoadam</dc:creator>
      <dc:date>2016-01-27T16:18:58Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot get to https://64.103.37.4</title>
      <link>https://community.cisco.com/t5/devnet-sandbox/cannot-get-to-https-64-103-37-4/m-p/3596319#M2758</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;thanks Jacob, Contact Center Enterprise Environment&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Jan 2016 16:37:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/devnet-sandbox/cannot-get-to-https-64-103-37-4/m-p/3596319#M2758</guid>
      <dc:creator>pmctiernan</dc:creator>
      <dc:date>2016-01-27T16:37:16Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot get to https://64.103.37.4</title>
      <link>https://community.cisco.com/t5/devnet-sandbox/cannot-get-to-https-64-103-37-4/m-p/3596320#M2759</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Padraig- &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I have tested out the VPN connection using the credentials that you have been supplied and can connect properly using &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="https://64.103.37.4" rel="nofollow" target="_blank"&gt;https://64.103.37.4&lt;/A&gt;&lt;SPAN&gt; (please see attached screen shot)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Could you please let us know what version of AnyConnect you are using? Please also ensure that there is no firewall that could be blocking the VPN on your local machine or corporate network. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG alt="AnyConnect.PNG" class="image-1 jive-image" src="https://community.cisco.com/legacyfs/online/fusion/92490_AnyConnect.PNG" style="height: auto;" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;Jacob &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Jan 2016 16:51:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/devnet-sandbox/cannot-get-to-https-64-103-37-4/m-p/3596320#M2759</guid>
      <dc:creator>jacoadam</dc:creator>
      <dc:date>2016-01-27T16:51:58Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot get to https://64.103.37.4</title>
      <link>https://community.cisco.com/t5/devnet-sandbox/cannot-get-to-https-64-103-37-4/m-p/3596321#M2760</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;thanks Jacob, I am not even asked for credentials. A colleague can get to it so it must be my end &lt;/P&gt;&lt;P&gt;Padraig&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Jan 2016 17:10:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/devnet-sandbox/cannot-get-to-https-64-103-37-4/m-p/3596321#M2760</guid>
      <dc:creator>pmctiernan</dc:creator>
      <dc:date>2016-01-27T17:10:17Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot get to https://64.103.37.4</title>
      <link>https://community.cisco.com/t5/devnet-sandbox/cannot-get-to-https-64-103-37-4/m-p/3596322#M2761</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;working now thanks, but the inbound number does not work&lt;/P&gt;&lt;P&gt;number: +353 91 484 708&lt;/P&gt;&lt;P&gt;Agent ready: 1000&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Jan 2016 18:09:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/devnet-sandbox/cannot-get-to-https-64-103-37-4/m-p/3596322#M2761</guid>
      <dc:creator>pmctiernan</dc:creator>
      <dc:date>2016-01-27T18:09:18Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot get to https://64.103.37.4</title>
      <link>https://community.cisco.com/t5/devnet-sandbox/cannot-get-to-https-64-103-37-4/m-p/3596323#M2762</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi padraig, Ill check the call routing and get back to you when its available &lt;/P&gt;&lt;P&gt;thanks eddie&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Jan 2016 21:53:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/devnet-sandbox/cannot-get-to-https-64-103-37-4/m-p/3596323#M2762</guid>
      <dc:creator>ecorban</dc:creator>
      <dc:date>2016-01-27T21:53:29Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot get to https://64.103.37.4</title>
      <link>https://community.cisco.com/t5/devnet-sandbox/cannot-get-to-https-64-103-37-4/m-p/3596324#M2763</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Eddie, any news on this. I am on there right now and no routing. I will be there for rest of day,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks,&lt;/P&gt;&lt;P&gt;Padraig&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 29 Jan 2016 14:20:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/devnet-sandbox/cannot-get-to-https-64-103-37-4/m-p/3596324#M2763</guid>
      <dc:creator>pmctiernan</dc:creator>
      <dc:date>2016-01-29T14:20:34Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot get to https://64.103.37.4</title>
      <link>https://community.cisco.com/t5/devnet-sandbox/cannot-get-to-https-64-103-37-4/m-p/3596325#M2764</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi Im working on this.. if this is needed ASAP, then i would suggest you could reserve an CCX sandbox which has finesse. but no PSTN access. you can do local call routing however..&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 29 Jan 2016 15:17:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/devnet-sandbox/cannot-get-to-https-64-103-37-4/m-p/3596325#M2764</guid>
      <dc:creator>ecorban</dc:creator>
      <dc:date>2016-01-29T15:17:47Z</dc:date>
    </item>
  </channel>
</rss>

