Generally, you should not have to do this. Ideally, you have control over the network that your cabs are on and can assign static IPs as opposed to using DHCP (this is really nice because it means your cab IP won't shift on reboot and break communication with HM). Even if you don't have control over your network, in most situations, the cabs should self-report their IP address in the settings menu. I have had issues specifically with the new 4k build with this - the cab will be connected to the internet, but won't show an IP address (v4 or v6) in the settings menu. If you are running into this issue, this is when to use this guide.
One thing to mention - I only had one cab that wasn't reporting it's IP address, so I was able to compare the results against the list of known IPs and determine the IP that way. If you have multiple cabs with this issue, I might actually recommend starting with only one cab powered on so you know the IP address you find belongs to the powered cab, then turn on a new cab, repeating the process each time. This will save some annoying guess-and-check work later (figuring out what IP is what cab)
ipconfig and ifconfig in Linux (or Mac). You're looking for the part of the output that gives your computer's IP address - in Windows, it will be IPv4 Address, in Linux/Mac, it will generally be inet addr under eth0 (wired) or wlan0 (wifi)..) and replace it with an *. For example, if your IP was 192.168.1.235, you'd end up with 192.168.1.*.In Windows, it's generally easiest to use Zenmap, a GUI frontend for Nmap that comes bundled with the download.
nmap -p12749If you're using Linux or Mac I'm going to assume you know what you're doing well enough to open up a terminal and run a program from the command line.
nmap -p12749 <IP range from last step>Nmap done