Skip to main content

Solarwinds' ipMonitor Evaluation




I was not sponsored by SolarWinds to look at this. I received the e-mail and went 'Hey, a free tool!'. You can skip the email and go right over here!

Remember - Your domain (if you're a single person using this) is more than likely COMPUTERNAME\LoginName. It's how you log in on the (local) web portal.



Scan your network within an IP range. If you leave the settings as they are, chances are you're scanning for about 75k IP addresses - and SolarWinds will let you know!

Welcome to the dashboard:


(I can show you the IP addresses because they're local to my network and not public for internet consumption!)

There's a very early 2000s feel which I kind of adore.


Scanning the network did not put my phone 'on the map'. I put in my phone's IP address to see if it could be found. They're on the same network. This nifty screen popped up with how I can monitor myself!




I removed the Active Directory option.

(Remember, this is the range of private IP addresses.)

I can set up an email alert if the phone fails.



Here are all of the devices being managed...all 2 of them.


A closer look at the phone:



The status is suspended...what does that mean in this context? Well, that's when we hit 'help' in the upper right hand corner and are taken to the online guide.





There's that 2000s style again! 


When my phone times out, ipMonitor catches it;



And here is a snazzier (partial) view on what is being monitored on the phone.


While the scanner did not pick up on many network devices, I consider that something I did. Suspicions involve Xfinity router preventing a ping sweep. It would probably act accordingly if you were using this with enterprise level equipment.

Putting in my phone's IP address was easy, and it was seen and able to be monitored quickly.

As this is only a demo with a limited network, so far, this is the gist of it.


EMPLOYERS: Find things, use things. This shows adaptability (scan doesn't work? Put it in manually), learning, and documentation.

Comments

Popular posts from this blog

Connecting IoT Devices to a Registration Server (Packet Tracer, Cisco)

In Packet Tracer, a demo software made by Cisco Systems. It certainly has changed a lot since 2016. It's almost an Olympic feat to even get started with it now, but it does look snazzy. This is for the new CCNA, that integrates, among other things, IoT and Automation, which I've worked on here before. Instructions here . I don't know if this is an aspect of "Let's make sure people are paying attention and not simply following blindly", or an oversight - The instructions indicate a Meraki Server, when a regular one is the working option here. I have to enable the IoT service on this server. Also, we assign the server an IPv4 address from a DHCP pool instead of giving it a static one. For something that handles our IoT business, perhaps that's safer; Getting a new IPv4 address every week or so is a minimal step against an intruder, but it is a step. There are no devices associated with this new server; In an earlier lab (not shown), I attached them to 'H

Building, Breaking, and Building A CRM with Retool

 I like no- or low-code solutions to things. I've often wanted to simply push a button or move some GUI around and have the code implement itself.  I've thought about building something that's like a customer relationship management (CRM) system for keeping up with my network better than my little spreadsheet where I click links and then go like something. The general idea in this CRM Development is:  To have a GUI to add people to a NRM (Network Relationship Management).       Attach it to a database (MySQL is what I went with eventually using Amazon Relational Database service, but you can use PostGRES, and probably others).     Make sure components are connected to each other in the retool interface. This video is a good start. Watching the tutorial video, heard some SQL commands and went 'Oh no 😳" before going "Wait I know basic SQL", which is good, because you'll see.  When you get set up, there's a plethora of resources you can use -- Incl

Securing Terraform and You Part 1 -- rego, Tfsec, and Terrascan

9/20: The open source version of Terraform is now  OpenTofu     Sometimes, I write articles even when things don't work. It's about showing a learning process.  Using IaC means consistency, and one thing you don't want to do is have 5 open S3 buckets on AWS that anyone on the internet can reach.  That's where tools such as Terrascan and Tfsec come in, where we can make our own policies and rules to be checked against our code before we init.  As this was contract work, I can't show you the exact code used, but I can tell you that this blog post by Cesar Rodriguez of Cloud Security Musings was quite helpful, as well as this one by Chris Ayers . The issue is using Rego; I found a cool VS Code Extension; Terrascan Rego Editor , as well as several courses on Styra Academy; Policy Authoring and Policy Essentials . The big issue was figuring out how to tell Terrascan to follow a certain policy; I made it, put it in a directory, and ran the program while in that directory