QM.DOT NET Interesting Problem WIN 10 and the fix.

[mixedgas]

So your QM.net is not showing up on the network when you bought it used and your Running Win 10 after a certain update. Win 10 is trying to prevent you from running without DNS and Gateway. This is because having 192.1.1.1 lets you reprogram some switches, hubs, servers, etc. Windows is being picky and Stupid with the thinking that this will prevent hacks.

FOR LEGACY SYSTEMS ONLY, NOT BEYOND!

This is for older systems, LD2000 with QM.NET, NOT BEYOND. I'm running LD2000 and Live Pro on a Dedicated Box that doesn't have to surf the net. This is for direct to computer connections, no hub, switch, etc. in use. I have the ability to restore the Intel Nuc CPU completely and quickly if I do something wrong.

Situation:

Your LD2000 is not seeing the QM DOT NET BOX, and this is a last resort. Call Pangolin support before anything else. You have Yellow, Green, and Red Leds at this time, but it won't connect:

I didn't want to wake Aaron @ Pango at 3 AM, so this was the alternative Emergency fix with some help from GPT And Grok. I'm assuming you do your own IT and you're not using a corporate system. I have a dedicated computer for each of my Pango systems, and like many pros, I strip all unexpected internet access and web surfing out of the system. I use other systems for surfing the net and downloads in the field. This Eliminates unexpected updates and other Windows Suprises completely. Note for newer readers, LD2000 uses the interface hardware card as the key, it does not need to log into the Pangolin system to authenticate. This is why this procedure is LEGACY hardware/Software only, and NOT for Beyond or Quickshow.

1. Unplug your computer from outside internet to protect it. Disconnect Ethernet cable, Turn off WIFI at a low enough level in the system that it is not coming back on if you reboot.
2. Turn off all Windows Defender Firewalls. Which is why you do not want an outside internet connection.
3. Go to device manager and settings and turn on IPV4 and Program in 192.168.1.1 from the QM Manual with a subnet mask of 255.255.255.0, no Gateway. Turn off IPV6
4. Plug in the Dot Net direct to the PC.
5. This is a laser show only machine, has no other uses, so lets rock. If you do your schoolwork or business ventures on this machine, do NOT do the following. For the record I know diddly about Windows Networking, so this was guidance from AI and a lot of Google Searching. I was desperate to get a used unit up, late at night, and I know the risks.

In my case my used Dot Net was set to 196.128.1.24 at factory, you'll need to know what your address should be, and that should be written on the case.


5. Open command line with admin privileges (Windows Key and X, select CMD with Admin) and type:

netsh interface ipv4 show interfaces


Find your Ethernet interface name in the list provided, (example: "Ethernet")

6. In the command line, using the Interface Name you just found:

netsh interface ipv4 set address name="Ethernet" static 192.168.1.1 255.255.255.0

7. Clean up any gateway:

netsh interface ipv4 set dns name="Ethernet" static none

8. You may get a message: “This adapter has no default gateway and cannot access the internet”, perfectly normal. Let's crush that with an Admin level command, remember to reboot.

reg add HKLM\SYSTEM\CurrentControlSet\Services\NlaSvc\Para meters\Internet /v EnableActiveProbing /t REG_DWORD /d 0 /f

9. Let us verify, open the cmd and type:



ipconfig


You should see:



IPv4 Address . . . . . : 192.168.1.1
Subnet Mask . . . . . : 255.255.255.0
Default Gateway . . . : (blank)

10. Lets verify , the Ping is expected to fail, but it arms the Ethernet for the ARP command.

ping 192.168.1.255
arp -a


At this point Pangolin's software found my unit, and life was bliss.

I need to back and fix what I turned off, including the Firewalls.




This is the rest of my conversation with GPT:

Pangolin QM.net – “Host Unreachable” Troubleshooting


1️⃣ Confirm physical Ethernet link (QM.net is picky)


QM.net does NOT auto-MDIX reliably.

Do this first

• 
  Use a straight-through Ethernet cable
• 
  OR insert a small unmanaged switch between PC and QM.net

👉 This alone fixes ~50% of “unreachable” cases.

Check LEDs


On the QM.net RJ45:

• 
  Link LED ON = PHY is alive
• 
  Activity LED blinking = packets moving

❌ No link LED = cable, MDIX, or dead port

---

2️⃣ QM.net default network behavior (important)


QM.net units typically ship with:

• 
  Static IP
• 
  NO DHCP
• 
  Common defaults:
  
  • 
    192.168.1.24
  • 
    255.255.255.0
  • 
    Gateway: none
  
  
  

If the unit was ever used on a different subnet, it will stay there.

---

3️⃣ Use Pangolin’s own discovery tool (do NOT rely on ping)


Open:


Pangolin → QuickShow → Settings → Network → Network Scan

(or QM.net Network Configuration Utility, depending on version)

This uses broadcast discovery, not ICMP.

✔ If it appears → you have L2 connectivity

❌ If not → proceed below

---

4️⃣ Force-discover via ARP + Wireshark (this always works)


Start Wireshark

• 
  Interface: Ethernet
• 
  Filter:

arp


Power-cycle the QM.net

Watch for:

• Gratuitous ARP
• ARP “who-has” packets

You are looking for something like:



Sender IP: 192.168.x.y
Sender MAC: Pangolin / QM.net


💡 That tells you the actual IP, regardless of what you think it is.

---

5️⃣ If you see ARP but ping still fails → this is NORMAL

QM.net often:

• ❌ Ignores ICMP (ping)
• ✅ Responds only to Pangolin software

So:



ping 192.168.1.24


can fail even when the device is working
This is expected behavior.

---

6️⃣ If NO ARP appears at all (critical)

That means one of these is true:
A) Wrong subnet

Temporarily set PC to:



IP: 192.168.0.10
Mask: 255.255.0.0


This lets you see anything in 192.168.x.x
Then re-run Wireshark + power-cycle.

---

B) QM.net is in fallback / corrupt config state

Some QM.net units fall back to link-local:
Set PC temporarily to:



IP: 169.254.1.10
Mask: 255.255.0.0


Then:

• Network scan in Pangolin
• Wireshark ARP watch

---

7️⃣ Known Pangolin-specific gotchas (very common)

Issue	Symptom
Used unit from another show	Static IP unknown
Auto-MDIX fail	No link lights
Windows firewall	Discovery blocked
Wi-Fi still enabled	Wrong interface used
Multiple NICs	Scan misses QM.net

Strong recommendation

Temporarily:

• Disable Wi-Fi
• Disable all other Ethernet adapters
• Leave only the QM.net NIC active

---

8️⃣ Windows Firewall (yes, it matters here)

Temporarily disable:



Windows Defender Firewall → Turn off (Private network)


QM.net discovery uses broadcast UDP, which Windows sometimes blocks.

---

9️⃣ Last-resort but guaranteed recovery

If still invisible:

• Connect QM.net to a router with DHCP
• Check router’s DHCP client table
• Note assigned IP
• Reconfigure QM.net back to static

This is Pangolin’s own recommended recovery method.


AGAIN< LAST RESORT PROCEDURE ON A STAND ALONE SHOW CONTROLLER PC.

Steve