What is Reddit's opinion of
PingTools Network Utilities?
From 3.5 billion Reddit comments
Popularity Score: 23
This app was mentioned in 27 comments, with an average of 3.19 upvotes
Best Comments
1) Don't let random people stay at your place
2) Use your router to check for devices you don't recognize. If you don't know how to do this and use Android, use this app and name all the devices it can see before renting out your place
3) Check outlets and inside your computer for a small, credit-card-sized board
4) Don't have a Wi-Fi network available to the visitors, or at least look into setting up a "guest" Wi-Fi network. Most modern routers have this built in, read the manual that came with your device.
Not all networks interconnect. Try a traceroute between your mobile network on your nexus, and your home IP network...
Pingtools has a trace option, but I've never used it, so I'm not sure how good it is.
See where the failure might lie. The last IP to respond is probably very close to the problem.
As per link:
" On PC/Mac, download the iperf3 client, open a command line/terminal window in the same folder where the iperf3 client is and enter the command ./iperf3 -c [ipaddress of your nas]
For example, on my network the command is ./iperf3 -c 192.168.1.10
The network test should now start. "
The iperf3 is started from the clients side, so you need to download it to your Windows/Mac machine. In cli navigate go the folder and use the command "./iperf3 -c xxx.xxx.xxx.xxx" where xxx.xxx.xxx.xxx your NAS ip is.
On Android you can use this app that has ipef support.
Could be connectivity I guess. Maybe install a network utility app and see if you can ping, trace route, etc.? https://play.google.com/store/apps/details?id=ua.com.streamsoft.pingtools&hl=en\_US&gl=US
My guess is something was changed in a firewall that is blocking some traffic.
Are you certain the LAN NIC is eth0? A lot of setups use unique names now (which I hate) but are 'stable' like enp0s0 and don't change between reboots.
You need a node outside of your network to test things with.
Maybe your phone set to LTE will work or if you have a VPS to use that's the nicest.
Get a traceroute program for your phone. Something like ping tool
Are you trying to connect to the wg hub when you are on the LAN? There's potential for that to cause issues because you're on the network it's routing over and if your laptop receives an ICMP redirect it'll break the NAT. That's why getting a node outside the LAN will help debug it. Eliminating the NAT will allow the network to work as IP intended it to but this means it will stop going over wg when you're on the LAN or some packet will and some won't.
If your remote network happens to be 192.168.1./24 that will also break it.
You might want to make your home LAN something less commonly used.
The problem is more likely in your wireless AP around client isolation/multicast filtering. You can use https://play.google.com/store/apps/details?id=ua.com.streamsoft.pingtools&hl=en_US specifically the UPnP scanner to see if those multicast packets are getting to your android device
When you wrote resolve, did you mean connect instead?
Can you try a couple quick checks?
When you do an nslookup on your hostname, does the result match what you get from visiting whatismyip.com?
Try nslookup <hostname> 8.8.8.8
If dns is broken, this needs to be fixed first. You cannot effectively use and secure https without this
From outside your network, are you able to connect to 80 and 443? Android app: https://play.google.com/store/apps/details?id=ua.com.streamsoft.pingtools If you get a connection refused message, you're getting though the router, but your PC isn't listening. All other failures are often attributed to some kind of blocking.
You can set it up to listen on non standard ports, but the normal certbot challenge requires you to listen on port 80. Some of the other challenge methods can be used, but it typically requires the ability to create txt records. See https://certbot.eff.org/docs/using.html#certbot-command-line-options I don't see no-ip listed here, so let's hope that isn't necessary.
My 2 cents: These public dynamic dns servers can be good, but the domain is not in your control. Should you ever find yourself storing sensitive information in your installation, purchase a domain, and use that.
No worries!
There are a bunch of ping apps for Android, here's one I chose at random:
https://play.google.com/store/apps/details?id=ua.com.streamsoft.pingtools
Grab that, hit the hamburger menu top left, 4th option is ping. Choose that, type in the name of your Windows machine you want to RDP to, it'll either say Unknown Host or it'll give your a round-trip time in ms of how long it takes.
Try that and report back. :)
(edit: spelling)
Maybe try a port scan on your public IP from an external source? If you have Android here is a good app full of networking utilities including port scanning that I use all the time.
https://play.google.com/store/apps/details?id=ua.com.streamsoft.pingtools
If there are lots of other wi-fi networks around your apartment you should check if they are interfering with your network, one way to do this is to check what wi-fi channels are all the networks using and set your router to use the one with least interference. An easy way to check these wifi channels is to use an app on your phone for egzample PingTools on android.
Not quite using Smart things..
But my Plex server (Dedicated RPi 2) and home PC have ports exposed to the web. Using my Android phone I then use the PingTools Network Utilities to monitor my IP and the ports of each device on my network. I could probably setup a Raspberry Pi to do the same thing as the app more reliably.... but i'm too lazy to bother.
are you able to ping from your galaxy tab to your PMS? Could be the firewall on the server blocking your android tab/IP
You can use PingTools to ping from your tab to pms
I switched to pingtools, very much the same functions, but much, much sleeker.
Try Ping Tools
In the past I have random stuff like this crop up with my Google Home Mini Speakers.
Here are two possible solutions for you to try.
Number 1: You might be having issues with IPV6. Some providers have been enabling IPV6 without full upstream compatibility. If this is the case, the solution is easy. Log into your router and disable IPV6. This seems to be a common problem: https://www.googlenestcommunity.com/t5/Speakers-and-Displays/quot-There-was-a-glitch-quot-on-first-try-but-works-second-time/m-p/22742/highlight/true
Number 2: ICMP packets might be blocked on your wifi. This turned out to be my problem. Any time I issued a request, (for example, "hey Google, turn on the bedroom light,") Google Home would just light up for about 30 seconds and then eventually respond with, "something went wrong, please try again."
Usually issuing the same voice request a second time, resulted in success, but not always, sometimes it took three or four tries. I replaced my router, three times, verified my connection speed, (220 down, 10 up, and stable.) I cleared the cache in my Home app and assistant, plus I reset and re- paired all my minis more than once. Still had the same problem. My wife was getting pretty aggravated, she has much less patience with technology than I do. I was pulling my hair out for a solution.
Finally I managed to fix my problem. Turns out, for reasons unknown, ICMP packets were being blocked on my wifi. I could find no reason for this, or settings in any of my routers that controlled ICMP filtering. I went through a total of three routers, and with every thing I tried, sure enough ICMP was being blocked. Finally, out of desperation, I flashed one of the routers that supported it with DD-WRT. Bingo ICMP works perfectly. I moved all my google minis to that router, and now everything works pretty normal now.
Don't ask me why or how ICMP was the problem for me, bottom line is everything works pretty normal now. Here is a Wikipedia link about ICMP and what it does: https://en.wikipedia.org/wiki/Internet_Control_Message_Protocol and here is a wikipedia link for DD-WRT: https://en.wikipedia.org/wiki/DD-WRT and this is the app that I used to check my network, https://play.google.com/store/apps/details?id=ua.com.streamsoft.pingtools
I hope these will help you, good luck.
In the past I have random stuff like this crop up with my Google Home Mini Speakers.
Here are two possible solutions for you to try.
Number 1: You might be having issues with IPV6. Some providers have been enabling IPV6 without full upstream compatibility. If this is the case, the solution is easy. Log into your router and disable IPV6. This seems to be a common problem: https://www.googlenestcommunity.com/t5/Speakers-and-Displays/quot-There-was-a-glitch-quot-on-first-try-but-works-second-time/m-p/22742/highlight/true
Number 2: ICMP packets might be blocked on your wifi. This turned out to be my problem. Any time I issued a request, (for example, "hey Google, turn on the bedroom light,") Google Home would just light up for about 30 seconds and then eventually respond with, "something went wrong, please try again."
Usually issuing the same voice request a second time, resulted in success, but not always, sometimes it took three or four tries. I replaced my router, three times, verified my connection speed, (220 down, 10 up, and stable.) I cleared the cache in my Home app and assistant, plus I reset and re- paired all my minis more than once. Still had the same problem. My wife was getting pretty aggravated, she has much less patience with technology than I do. I was pulling my hair out for a solution.
Finally I managed to fix my problem. Turns out, for reasons unknown, ICMP packets were being blocked on my wifi. I could find no reason for this, or settings in any of my routers that controlled ICMP filtering. I went through a total of three routers, and with every thing I tried, sure enough ICMP was being blocked. Finally, out of desperation, I flashed one of the routers that supported it with DD-WRT. Bingo ICMP works perfectly. I moved all my google minis to that router, and now everything works pretty normal now.
Don't ask me why or how ICMP was the problem for me, bottom line is everything works pretty normal now. Here is a Wikipedia link about ICMP and what it does: https://en.wikipedia.org/wiki/Internet_Control_Message_Protocol and here is a wikipedia link for DD-WRT: https://en.wikipedia.org/wiki/DD-WRT and this is the app that I used to check my network, https://play.google.com/store/apps/details?id=ua.com.streamsoft.pingtools
I hope these will help you, good luck.
In the past I have random stuff like this crop up.
Here are two possible solutions.
Number 1: You might be having issues with IPV6. Some providers have been enabling IPV6 without full upstream compatibility. If this is the case, the solution is easy. Log into your router and disable IPV6. This seems to be a common problem: https://www.googlenestcommunity.com/t5/Speakers-and-Displays/quot-There-was-a-glitch-quot-on-first-try-but-works-second-time/m-p/22742/highlight/true
Number 2: ICMP packets might be blocked on your wifi. This turned out to be my problem, any time I issued a request, (for example, "hey Google, turn on the bedroom light,") Google Home would just light up for about 30 seconds and then eventually respond with, "something went wrong, please try again."
Usually issuing the same voice request a second time, resulted in success, but not always, sometimes it took three or four tries. I replaced my router, three times, verified my connection speed, (220 down, 10 up, and stable.) I cleared the cache in my Home app and assistant, plus I reset and re- paired all my minis more than once. Still had the same problem. My wife was getting pretty aggravated, she has much less patience with technology than I do. I was pulling my hair out for a solution.
Finally I managed to fix my problem. Turns out, for reasons unknown, ICMP packets were being blocked on my wifi. I could find no reason for this, or settings in any of my routers that controlled ICMP filtering. I went through a total of three routers, and with every thing I tried, sure enough ICMP was being blocked. Finally, out of desperation, I flashed one of the routers that supported it with DD-WRT. Bingo ICMP works perfectly. I moved all my google minis to that router, and now everything works pretty normal now.
Don't ask me why or how ICMP was the problem for me, bottom line is everything works pretty normal now. Here is a Wikipedia link about ICMP and what it does: https://en.wikipedia.org/wiki/Internet_Control_Message_Protocol and here is a wikipedia link for DD-WRT: https://en.wikipedia.org/wiki/DD-WRT and this is the app that I used to check my network, https://play.google.com/store/apps/details?id=ua.com.streamsoft.pingtools
I don't know if these will help you, good luck.
In the past I have random stuff like this crop up. Some time a few months ago k I was having major problems with Google Home, any time I issued a request, (for example, "hey Google, turn on the bedroom light,") Google Home would just light up for about 30 seconds and then eventually respond with, "something went wrong, please try again." Usually issuing the same voice request a second time, resulted in success, but not always, sometimes it took three or four tries. I replaced my router, three times, verified my connection speed, (220 down, 10 up, and stable.) I cleared the cache in my Home app and assistant, plus I reset and re- paired all my minis more than once. Still had the same problem. My wife was getting pretty aggravated, she has much less patience with technology than I do. I was pulling my hair out for a solution.
Finally I managed to fix my problem. Turns out, for reasons unknown, ICMP packets were being blocked on my wifi. I could find no reason for this, or settings in any of my routers that controlled ICMP filtering. I went through a total of three routers, and with every thing I tried, sure enough ICMP was being blocked. Finally, out of desperation, I flashed one of the routers that supported it with DD-WRT. Bingo ICMP works perfectly. I moved all my google minis to that router, and now everything works pretty normal now.
Don't ask me why or how ICMP was the problem, bottom line is everything works pretty normal now. Here is a Wikipedia link about ICMP and what it does: https://en.wikipedia.org/wiki/Internet_Control_Message_Protocol and here is a wikipedia link for DD-WRT: https://en.wikipedia.org/wiki/DD-WRT and this is the app that I used to check my network, https://play.google.com/store/apps/details?id=ua.com.streamsoft.pingtools
Last week I was having major problems with Google Home... And I was able to solve it, for the most part. Though my problem was not exactly like yours, the reasons might be related. Any time I issued a request, (for example, "hey Google, turn on the bedroom light,") Google Home would just light up for about 30 seconds and then eventually respond with, "something went wrong, please try again." Usually issuing the same voice request a second time, resulted in success, but not always, sometimes it takes three or four tries. I replaced my router, three times, verified my connection speed, (220 down, 10 up, and stable.) I cleared the cache in my Home app and assistant, plus I reset and re- paired all my minis more than once. Still had the same problem. My wife was getting pretty aggravated, she has much less patience with technology than I do. I was pulling my hair out for a solution.
Finally I managed to fix my problem. Turns out, for reasons unknown, ICMP packets were being blocked on my wifi. I could find no reason for this, or settings in any of my routers that controlled ICMP filtering. I went through a total of three routers, and with every thing I tried, sure enough ICMP was being blocked. Finally, out of desperation, I flashed one of the routers that supported it with DD-WRT. Bingo ICMP works perfectly. I moved all my google minis to that router, and now everything works pretty normal now.
Don't ask me why or how ICMP was the problem, bottom line is everything works pretty normal now. Here is a Wikipedia link about ICMP and what it does: https://en.wikipedia.org/wiki/Internet_Control_Message_Protocol and here is a wikipedia link for DD-WRT: https://en.wikipedia.org/wiki/DD-WRT and this is the app that I used to check my network, https://play.google.com/store/apps/details?id=ua.com.streamsoft.pingtools
Ah, ok... Für nen Ping vom Smartphone gibt's Apps. Android z.B.: https://play.google.com/store/apps/details?id=ua.com.streamsoft.pingtools&hl=en
from my experience, still haven't found anything better than this:
https://play.google.com/store/apps/details?id=ua.com.streamsoft.pingtools
My favorite - PingTools
https://play.google.com/store/apps/details?id=ua.com.streamsoft.pingtools&hl=en