September 24, 2019 at 08:28 #23724
NoMachine 6.8.1 free version and some earlier versions failed to update the physical display on a Windows 7 Home Premium computer, but only for certain connected computers running CentOS 6.x and Ubuntu 18.x Linux, and NoMachine 6.8.1 (free).
After a great deal of effort, the problem was tracked down to the Radeon HD-667X-ZH graphics card on the Windows machine. While the graphics card is outdated, it is fully functional and works with all other software.
Removing the graphics card and rebooting to use the on-motherboard video adapter solved the problem, so this message is informational only.September 24, 2019 at 17:02 #23745
any chance to get NoMachine logs from the non-working case? To do that, you would have to restore the Radeon card, reproduce the issue and gather logs as explained in https://www.nomachine.com/AR10K00697. You can also send them to email@example.com. If you do that, please also try to uncheck the ‘Use acceleration for display processing’ box in Server preferences -> Performance tab and see if it solves the problem.September 25, 2019 at 07:39 #23747
Sure, I can do that. It will take a day or so. Thanks for your interest!September 26, 2019 at 08:29 #23754
I’ve reinstalled the graphics card and the display problem reappears.
The box “Use acceleration for display processing” in “server preferences” was already unchecked.
Compressed log files attached to this message as log.zip.
The most recent (failed) attempt to contact another computer via NoMachine from this machine was shortly after 12:00 PM PDT, 9/25/2019September 26, 2019 at 08:29 #23755
PS: checking the “Use acceleration” box with the graphics card installed and restarting everything did not seem to change the situation. The problem persists with or without that check.September 26, 2019 at 08:32 #23761
Please send the logs directly to forum[at]nomachine[dot]com making sure you include the title of your topic in the subject. Thanks!September 27, 2019 at 08:10 #23794
I tried to send the logs to firstname.lastname@example.org and the message was returned, with the following errors noted (log.zip comprises 1.38 Mb).
The original message was received at Thu, 26 Sep 2019 11:56:37 -0700
from d131-117.uoregon.edu [18.104.22.168]
—– The following addresses had permanent fatal errors —–
(reason: 550 5.7.0 Message Size Violation)
—– Transcript of session follows —–
… while talking to mxa-000bfd01.gslb.pphosted.com.:
<<< 550 5.7.0 Message Size Violation
554 5.0.0 Service unavailableSeptember 27, 2019 at 09:17 #23806
Hello, can you try sending again? We checked to make sure that everything is working and it is. We’ve also checked our mail server as well for attempted receipts from your IP address and domain. You can also try submitting here if they are small – I wasn’t sure how big they would be, hence I suggested to send them directly.
You must be logged in to reply to this topic.