MacOS Sequoia issues

Forum / NoMachine for Mac / MacOS Sequoia issues

Tagged: , , ,

Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • #48465
    Jhawk27
    Participant

    None of my local network computers are displaying after the upgrade. Anyone have luck yet?

    #48474
    Jhawk27
    Participant

    Seems to be local issue with the new Sequoia update. Attempted to run NM on parallels and it failed miserably. I have a hunch that Apple changed the workings of how apps request access and something isn’t meshing with NM anymore. Hope a fix comes soon! Still love the product!

    #48475
    Britgirl
    Keymaster

    Hi, macOS Sequoia is available as a Preview only (and just out less than 24 hours ago), so there could be some further updates still from the Apple developers before they release the final stable version. Thanks for reporting, we will be testing ourselves as well in the meantime. Can you provide more details about how NoMachine failed with Parallels?

    #48517
    jm76430
    Participant

    Hi, I’m encountering the same issue.  If there’s anything I can do to help you folks investigate, I’m happy to help.

    #48630
    kenthompson1
    Participant

    I can confirm that the MacOs V15 beta (Sequoia) breaks compatibility with the player, at least. No remote locations appear on the network, although I have other computers on the network running linux/mac sonoma that see the Sequoia computer just fine.  When I attempt to manually create a connection from the Sequoia to a local network location, I get an error about a route not being found.  SSH option yields the same message.  However, the target machine is 100% accessible.

    #48635
    Britgirl
    Keymaster

    Dear macOS Users,

    Sequoia must be out of beta status before we can consider adding it to our list of supported platforms (and of course, first we have to conduct rigorous testing). At the moment we are aware of some issues with permissions. It is possible that incompatibilities with this beta will be fixed when Apple officially releases it for production. Please bear in mind that NoMachine cannot officially support pre-release (beta) versions of operating systems. Such pre-releases are made by those operating systems for trial and testing purposes only. We do of course accept bug reports from users who are testing with these pre-release versions as we strive to make sure we are compatible at the time of the general release of supported operating systems. We cannot guarantee any compatibility with these pre-release versions as much of the software changes dramatically during the pre-release cycle.

    See here for our policies about beta versions: https://www.nomachine.com/AR03E00450

    #48636
    Jhawk27
    Participant

    Thanks for the info. That’s pretty standard with betas. I believe the community, whom likes using the product, was attempting to voice the same confirmation of the issue. The intent of this post was to make the issue aware to the NM team so we could maybe(?) get a fix, sooner or later. Or who knows, maybe it was user error. Glad to know it is not a single issue or user error that can be corrected. I look forward to updates of all kinds, from both sides.

    #48638
    Britgirl
    Keymaster

    Any issues in the production-ready Sequoia will become Trouble Reports, which we’ll publish, and they will of course be fixed  🙂

    #48768
    n6ac
    Participant

    Add me to the list of those having an issue in Sequoia.

    I am able to connect with 3 Macs on the Lan, and 2 Raspberry Pis via WAN, but cannot seem to get local Pi on LAN – try to ADD, but never asks for password and says that LAN IP not available …

    But I discovered a useable workaround! In ~/Documents/NoMachine/ I found a file named PiName.nxs – double-clicking that brings up the LAN Pi screen! Left over there from the former Sonoma volume that was copied as a volume for Sequoia.

    However it does not add the Pi LAN connection onto the Main Window of the NoMachine program ….

Viewing 9 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic.