cytan299

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 17 total)
  • Author
    Posts
  • cytan299
    Participant

    Hi Britgirl,

    I’ve upgraded to Sequoia 15.1 and have re-enabled the Firewall. I’ve been running noMachine client for the past 24 hours and I haven’t seen any “bad message” errors. So I think this problem is resolved.

    Thanks!

    cytan

    cytan299
    Participant

    Unfortunately, nxplayer, nxd and nxdock were already added to the firewall options list to “Allow incoming connections”. I’m waiting for the next Seuquoia update which hopefully will fix the firewall problem.

     

    cytan

    cytan299
    Participant

    Hi Britgirl,

    I’ve sent you my logs via email. I’m not sure how useful the crash log is without the Mac client nomachine log. I don’t have this log because I had turned off logging.

       In the mean time, after turning off the Sequoia firewall, I have not experienced any nomachine crashes or “Bad Message” errors. Everything has been running solidly so far. My guess is that the Sequoia firewall is broken because people have been posting that with the firewall turned on they’ve been experiencing problems. Once they turned it off (like me), their apps worked properly.

    cytan

    cytan299
    Participant

    Another update: I turned off the firewall which is a known problem in Sequoia. And miraculously, there hasn’t been any “Bad Message” errors so far and NoMachine has not crashed since (nxplayer crashed another time since I posted the crash log, but that was *before* I turned off the firewall). This “Bad Message” error may be related to the firewall because my other app, [removed], had been complaining about AES errors periodically as well. But those AES errors went away with the firewall turned off.

    All I can say is that Sequoia has problems …

    cytan

    cytan299
    Participant

    I ran NoMachine overnight and nxplayer crashed when it shouldn’t have been doing anything because I was asleep :).

    Attached is the crash log, which may be related to “bad message” (or not). Anyway, I hope it’s useful for you, Britgirl.

    Thanks!

    cytan

    P.S. Posting again, because I wasn’t allowed to post a log file ?

    Attachments:
    cytan299
    Participant

    Well, the “bad message” error has popped up twice over a 24 hour period. But reconnection was nearly immediate. Unlike Sequoia 15.0 where the “bad message” pops up nearly immediately and repeats itself every few minutes, on Sequoia 15.0.1, it repeats after a few hours.

    I’m still game on trying the debug version to see if this problem can be resolved.

    cytan

    cytan299
    Participant

    Well, I’ve been running for 2.5 hours with NoMachine 8.14.2 and Sequoia 15.0.1, and the “Bad Message” no longer pops up. This may be fixed because previously the “Bad Message” error pops up within less than 1 minute of NoMachine use.

    I’ll post again if the problem comes back.

    cytan

    cytan299
    Participant

    Thanks, I’ll test when I get the link.

    P.S. I just got an update message from Apple to upgrade from 15.0 to 15.0.1 for my Intel Mac but not my M3 Mac yet. I’ll see if this fixes the “Bad Message” problem plus other bugs in Sequoia.

     

    cytan

    cytan299
    Participant

    Sure. Please send me the link and I’ll download, install and test. Same instructions from https://kb.nomachine.com/DT07S00243 ?

     

    cytan

    cytan299
    Participant

    I sent it again, this time to the correct email address, I hope 🤞
    Please confirm.

    cytan

    cytan299
    Participant

    Hi Britgirl,

    I’ve just sent email to you with the log files. The PC I’m connecting to is running

    MS Win11 Pro version 10.0.22631 build 2231

    and NoMachine 8.14.2.

    cytan

    in reply to: Audio only when remote miniPC audio enabled #38253
    cytan299
    Participant

    Hi kubasym1,

    Thanks for trying to fix the problem and confirming that it was a driver problem like I had suspected.

    As for updating drivers, that was my first thought as well. I have the latest Intel driver for the audio chip, so that isn’t a solution.

    The workaround with an audio plug inserted into the audio port is acceptable for me.

    Thanks again.

    cytan

    P.S. If you do find a solution, or some other way to stream audio with the audio muted at the server, please post in this thread so I can test it out. Thanks.

    in reply to: Audio only when remote miniPC audio enabled #38233
    cytan299
    Participant

    Hi kubaszym1,

    Yes, I’ve already done this. I’ve plugged in an audio plug to mute the sound at the miniPC (pink plug in the photo) and then unmuting the sound on the miniPC. This means that I can stream the audio from the miniPC to my MacBook Pro without audio spilling out from the miniPC.

    I’m eagerly waiting for your fix.

     

    cytan

    in reply to: Audio only when remote miniPC audio enabled #38067
    cytan299
    Participant

    Hi kubaszym,

    I tried your suggestion this morning and unfortunately, streaming sound to my MacBook Pro doesn’t work at all with the selection of the NoMachine Microphone adapter. Please see attached screen shot.

    When you do your fix, please note that my laptop with the RealTek sound chipset streams fine to my MacBook Pro with the audio muted on the laptop.

     

    cytan

    Attachments:
    in reply to: Audio only when remote miniPC audio enabled #38055
    cytan299
    Participant

    Hi Britgirl,

    Just another data point to consider: I have another PC that has RealTek sound hardware and that works with the audio muted at the PC end.

    My miniPC has an Intel SmartSound hardware, so perhaps that’s the problem.

     

    cytan

Viewing 15 posts - 1 through 15 (of 17 total)