Need to make a device discoverable on a network other than the one it gets its IP address from.

CTSLA used Ask the Experts™
Our Airtame wireless HDMI application searches for available Airtame devices on the network and shows them on the opening screen. We have multiple HDMI devices in the same building but on a different network. These devices can be accessed from the default network by typing in the IP address in the Airtame app. My question is: - Is there a way to use DNS or some other method to make these devices automatically discoverable as if they were on the same network?
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
nociSoftware Engineer
Distinguished Expert 2018

Your problem is the same as with DHCP. Broadcasts are limited to the broadcast domain.
You will need some kind or "forwarder" / "helper"  that can listen for some protocol and pass those request on to other networks etc.
(There is no generic  solution for this, reasonably hard to do well, and one does need to know the in / outs of the discovery  protocol).

Another option:    use DNS to provide a name schema for devices....
Use a two level schema:    
actual_device_name IN A ipaddress.of.some.device
location_id IN CNAME actual_device_name.

Location ID is room number, or some other identification visible on the equipment. (and can be multiple different name schemas at the same time).
The actual_device_name can be the  something that is a sticker on the device and tied to the equipment (even if equipment is carried around the premises).
The actual device name can be base on the MAC address if you like.

If devices get their address using DHCP then using DHCP reservations can make your equipment semi-static.
with stable IP address that can be reached through DNS.
VP Technology / Senior Consultant
  1. Airtame appears to support mDNS and/or SSDP/UPnP for device discovery.
  2. You need multicast enabled and allowed between each of these networks (or vlans) on any intermediate firewalls, routers, and switches.
  3. Multicast ports 1900-1901 need to be open between these networks.
  4. On Windows, you may need to disable the SSDP Discovery service, and modify Windows Firewall to permit SSDP traffic.
  5. SSDP traffic is sent to, which cannot be NATted - so if you NAT between the two networks, SSDP won't work.
Airtame publishes pretty extensive configuration and troubleshooting documentation on their web site:

Article also provides some specific configuration guidance for various specific devices and operating systems.

There are so many variables, and this is so device-specific, that if I were you, I'd be working with Airtame tech support - since they may be able to provide specific configuration guidance for your network devices.

If you need more help here, suggest you post speciifics:

Your current Airtame configuration, intermediate network configuration, including device type/make/model, and network device configuration (router/firewall, plus switch configuration if they do any L3 stuff).


noci, your suggestions were very helpful, and I was ready to implement them until Gary Patterson pointed out that Airtame has documents and specific instructions for doing this. I had already spoken with tech support without finding a solution, but in actuality the question I asked of them was a bit different so I can't fault them.

Gary Patterson - thank you for the excellent documents you pointed out. We will be implementing these some time next week and I'll post back how it works out.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial