05-09-2013 08:26 AM
We are facing following error from Tidal when we are trying to connect to EC2 ( from Discover Infrastructure -> Subnets (EC2) process)
The remote name could not be resolved: 'ec2.us-west-2.amazonaws.com'
Tidal running on local IP address in the lab and configured proxy setting to get internet access. But still we see the above issue though we have internet connectivity to Tidal VM through proxy. I am not sure Tidal is able to use proxy set at windows level.
Could you please let me know if you have any suggestions to get this issue resolved.
Solved! Go to Solution.
05-09-2013 11:49 PM
If you plan to use CPO and web service activities from a machine that requires a proxy, you will also need to configure the .Net framework to use the proxy. You can also specify bypass lists.
See the following article:
http://geekswithblogs.net/ranganh/archive/2005/08/29/51474.aspx
Add the following to the C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Config\machine.config file on the CPO server.
usesystemdefault = "false"
proxyaddress="http://64.102.255.40:8080" <=== your proxy addresss and port go here
bypassonlocal="true"
/>
05-09-2013 11:49 PM
If you plan to use CPO and web service activities from a machine that requires a proxy, you will also need to configure the .Net framework to use the proxy. You can also specify bypass lists.
See the following article:
http://geekswithblogs.net/ranganh/archive/2005/08/29/51474.aspx
Add the following to the C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Config\machine.config file on the CPO server.
usesystemdefault = "false"
proxyaddress="http://64.102.255.40:8080" <=== your proxy addresss and port go here
bypassonlocal="true"
/>
05-10-2013 12:07 AM
Thank you verymuch Derek. It worked :-)
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide