🚀 go-pugleaf

Our firm creates software for the financial community and is also running into this same issue on our client's networks (banks, asset managers, pension funds, etc). Basically, Acrobat 9.0.0 is doing a DNS request and falling back to NetBIOS name resolution if the destination site is unresolvable. The app then issues hundreds of NetBIOS requests at a rate of 1-2 per second for the next two to three minutes before timing out and allowing a document to be displayed.

Turning off NetBIOS makes this problem go away - but many firms need NetBIOS. Firms running proxies, as John above noted, will also be in trouble with no workaround since the DNS resolution is not proxied.

Why is Reader trying to do local DNS/NetBIOS name resolution of the destination? What is the purpose of this resolution? This is a new behavior which is causing pain at many firms. Does anyone have insight if there is a registry key or setting that can be put into place that diaables name resolution of the destination?

The problem becomes even more severe with software that uses IE Pluggable Protocols (non-http:// or <https://> custom protocols that route through another appliation via COM) - the use of these protocols will almost guarantee that the name is not resolvable, and thus preclude the use of Acrobat 9.0.0 Reader.

Any insight from Acrobat Engineers appreciated.