AutoCad freezes with Chrome installed

[Anonymous]

We recently swapped out our firewall and since then we are unable to use our products. The application launches, there are no errors, but the application doesn’t respond to any type of input. The only thing I can do is close the application from task manager.

If I uninstall Google Chrome, the product seems to work fine. We have 18 sites across the US, and this seems to be happening at 10 sites.

[Anonymous]

Forgot to mention, this is AutoCad 2018.

[john.vellek]

Hi @Anonymous,

I see that you are visiting as a new member to the AutoCAD forum. Welcome to the Autodesk Community!

Please check the proxy exceptions and settings in this article to see that they have been applied to your new firewall.  I assume that if you bypass the firewall, that everything works as expected.

Please select the Accept as Solution button if my post solves your issue or answers your question.

[Anonymous]

We’ve spent the better part of 5 days taking packet captures, adding exceptions, etc, with the manufacturer of both our firewall, AutoCad, as well as antivirus, with no resolution. I can put a allow all any any to the user and it results in the same issue, so no, everything does not work as expected. I was hoping someone had the same issue. Seems to only happen once a user has google chrome installed. If I borrow a license and take the user off the network completely it seems to work.

[john.vellek]

Hi @Anonymous,

Which version of Chrome is installed and on which OS?  From what I have been researching, some version s of Chrome have intermittent issues with port monitor.  My version is Version 65.0.3325.181 (Official Build) (64-bit).

Please confirm that AutoCAD is working properly if you bypass your firewall.  If so and you add Chrome back onto the computer, does AutoCAD then have problems?

[Anonymous]

Latest version of Chrome. This is on Windows 10.

Sometimes it works behind the firewall with our normal rules applied as long as chrome isn’t on the station.

[john.vellek]

Hi @Anonymous,

Please take a look at the solution on this other thread.  Development is still examining this but it seems to correct the behavior for a couple of customers.