Good day everyone,
I am a little bit stupid with this software now. How to I remotely monitor all connected devices on the company network, including wireless devices, for example, the IP of a workstation is 10.x.x.x and I want to see the activity of that specific device?
Thank you in advance
GlassWire is an endpoint monitor that focuses on Android/Windows.
You can monitor another Windows PC remotely. https://www.glasswire.com/userguide/#Remote_Monitoring
Our “Things” tab shows all the devices on your network and lets you know when a new unknown device joins. https://www.glasswire.com/userguide/#Things_Tab
Thank you for the information. So, in other words, I have to install glasswire on each and every pc that is being used on the network? Also, if I go to the “Things” tab, only devices connected to the DHCP server is listed and not the devices with static IP’s?
GlassWire breaks down network usage in detail by traffic, app, host, so yes you’d need to install it on the PCs where you would want these details.
If you just want to know what devices are online you can just use GlassWire’s “Things” tab, and you don’t have to install anything on other PCs.
GlassWire lists devices with static IP addresses. Is it possible those devices are on a guest network, or you are on a guest network that’s segmented from them? GlassWire can’t see devices on segmented networks that GlassWire itself cannot access due to segmentation. For example a “guest” network.
No, I am not on a guest network. My company is using a private network, IP range is 10.0.x.x. If I understand correctly, it should be on public then?
Yes, I think it should. If it is not please email us details and we’ll see what’s going on.
https://www.glasswire.com/contact/
Press the “Scan” button under “Things”.
Go to GlassWire’s General settings for automatic scanning.
I figured out why the IP’s weren’e showing. My laptop was on DHCP and not static. I set my static IP and all static IP’s is showing. Now I am just going to add the DHCP server IP range to be able to monitor those as well.
Thank you for the assistance and if I come across more problems, I will contact you.
When I tried to create a connection between the network and the monitoring service suddenly router shows connection failed with error 651 and the connection could not be created. Please help me with a proper guide so that I can fix it.
Maybe I’m misunderstanding something but GlassWire cannot interface with routers. It appears this error is related to your router and not GlassWire and GlassWire is technically unable to interface with a router and cause this error “651”.
We don’t use an error system like this, so it doesn’t appear to be a GlassWire error.
Effective network monitoring is important to help ensure that your IT infrastructure is up and running for the users that depend you. Network monitoring software like the Spiceworks Monitor can help you quickly spot and fix issues on servers, switches, VoIP phones, security cameras, and more… but what’s the best way to start keeping an eye on your critical network devices?
Whether you’re a total beginner or a seasoned pro, here are 10 steps to follow for network monitoring success. Check out these tips to make sure you’re adequately keeping tabs on your important devices and infrastructure.
Effective monitoring starts with identifying these types of devices – the ones you just can’t live without – and setting up network monitoring software to keep a close eye on them. Look for devices that support vital business functions or run applications that are heavily utilized.
Define your network monitoring policies
The scope of your network monitoring activities should be well-defined. Policies provide a way to keep everyone in the loop. Some guidelines for creating a policy include defining:
• What devices and equipment will be monitored
• What information will be collected
• Who will have access to that data
• When an alert will be triggered
• Who will be notified
• What the expected action(s) will be when something happens
Configure WMI and SSH on Windows and Linux servers
Setting up servers to work with WMI and SSH network will allow your network monitoring software to pull detailed information about your Windows and Linux systems to keep you in the know. However, to get access to data such as CPU, memory, and disk utilization, you’ll need privileged credentials for the machine you’re trying to access.
Usually it’s as simple as providing a username and password through LDAP or Active Directory, but sometimes authentication or firewall issues can arise. If that happens you may need re-configure anti-virus or open a port in your firewall, troubleshoot authentication on Windows devices or verify your SSH credentials.
networking switch
If this is the case, you’ll have to enable SNMP and set the community string, which is similar to a password. For example, here’s a quick example of how to enable SNMP on a Cisco switch. Once you define the community string on the device, you’ll also want to update your network monitoring software to reflect that change too. Another useful application for debugging connectivity issues is snmpwalk, which can provide detailed information about the device you’re trying to reach.
You should also know about exception cases, where there might be regular, expected spikes in activity. For example, you might take nightly backups after everyone goes home or run scheduled jobs every Friday at 3PM. Some servers might use more memory than usual by-design. For example, it’s actually desired behavior for a SQL server to run at 90% utilization all the time because you want the best performance possible.
Baselining is also useful for performing device-to-device comparisons. For example, if one device is suddenly experiencing unusual behavior, are other similar ones doing the same thing? Finding this out can help you get to the root of issues.
Spiceworks Network Monitor Thresholds
Alert thresholds in the Spiceworks Network Monitor
In general, you will want alerts to inform you of potentially problematic behavior, but not routine events because you don’t want to be overwhelmed by meaningless notifications that can lead to “alert fatigue” when everything is running smoothly. In other words, excessive notifications could cause you to ignore alerts about actual emergencies, like in the story of the boy who cried wolf.
So you don’t receive “false alarm” or “false positive” notifications for routine blips on the network, tweaking your thresholds and aligning them with baselines you’ve established is the key to getting relevant alerts. For example, say you’ve set a baseline for 50% CPU utilization on a particular server. If the server suddenly jumps to 95% usage for a period of time, you’ll get an email alert telling you to check out the potential issue.
Another trick best practice to reducing alert fatigue is to disable certain types of default alerts that don’t matter to you. Maybe you’re using another tool to monitor your storage, someone else in IT responds to server alerts, or checking the network activity is not your job (leave that to the overpaid network admin). Not getting unwanted notifications in the first place is much preferred to cluttering your inbox and tweaking your settings only takes a couple of minutes.
For example, if you run into something relatively simple, you could send the issue to a new employee as a training exercise. In contrast, a more complex technical issue involving a mission-critical device might require the immediate attention of a more senior staff member.
website monitoring dashboard
Many IT pros like to keep a real-time dashboard open on a second screen so they can stay informed of activity on their network. Think of it as mission control for your IT infrastructure. After the initial set up of your network monitoring software, make sure to keep everything current. Remember to update your alert thresholds if something changes in your environment or if you add new devices to ensure that you continue to get relevant alerts.
This may help you,
Rachel Gomez
