G

[G]

Thank you, Haven, I look forward to when the fix becomes available in a new version of NoMachine.

[G]

The other thing that might be the possible source of this problem is the fact that a while ago I had two displays connected to my Mac Mini, one through the HDMI port, and the other through the Thunderbolt port. But at the moment I just run my Mac with one display, connected via the HDMI port.

However, I wonder whether my Mac may have maintained a some kind of configuration file somewhere for these two displays that I used, and it is this configuration file that is confusing NoMachine. If this were the case, then in order to replicate the problem, it might be an idea to connect two displays to your test Mac temporarily, and then revert back to using one display.

The fact that when this problem occurs, NoMachine shows me the option of connecting to two different physical displays, but only one of these physical displays works to create a connection, suggests to me that NoMachine may still think that my Mac has two displays connected to it, and so is presenting the option of connecting to either display.

I managed to reproduce the problem again, and have emailed you the client logs and the server logs.

[G]

Hi haven

Thanks very much for your help with this issue.

At the moment I am have trouble reproducing this problem myself. Having used the command /etc/NX/nxserver –restart a few times, this seemed to clear out the problem, and so far it has not returned. That is to say, the second screen containing these Physical Display icons no longer appears.

However, the problem was intermittent anyway, so it may return in the next few days. When it does, I will send you the server side and client side logs as requested (sorry that I made a mistake earlier of not properly setting the SessionLogLevel to 7; I will make sure I get it right next time).

One thing that occurred to me as the possible source of this problem is the fact that I have a second router running in my home, in order to provide good WiFi coverage across the house. Although both my routers are connected together, via an ethernet cable that runs from a LAN port on the first router to the yellow Internet port on the second router, these routers are not using the same LAN IP address range (the first Netgear DG834GT ADSL model/router has the LAN IP 192.168.0.1, and for attached devices issues LAN IPs in the range 192.168.0.2 to 255; the second Netgear WNDR3400 router has the LAN IP 192.168.1.1, and for attached devices issues LAN IPs in the range 192.168.1.2 to 255; I have not yet figured out how to get both routers to use the same LAN IP range).

Depending on where I am in the house, sometimes my Android tablet will connect to the WiFi of the first router, and sometimes to the WiFi of the second router. Possibly this might be the source of the problem.

Anyway, as soon as the problem occurs again, I will send you the logs.

 

[G]

By the way, when I followed your above instructions and then executed the Terminal command /etc/NX/nxserver –restart, this had the effect of reducing the number of Physical Display icons shown on my Android tablet from two down to one.

(Incidentally I had to prefix that command with the sudo command, in order to provide administrator access necessary to get it to work).

[G]

Hi Bilbotine,
Many thanks for your post.
I followed the instructions you provided above, and have emailed you the server logs.

[Author]

Posts