Forum / NoMachine for Mac / Discovery doesn’t work for MacBook Pro, does for other MacBook
- This topic has 10 replies, 2 voices, and was last updated 1 hour, 31 minutes ago by Britgirl.
-
AuthorPosts
-
October 7, 2024 at 17:20 #50030timParticipant
I use Ubuntu/Pop_OS! to connect to two macOS computers. Only the MacBook shows up when the local network is searched.
The 2017 MacBook Pro does not. On that computer, under Server settings –> Ports, the NX service is running and “Advertise this computer…” is checked.
I exported the logs and they indicate the service is listening for connections.
What are my next steps to figure out why this computer is not being discovered.
Server: 2017 MacBook Pro Ventura 13.7; NoMachine 8.14.2
Client: Pop_OS! 22.04 LTS; NoMachine 8.14.2
October 8, 2024 at 09:24 #50043BritgirlKeymasterHi, can you enable debug and send us the server-side logs of the affected Macbook, so we can check them? You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243
Attach them here or send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
October 8, 2024 at 14:56 #50052timParticipantCompleted.
October 8, 2024 at 16:52 #50066BritgirlKeymasterHi, logs show that that NoMachine is broadcasting correctly. So, we need to understand why your client is not receiving from the problematic Macbook. Either the Macbook 2017 server is not on the same LAN as the client (they must not be subnets), so verify this. And check that the firewall of the 2017 MacBook Pro is not filtering the traffic. You can do that by temporarily turning it off.
October 8, 2024 at 19:14 #50071timParticipantAll computers are on the same LAN (no subnets) assigned ip addresses by the same router.
Turned firewall off on 2017 MacBook Pro and restarted. No change. I’m pretty sure the working MacBook also has the firewall on, but I’d have to check and confirm later. Either way, the 2017 MacBook Pro still doesn’t show up (I am able to connect by manually configuring).
October 8, 2024 at 22:10 #50073timParticipantI just tried deleting and reinstalling NoMachine on both the Ubuntu box and the 2017 MacBook Pro. Same result.
October 11, 2024 at 17:08 #50154BritgirlKeymasterWe could send you a package for you to install with higher debug enabled for mdns discovery which could allow us to investigate (given that we can’t reproduce it). Are you available to try that?
October 13, 2024 at 17:15 #50184timParticipantSure. Would be happy to help and try that.
October 25, 2024 at 18:33 #50421BritgirlKeymasterHi Tim, check your inbox 🙂
November 20, 2024 at 15:42 #50820timParticipantHi @Britgirl–
I just wanted to confirm y’all got my set of logs from the higher debug version and that they are what you need?
Thanks!
Tim
November 20, 2024 at 18:03 #50828BritgirlKeymasterApologies for not updating you. The logs show that the player didn’t receive anything on the port where it reads the multicast UDP messages (to know the servers available in LAN). And we’ve previously confirmed that NoMachine is broadcasting correctly on the Macbook server. So something is happening in the middle, and in the middle there is the network or a firewall.
Did you already try:
disabling the FW completely on your Ubuntu machine?
checking whether the Macbook Pro (2017) machine can see the Ubuntu host and the other Macbook?
checking whether the other Macbook can see the Ubuntu machine and the Macbook Pro (2017) ? -
AuthorPosts
You must be logged in to reply to this topic. Please login here.