Q&A
Windows Platform

Q. When I installed ASWM on a Windows 2003 Server Enterprise Edition, I cannot browse the web page of a specific IP address after I login.
 or
Q. When I installed ASWM on a Windows 2003 Server Enterprise Edition and connect to the web page, the system told me that ASWM was blocked by the browser's enhanced security configuration.

A. In the former question, you may see the content of browser as the following figure.


Fig. Blank content of web pages


In the latter question, you may see the security alert dialog popped up as the following figure.


Fig. Security alert dialog of web pages


In the former case, you can turn on an option of browser and then you will see the same result in the latter case.


Fig. Turn on the security alert dialog of browser


Normally speaking, both of these two problems are the same issues. To browse web content by the Microsoft Internet Explorer in a Windows 2003 Server Enterprise Edition, you have to follow the security guideline when the web content needs higher security accessibility to your system. As you know that ASWM web page is operated under a privileged user identity called "aswm user" which is very different from the ordinary anonymous (or uncensored) accessing. ASWM needs to retrieve the system resources from your hardware, hence it only works under the certain user privilege.

To grant your ASWM web page to be accepted by your browser, you should tell the browser those IP address of hosts that ASWM installed. When you are warned that you will be blocked by the unsafe content, you are allowable to add the IP address by click "Add" button. After clicked that button, the browser will always remember those "confirmed-to-be-safe" IP addresses. Next time, you should never encounter any failed connection to the ASWM web pages.



Q. When I installed ASWM on a Windows 2003 R2 Enterprise Edition X64 Version, Two warning events in the Event Viewer are always shown. I was told that SNMP service ignored two mis-configured (or missing) extension agent dll snmpagt.dll and ecsnmpagent.dll. What happened there?

A. The Event Viewer always show the events as following figure whenever the SNMP service is started or re-started (After complete installation of ASWM or reboot system next time).


Fig. SNMP Service complained about ecsnmpagent.dll


and


Fig. SNMP Service complained about snmpagt.dll


This is an implementation consideration. Currently, ASWM only has common 32-bit SNMP agent DLLs but SNMP Service in Windows X64 (64-bit SNMP Service) requries 64-bit SNMP agent DLLs. However, the DLL files, which are 32-bit, with the name of "snmpagt.dll" and "ecsnmpagent.dll" may confuse 64-bit SNMP Service and it tries to load them as 64-bit agent DLLs, After it failed, the other 32-bit SNMP Service will try to load these agent DLLs again without any problem. All the SNMP agent functions will still work properly

In the future, ASWM will fully support all x64 edition after all 32-bit Windows phase-out.

Linux Platforms

Not available.