I see an issue in the debug log related to a defect associated with build 6.4. The UPS APC probe would cause the service to stop. We recently released build 6.4.1 last week and it contains a fix for the defect.
Can you please upgraded to build 6.4.1 and let me know if the issue continues?
6.4.1 Download - https://community.helpsystems.com/products-and-downloads/downloads/
I reopened case - CAS-0010073933 - no SNMP response
I will follow up with you over email shortly.
Generally, if the SNMPwalk shows results and Intermapper is saying No SNMPv2c response it's due to the community string not entered in correctly.
If you can open the information window > Probes Tab > Double click on the probe > try re-entering the SNMP community string and see if that works. If it doesn't help let me know and I'll open a case to look into this further.
If the version of Intermapper is 5.8 or higher, it will not require internet access because the registration is completed within the software itself.
If the version of Intermapper is 5.7.1 or lower, please contact [email protected]m for further instructions.
The InterMapper polling engine is single-threaded, so nearly all work done by intermapper.exe/intermapperd is restricted to a single CPU. Adding more CPU is not helpful in the case a single-threaded (vs multi-threaded) architecture.
No combination of CPU/RAM will allow InterMapper to monitor more devices once it reaches its limit. Choices are to poll less often (longer polling interval), monitor fewer interfaces/device on average for SNMP probed devices, change the probe mix to use more lightweight probes (like ping/echo), or to expand to an additional server by shifting some of the maps (chart data continuity can be a problem in this case).
In order to use the WMI probe, the Intermapper server will have to be on a Windows Operating System. The WMP probe uses the Windows RPC service to send WMI requests to remote Windows boxes. Linux and Mac don’t have Remote Procedure Call code in their OS. It’s a Microsoft service.
603.643.9600 | www.helpsystems.com
Please go to the Intermapper Server and stop the InterMapper service, rename your Web Pages folder and restart the InterMapper service.
You can rename it to anything you like. Once it has a different name and the service has been restarted it will create a new folder called “Web Pages” and that should get the web page to look normal again.
Keep in mind that ProgramData on a Windows server may be a hidden file. The Intermapper Settings folder can be located here per OS.
For the web server – Edit > Server Settings > Web Server > Edit the port number in this window.
User guide web server documentation - https://static.helpsystems.com/intermapper/help/userguide/Content/08-Server_Settings/08-03-Server_Config/Web_Server.htm?Highlight=web%20server
You should be able to edit the port number right from Edit > Server Settings > Telnet Server
Here is a link to the User Guide’s section related to the Telnet Server - https://static.helpsystems.com/intermapper/help/userguide/Content/08-Server_Settings/08-03-Server_Config/Telnet_Server.htm?Highlight=telnet
Let me know if you have any questions.
603.643.9600 | www.helpsystems.com
Unfortunately, something like this doesn't exist yet. However, it's a great idea so I created an enhancement request for us to create an error reference section in our user guide and community portal. You have been added a contact to the request so any updates will generate an email notification to you. The Enhancement Request article number is KBA-36489-D0G4Y1 for your reference.
We have had several customers report that running Intermapper Remote Access on a Windows OS can make the text unreadable. Changing the screen resolution makes no difference.
Please try the following solution.
Go to C:\Program Files (x86)\InterMapper RemoteAccess > right click on InterMapper_RemoteAccess.exe > Properties > Compatibility > check Override high DPI scaling behavior, Scaled performed by > then change (drop down menu} below it to System Enhanced.
So far, the following hardware listed below have been reported to have this issue.
Windows 10 Education