Forum Replies Created
Apparently no news posted here. Is it being looked into, solved. Or it simply does not with such GPU type?
Responded by email, with a fresh set of logs, hope this time everything there. It does not seem to be a codec matter, nor a connection issue, but then I am no expert 😉
By Forums Admin: Updated info from user submitted via email with logs, useful for the topic:
With VP8 forced on the server the client does not discover the server, unless a Micrsoft RDC session is established first and the NX browser window on the server is open. Even with RDC established but NX browser window on the server closed the client keeps on reporting back “No Computers were found in your local network”. Leaving the NX browser window open and killing the RDC the client then discovers the server. Very weird but that is how it happened repeatedly and it is different than not forcing VP8.
Just for your understanding, the fist connection between client and server is through VPN initiated by the client. Then I would attempt from the client NX, or as it does not work RDC, latter also through the LAN (VPN) and not externally through the WAN. Commonly I would kill RDC prior attempting NX, to avoid interference/redundancy.
I trust I mentioned earlier that a connection from the server to the client is working.
I have scrambled the logs again, both sides attached and hope it does suffice now, from the locations:
- C:\ProgramData\NoMachine\var\log\ (aka %PROGRAMDATA%/NoMachine/var/log)
, else would not know where to find what you are looking for.
The connection over VP8 has the same outcome – a black/blank screen. The client is going through with the credential handshake, then showing 2 option screens and then going blank.
Some additional info, just in case:
Listening on TCP port 1972
nettest -client 192.168.0.3
Error in vglutil::Socket::connect–
No connection could be made because the target machine actively refused it.
Thin Client Benchmark
Click the mouse in the window that you wish to monitor …
Monitoring window 0x0003020e (NoMachine Forums – Blank on headless Tesla GPU – Mozilla Firefox)
Sample block location: 944, 508
Samples: 3001 Frames: 19 Time: 30.010020 s Frames/sec: 0.633122
wglspheres (screenshot attached)
Polygons in scene: 62464 (61 spheres * 1024 polys/spheres)
Client area of window: 1240 x 900 pixels
Pixel Format of window: 3
OpenGL Renderer: GDI Generic
22.709968 frames/sec – 25.344324 Mpixels/sec
NVIDIA SMI tool (attached)
relevant (I hope) just sent by email
(x86) is apparently the path of the NX installation in WIN but apparently Cygwin (compiling in Win) has some issue with parsing the (). Anyways, I purchased NoMachine AVC Pack meantime.
I did send the logs already.
Your understanding is correct.
Tried with uncheck ‘Use acceleration for display processing’ but it does not make a difference. As mentioned in the other post VirtualGL is communicating fine with the GPU as well as the nvidia-smi tool.
Logs were already sent to that email, but I did not receive a (auto) response of whether actually been received.
Apparently no support for NoMachine AVC Pack, except then Pay-Per-Incident$ 124.50 (€ 105.60)…
Whilst the NVIDIA smi tool can query the K80 NX does not seem to be communicating with it. Is there any way to check on the communication of NX with the GPU or VirtualGL. VirtualGL is apparently also able to communicate with GPU, as shown by their test tools
Given up on this whole compiling thing and purchased the NoMachine AVC Pack Subscription then
Thinking that it might be the lack of the x264 codec I purchased NoMachine AVC Pack Subscription v6, installed it, placed the license files in C:\ProgramData\NoMachine\codec\etc and restarted the NX server. But no avail, the remote screen remains blank.
What else then, or NX not suited for this scenario?
No ASCII characters
Thanks for the feedback. Machine been restarted and everything. Enclosed a screenshot of the settings for icons to show in the tray, NX is not not amongst those.
Will be collecting/sending the logs