Forum Replies Created
-
Posts
-
I made the requested changes to the node.cfg file and I still note the screen shading issue. It happens when the server screen is asleep and it also happens when the screen is awake so it does not appear related to sleep issues. I am providing a link to a screencast video so you can see the issue happening for yourself. I will email the logs without the /users folder as the number of files in that folder is so large my email server rejects the mail. Let me know if this is an issue or if you want it anyway and I will send it with a different mail service. https://app.screencast.com/EUnOprNy76vZp
No it does not help by implementing the suggested settings on either the server or the client. I’m also having issues I’ve never had before with the server being unresponsive to the keystrokes from the client, i.e., I cannot enter in my MacOS password on the remote server lock screen; characters will not appear in the password entry field when keys are depressed. Restarts and close and reopens do not remedy this issue. Very frustrating after just having gotten version 8 finally working.
I’ve also added a link to screencast where I’ve placed a brief 17 second video that shows what is happening on my client side connection on the MBP as well as a snip of the security settings on the MacMini M1 server.
See video here:
Attachments:
Got it now, thanks! Installed and an interesting result. When it connects for the first time the results are exactly the same as before:
the client connects to the server and the server wakes up, but the client is in black screen. Moving the finger around on the black screen of the iPhone correspondingly moves around the arrow cursor on the MacBook, but this is not visible on the black screen of the client.
Now however, after having installed your update, if I then disconnect from the server, and I reconnect once again, I am able to connect and see the server on my iOS client, apparently because the server has now been awaken (though it was in the previous instance as well so I’m not able to understand why dropping out and going back in works now.)
This behavior is different than with my MacMini M1 where the computer wakes and connection is possible right from the very first attempt. So this is usable now, but wanted to throw these findings out to you for what it’s worth.
Thanks!
Brian
What in box are we referring to ? Nothing received in my email and if it is here on the website I’m not sure if I know where that is? Sorry!
Ah thanks for that link on how to collect all of the log files. Again, what I am seeing, on an iOS iPhone 12 Pro Max client (running ver. 8.7.1) and an Intel MacBook Pro (running ver. 8.16.1) is that for both LAN and outside External WAN IP address connection attempts, the client connects to the server and the server wakes up, but the client is in black screen. Moving the finger around on the black screen of the iPhone correspondingly moves around the arrow cursor on the MacBook, but this is not visible on the black screen of the client. If the MacBook is already awake, the client will connect and the screen of the MacBook is visible as normal on the iPhone client with no black screen.
The ZIP file is too big to attach so I will email it to you…(I did reset and clear the logs before I started debug mode to catch the errors for demonstration).
Thanks!
Brian
And an additional note relating to an earlier post: attempting to work around this bug by downloading an earlier version of NM did not help at all. I downloaded and reinstalled the previous build (8.13.1 – 7/29/2024) to see if it would solve the problem and it did not. More than anything else I’m just curious what caused this to all of a sudden break. If it’s not a NM-internal proprietary secret my curiousity is killing me to know!
This works! Please note a reboot of the computer hosting the server is required though!
Thanks!!
Brian
Yeah, kind of have to go in with Britgirl on this one: with all due respect to the frustrations of daclint01; the objective is to get this thing fixed so we can be on the most current release and that it just works! We will get there, even if it takes sending a dozen logs. I realize that we are the debugging universe, compensated via a free product that is essentially fully functional, which of course assists to perfect the commercial product as well. I don’t mind being the testing ground given the supreme responsiveness of the NM support team.
Brian
When connecting from another desktop (actually a MacBook Pro running the same software version of MacOS Sequoia as the MacMini, I get the following results (screenshots attached:)
1 – Two connections on NM player for this same MacMini: one for the LAN connection and the other using the external IP for on the road.
2 – Connecting with LAN connection yields a white screen
3 – Connecting with external IP address connection produces white screen (shot #4) and then shows a “Connection Reset By Peer” error (shot #3) which alternates on and off every ten seconds or so on top of the white screen.
This is with the mod to the node.cfg file edited in as requested above.
PS when I get home I will attempt to connect to the Mac mini from another desktop for you after having made the edit to the cfg file and will report my findings …
No luck with this. I unlocked the app and edited the cfg file as directed and restarted the server at the command line but the results are unchanged. The client reports and error 5: input/output error- “could not start the display server” after disconnecting from the black screen…I will go back into node.cfg and edit the added line back out I guess? What’s next (?)
