Forum / NoMachine for Windows / DaemonGreeter error 6 ‘No such device or address’
- This topic has 2 replies, 2 voices, and was last updated 8 years, 8 months ago by
Thinker55.
-
AuthorPosts
-
June 29, 2016 at 15:18 #11732
Thinker55
ParticipantI have one Windows 10 Enterprise box that the client works on, but the server will not accept connections. Windows clients get error 138, Linux clients get error 110. What I see in the nxerror.log is:
DaemonGreeter/DaemonGreeter: WARNING! Read from FD#xxx failed.
DaemonGreeter/DaemonGreeter: WARNING! Error 6, ‘No such device or address’.
The nxserver.log reports:
NXSERVER WARNING! Cannot write to FD#xxx.
NXSERVER WARNING! Error is 106, Software caused connection abort’.
nxdevice log reports:
[1256][16048] 12:50:27 010 ERROR: Cannot remove preinstalled driver package.
Winapi code is : 2.
[3796][13388] 14:52:25 529 ERROR: Unexpected service state [4] reached.The nxd.log reports nothing unusual. It says it is opening an closing connections:
Info: Server started with pid 3620 on Tue Jun 28 13:49:24 2016.
Info: Listening for connections on any interface on port 4000.
Info: Accepting connections from any host with encryption enabled.
Info: Connection from 192.168.1.8 port 65353 accepted on Tue Jun 28 13:50:45 2016.
Info: Connection from 192.168.1.8 port 65353 process 13300 started on Tue Jun 28 13:50:45 2016.
Info: Connection from 192.168.1.8 port 65353 process 13300 closed on Tue Jun 28 13:52:46 2016.
Info: Connection from 192.168.1.8 port 65382 accepted on Tue Jun 28 13:52:55 2016.
Info: Connection from 192.168.1.8 port 65382 process 11192 started on Tue Jun 28 13:52:55 2016.
Info: Connection from 192.168.1.8 port 65382 process 11192 closed on Tue Jun 28 13:54:56 2016.
Info: Connection from 192.168.1.170 port 34072 accepted on Tue Jun 28 14:24:46 2016.
Info: Connection from 192.168.1.170 port 34072 process 7920 started on Tue Jun 28 14:24:46 2016.
Info: Connection from 192.168.1.170 port 34072 process 7920 closed on Tue Jun 28 14:26:47 2016.I detected nothing unusual in the install logs.
This in NoMachine 5.1.26 Free version. Tests on other Windows 10 machines are fine. Tests on SuSE LEAP servers are fine.
I have tried changing ports — no effect.
This is all physical displays.
Suggestions? I want to move to this software, but I need for it to work on this machine.
June 30, 2016 at 09:57 #11740barpa
ParticipantHi Thinker55,
To understand better we will need more logs from the server side. Reproduce
the problem and send to forum[at]nomachine[dot]com. Instructions about collecting logs you can find here:
https://www.nomachine.com/DT07M00098.July 4, 2016 at 08:46 #11754Thinker55
ParticipantI resolved this. It appears to have been a conflict with the NVIDIA display driver on my system.
-
AuthorPosts
This topic was marked as solved, you can't post.