Sequoia (INTEL Mac): NoMachine 8.14.2 gives “bad message”

[cytan299]

Hi,

I just downloaded and installed NoMachine 8.14.2 on my INTEL Mac and after I connected to a Win PC, after a few seconds of connection, it gets disconnected with a “Bad Message” popup error. The screenshot of the bad message is attached.

Backdating to 8.13.1 fixed this problem and the connection is solid. Note: that this may be a problem only on INTEL Macs (INTEL MacBook Pro 16 2019 i9) because when I ran the latest 8.14.2 on my M3 MacBook Pro and connected to the same Win PC, no “Bad Message” error ever occurred.

As a side note: My Intel Mac on 8.13.1 could *see* my Win PC and did not need any workarounds for connecting to it. It just couldn’t see the Macs on my local network. However, if I start nxplayer (8.13.1) from a Mac terminal as per instructions from the workaround, 8.13.1 also gave the same “Bad message” error when it disconnects from the same Win PC.

cytan

Attachments:

1. 

   bad_message-scaled.jpg
   

[Britgirl]

Hi, can you submit the following:

i) Windows version on the PC
ii) logs from the client and server sides as well. Enable debug, reproduce then gather the logs and submit. You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243. There are 4 steps to follow.

Submit here or send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!

[cytan299]

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

[Britgirl]

Hi, I don’t see an email from you. Maybe the email is being caught up in our filters? If they are big attachments, they might even be prevented from getting through. Can you try again? Or alternatively, we can download them whichever external service you prefer. Send us the link privately.

[cytan299]

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

cytan

[Britgirl]

received now 🙂

[Britgirl]

We are not able to reproduce this error. Can we send you debug packages? This would be the current version with additional debug enabled in the logs.

[cytan299]

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

 

cytan

[Britgirl]

Ok , thanks for letting us know. We need a couple of days to prepare it. I will send you a private link when the packages are ready.

[cytan299]

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]

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]

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]

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:

1. crash_log.zip

[cytan299]

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

[Britgirl]

We won’t send a debug package for the moment, at least not for the bad message issue.  However we would be interested in seeing that other crash report you mentioned. And the NoMachine logs from the Mac, zip up the entire .nx directory in the user’s home.

[Author]

Posts