What is our primary use case?
My use cases revolve around determining
- how much PoE power is coming out
- if I have the port configured so that it will present me with an IP address for that access point
- what port that I have it plugged into on the switch.
I use it for other things as well, but those are the day-to-day uses, 98 percent of the time.
How has it helped my organization?
I plug in the unit and it will tell me good things like how much PoE power is coming out and whether it can support one of the fanciest wireless access points. In addition, I will know if I have the port configured so that it will present me with an IP address for that access point, and what port I have it plugged into on the switch.
I don't necessarily need to take a laptop with me anymore. I like that I don't have to carry multiple tools to do the basic job of knowing if the cable is good, or if the port or network is available to do the job. It reduces the amount of equipment you need.
The ability to streamline installation and triage is helpful. For example, I had a job where I rewired a room. I had all the cables going to the network closet and terminated all of them. I plugged them all into the network switch, and then it was a matter of going from port to port to port in that room to see whether or not they all had basic connectivity. The results I was able to get with LinkRunner met my "hurry up, let's see if they all work" requirement so that I could put the room and all the furniture back together quickly.
In terms of troubleshooting, it helps when it comes to PoE. If I need a Class 3 or Class 4 level of power, meaning I need all 30 watts to be coming out of my network switch to be able to boot up an access point, I can plug the unit into a network jack and it will tell me if that jack is presenting the amount of power necessary. If not, it will tell me what it did put out. That lets me know there's either something wrong with the cable or the cable run is too long to present the needed power over that distance.
Another example where it helped with troubleshooting was in pulling up IP and DNS. I found out that at a particular site I was actually getting my responses for DCP and DNS from my failover site, not from the primary. That let me know that there was something wrong. When I looked into it in more detail, I found out that the response time was slower from the local server than it was from the remote server. That clued me in that I needed to tell somebody about that.
If I compare the time it takes me now, versus my old mindset of four years ago, to do a single job, LinkRunner has cut it down to about one-third of the time. It has made me more productive.
What is most valuable?
I like the fact that I can tell the equipment to stop at a certain point during the test of a cable, to see whether or not there is basic connectivity. I can stop it before it starts pinging the outside world, such as Google or, perhaps, our core network switch. Those basic results—do I have a basic connection and power—finish up fast and I can move on. The fact that I can stop it at certain points, if that's the targeted job for the day, is helpful. It does the job fast enough, producing accurate information every time.
I don't use the online results because I don't pay for the account. Right there, on the spot, the handheld gives me what I need to know. I don't have to report to anybody else. I am the guy who needs the information.
The AutoTest feature is pretty much the only button I use. It provides me with 100 percent of the information I need. There are a lot of other cool things available, like speed tests, but I don't use them. The Auto-Test gives me the POE, the DNS, DCP, responses, and which switchport it is on. That one button gives me all the most important information for my needs.
Overall, what I like about it is that I can do jobs quickly and tailor them in a way that I like.
What needs improvement?
Other than the battery not lasting long, it's easy to use.
A feature that I would like to see is the ability to send a tone down the cable. That would be great. I have to use a separate tool for that. If I'm trying to troubleshoot a cable that is not plugged into a network switch, I need the ability to tone.
Buyer's Guide
LinkRunner
June 2026
Learn what your peers think about LinkRunner. Get advice and tips from experienced pros sharing their opinions. Updated: June 2026.
900,747 professionals have used our research since 2012.
For how long have I used the solution?
I have used two or three different products from NetAlly, but I have been using the LinkRunner 10G for about a year.
What do I think about the stability of the solution?
I've had no issues with it at all.
How are customer service and support?
I used the technical support one time when I wondered what happened to my online account. I found it was no longer there because that amount of time is what you get with the product. You don't get the online features forever.
When I asked about the software updates, I got all the answers quickly and they were clear. The tech support provided me with the answers to my questions. They weren't necessarily the answers I wanted to hear, but at least they were the answers to my questions.
Which solution did I use previously and why did I switch?
I have used the company's older products. I also have some Fluke equipment, but not the type that runs IP lookup and the functions that the LinkRunner has. The Fluke equipment is not the same.
How was the initial setup?
Was it easy to figure out, out-of-the-box? I would say that the typical guy doesn't read the manual. If creating the Link-Live Cloud Service account wasn't part of the initial process, the time it would have taken me to figure it out would have been about 30 seconds. And 20 seconds of that was because it took that long to boot up. It's extremely easy. It's just that they send you through a lot of steps to enjoy the Cloud Service features that, after that initial time frame, I didn't use.
What's my experience with pricing, setup cost, and licensing?
Compared to another company's product, LinkRunner is cheaper, but it's still about $1,000 too expensive, considering that the operating system is a free operating system. The OS has just been tweaked to give you a graphical interface. I don't think it's priced right. I don't consider it to be of appropriate value, even though it's cheaper than the competitor. The price is just too high.
If it were $1,000 cheaper, we would see ISDs (independent school districts) using this product. The local ISD here saw me using the product and didn't know about it. When they realized how expensive it was, they weren't able to purchase it.
You do get the ability, out-of-the-box, to save test results automatically to NetAlly’s Link-Live Cloud Service, but it's not a free cloud after your initial subscription. I looked at it and was able to see the results online, but it was useless to me. I don't need to pay for something that's not necessary for this college. Nobody needs that data. For me, the online account and the ability to put things up on the cloud is not important.
Which other solutions did I evaluate?
I definitely looked at products from Fluke, but there are not many out there that have the level of functionality that the LinkRunner has. It didn't take long to realize there are only two or three choices out there that are in the price range that a community college can buy.
The big factor was the price tag.
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
Want to save time and money? This is the tool. The autotest feature tests servers such as DHCP and DNS. This helps identify why a device is not getting an IP address as well. One time a device wasn't getting an IP. Come to find it the there was no available IP in the subnet range.