ActiveX access to external networks

Today, the customer raised a headache. The customer's environment is like this: because it is a factory production environment, the LAN cannot be connected to the Internet. Some of their departments need to use ActiveX controls on the page s for hardware detection, so the options for running ActiveX are enabled on the client IE of these departments; other departments do not need to use ActiveX, the options for running ActiveX are disabled.

This is the background, but when you enter page S, the client IE that has enabled the options for running ActiveX can quickly enter the page, however, the client IE that does not have the options for running ActiveX is stuck for 4 or 5 minutes to enter the page. However, if you connect these clients with slow loading to the Internet, the speed will be faster.

The customer has a lot of opinions on this. I am not familiar with Activex and have a big head. So I searched a bunch of web pages on the Internet and found that some people said that when I load ActiveX without the codebase attribute, I would request the Internet, making loading of clients that are not connected to the Internet slow. After several queries, when ActiveX did not specify codebase, ie will go to the Registry to find the default Request Path of codebase, Which is http://activex.microsoft.com/objects/ocget.dll. The truth is, the request path cannot be requested by clients that cannot access the Internet. The page is loaded only after timeout.

Solution: You can find HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ Windows \ CurrentVersion \ Internet Settings \ in the registry. One of the keys is codebasesearchpath.

See http://support.microsoft.com/kb/323207 for details