ArcGIS Explorer Online - Cannot access ArcGIS Server located on internal network

DennisGeasan

I'm unable to open ArcGIS Server map services with ArcGIS Explorer Online.  I have set up a clientaccesspolicy.xml file and am able to access map services using an internal Silverlight application with no problem.  In the 'My Content' section of ArcGIS Online I am able to view the internal map services when using the ArcGIS.com map viewer application.

This has to be a problem with permissions for ArcGIS Explorer Online to access the internal map services.  I have tried several variations in the policy file but nothing is working.

Is it possible there is a firewall issue?

Can anyone see an error in the policy file.

This is the current one.

<?xml version="1.0" encoding="utf-8" ?>
<access-policy>
<cross-domain-access>
  <policy>
   <allow-from http-request-headers="*">
    <domain uri="*"/>
    <domain uri="http://*"/>
   </allow-from>
   <grant-to>
    <resource path="/" include-subpaths="true" />
   </grant-to>
  </policy>
</cross-domain-access>
</access-policy>

Others I have tried:

<?xml version="1.0" encoding="utf-8" ?>
<access-policy>
<cross-domain-access>
  <policy>
   <allow-from http-request-headers="*">
    <domain uri="http://*"/>
   </allow-from>
   <grant-to>
   <resource path="/" include-subpaths="true"  />
   </grant-to>
  </policy>
  <policy>
   <allow-from http-request-headers="*">
    <domain uri="https://arcgis.com"/>
   </allow-from>
   <grant-to>
   <resource path="/" include-subpaths="true"  />
   </grant-to>
  </policy>
</cross-domain-access>
</access-policy>

<?xml version="1.0" encoding="utf-8" ?>
<access-policy>
<cross-domain-access>
  <policy>
   <allow-from http-request-headers="*">
    <domain uri="http://*"/>
    <domain uri="https://*"/>
   </allow-from>
   <grant-to>
   <resource path="/" include-subpaths="true"  />
   </grant-to>
  </policy>
</cross-domain-access>
</access-policy>

Any help much appreciated.

Dennis Geasan

BrianHaren

Dennis,

We had the same issue in my organization.  Configuring the client access policy never solved it.  However, we finally figured out that if we called the service using the server IP address instead of the server name that solved the issue.

Brian