Forum / NoMachine for Windows / NoMachine scanning range
Tagged: auto-detection, network segmenting, subnet
- This topic has 3 replies, 3 voices, and was last updated 5 days, 18 hours ago by Britgirl.
-
AuthorPosts
-
November 25, 2024 at 16:19 #508704verageParticipant
I have a home network running on two segments (192.168.0.1 and 192.168.1.0). NoMachine is only auto-acquiring devices that are connected to the same network segment (192.168.1.0). I have static routes setup to support and interconnect the 192.168.0.1 network and can MANUALLY connect to the devices if I input the connection information. However, these are DHCP devices and it can become quite tedious.
How can I get NoMachine to scan/auto-detect devices on the other network segment? How does it perform the scan? Is it limited by scanning devices including the first three octets of the IP it is on, or is it just a listener and the servers are broadcasting? Do I need to open something up on the 192.168.0.1 network to allow this broadcast if so?
If anyone has an idea or has a simliar setup working, please let me know! This would make my quality of life so much better. lol
November 26, 2024 at 18:37 #50889fishermanModeratorNoMachine cannot autodetect devices on the other network segment, but there is a workaround that you can implement on the router.
To implement a workaround for this issue, the user must have network administrator privileges. They need to configure an mDNS forwarder, repeater, or proxy on the router, provided the router supports this feature.
This is necessary due to a fundamental limitation of the multicast protocol: each subnet uses the same multicast DNS address (224.0.0.251), which is not shared across subnets. For example:
- Subnet 192.168.1.0/24 uses the local mDNS address: 224.0.0.251
- Subnet 192.168.0.0/24 also uses the local mDNS address: 224.0.0.251
Without mDNS forwarding or proxying, devices in one subnet cannot discover or communicate with devices in another subnet via multicast.
November 28, 2024 at 04:49 #508994verageParticipantThanks, fisherman. I am not seeing any sort of mDNS configuration in my router (Linksys EA6300). I do have Static Route configuration. Not sure if that will get me where I need to be.
For now, I just threw out the subnet and changed it over to a bridge connection for now so we are all on the same subnet. Very uncomfortable with this practice! 😀
May need to look into some sort of cloud-based offering where the devices register so I can tackle them regardless of their network connection.
December 2, 2024 at 09:50 #50922BritgirlKeymasterHi 4venger, you might be interested in the upcoming NoMachine Network feature in NoMachine 9, coming soon, which will let you see (and connect to) all your computers regardless of the network they are on. By adding them to NoMachine Network, which will be free to do, they will each be allocated a univocal Machine Id. Then all you’ll need to do is log in to the Network service on any device and add your computers to the Machines panel using their Machine Ids (just like you add a NoMachine connection today). There’s a brief introduction about what users can expect (give or take a few small changes): https://www.nomachine.com/network. Connecting to those computers using the Network service will require a Network Subscription, monthly or yearly, and you can continue to use the free version 🙂
-
AuthorPosts
You must be logged in to reply to this topic. Please login here.