DragonFly connected in the network alongside the Platypus and SOLO

The problem

Windows 10 security improvements have added friction to local network discovery. Devices like the DragonFly, Platypus, and SOLO — which use hostname-based discovery — can intermittently become unreachable after Windows updates or network changes, requiring a reconnection step that should not be necessary.

Trick 1: Static IP and hosts file entry

The most reliable approach is to assign your device a static IP address and then add an entry in the Windows hosts file so the hostname always resolves to that address.

  1. Assign a static IP address to your device (DragonFly, Platypus, or SOLO) through the device's own configuration page or your router's DHCP reservation settings.
  2. Open C:\Windows\System32\drivers\etc\hosts as Administrator in a text editor.
  3. Add a line like: 192.168.1.123 aagsolo (or whichever IP and hostname your device uses).
  4. Save the file. Windows will now always resolve that hostname to the static IP, bypassing network discovery entirely.

Trick 2: Direct UNC path access

If you need to browse the device's shared files directly from Windows Explorer or a command prompt, use UNC path syntax:

  • Open a Run dialog (Win+R) or command prompt and type: start \\aagsolo
  • Or use the IP address directly: start \\192.168.1.123

This opens the device's shared folder in Windows Explorer without relying on the network browser discovery.

Both tricks work for any of the Lunatico network devices — DragonFly, Platypus, and SOLO. For the SOLO in particular, the hosts file approach also ensures that the ASCOM driver can always reach the device at the expected address.