PAC File?

[Anonymous]

Hi,

Does AutoDesk (AutoCad LT 2014) support PAC Files?

I cannot license Autodesk when accessing via a pac file, pointing the client directly to the proxy server works (following previous advice on Proxy configuration and hotfix cve-2014-3566).

I have ran a trace route on the client and cannot see any failed connections from Autodesk, but it doesnt appear to redirect the full traffic to the proxy (when using the pac file) as if Autodesk doesnt understand the pac redirection.

I have seen many posts about this issue, but not found an answer or comment from Autodesk?

Thanks.

[BJ.C]

Multiple posts error - see post below.

[BJ.C]

Hello @Anonymous

I'm not familiar with PAC files but I understand it involves a proxy.  Let me share something that may be useful.

Finding ways to activate an Autodesk product from behind a proxy can be challenging.  There are no guarantees that an activation is possible on all proxy configurations especially when 3rd-party software is involved. 

The first solution may activate your product with no further configuration necessary:

https://knowledge.autodesk.com/search-result/caas/sfdcarticles/sfdcarticles/For-Desktop-Subscription...

Autodesk desktop subscriptions require a connection to the Autodesk license server to maintain the license. 

https://knowledge.autodesk.com/search-result/caas/sfdcarticles/sfdcarticles/Meta-licensing.html

For advanced proxies I would show your network Administrator the following article:

https://knowledge.autodesk.com/support/autocad/troubleshooting/caas/sfdcarticles/sfdcarticles/AutoCA...

This is probably the most IMPORTANT information when dealing with proxy servers:

To use Autodesk online components through proxy servers with Authentication enabled:

Enable http (port 80) and https (port 443) access to the following domains in the proxy without Proxy Authentication (i.e. Access for “All users” or Anonymous access through the proxy):

*.autodesk.com 

*.google-analytics.com 

*.cloudfront.net 

*.virtualearth.net 

*.autocadws.com 

*.newrelic.com 

*.akamaiedge.net 

*.amazonaws.com 

*.getsatisfaction.com 

*.autodesk360.com  

*.skyscraper.autodesk.com

*.ssl.google-analytics.com 

*.js-agent.newrelic.com

Thank you for taking part in our community forum!

Kind Regards,

[Anonymous]

Thanks for the reply BJ. C, but I have already found these suggestions and this is not my issue.

A PAC file or  Proxy Auto-configuration file is a shared file containg javascript, which directs requests to a proxy or proxies. In my organisation it is used for fail over incase a proxy fails.

Our config is very simple and just confirms the domain the request is coming from, then redirects all traffic to a proxy, or a second proxy if the first proxy fails.

The problem appears to be that after checking with the PAC file the software attempts to direct part of the traffic directly to the internet, rather than via our proxy (traffic to autocadws.com does get sent to the proxy correctly).

The proxy has already been confirgued as Autocad/forums suggested and when sending dircetly to the proxy I am able to activate the license.

[Anonymous]

Hi,

did you finally solved the issue, if yes can you share your solution.

Many thanks

[Anonymous]

No real solution, but found a work around...

The application does not understand the PAC redirection and will not let you initially authenticate your license, so I modified the registry of the machines with the installation (pointed them directly towards the proxy) to allow the registration/authentication of the licenses and then re set the reg file back to the PAC redirection.

I could have done this via GPO/AD group, but my security team were concerned about 'leaving' machines in this group and felt the manual option was less risky for us.

The application itself will work behind a PAC file after the initial authentication, so I have not had any further issues.