Forum Replies Created
-
Posts
-
Thanks again @britgirl
Not exactly what I was after. The Recent Connections just shows the OS type (eg Windows), not version info (eg, Windows 10 Build #, Windows 7 SP# etc).
Also I discovered that a fresh install has “Don’t delete log files on exit” unticked as default https://www.nomachine.com/DT10O00154#2.5. So if there was any info there, its now gone for my old sessions.
No matter, I’ve ticked the box and will hopefully have the info from now on at the client end.
Thanks @britgirl
That may be the answer for the OP, but I’m interested in learning the server’s OS version (sorry, I called it the remote host since the server is remote from the client’s point of view).
So to reword, does the client keep any OS information about the servers it connects to in logs etc?
I’d also like to know what the operating system version was of the remote hosts, assuming that’s captured somewhere in the client logs?
Hi Zag
Problem solved.
The issue was to do with a corrupt Windows C:\Users\Default profile, not a NoMachine issue.
I thought maybe something was wrong with my own profile being corrupt, so I created a new Administrative account with the intention of installing NoMachine from there. But I had issues logging on to the new account and a new profile could not be created (ie from the Default profile).
Naturally this is the cause of the error “Cannot create the home directory for the nx user”. Since there is no profile there can’t be a home, although in UNIX this would be there can’t be a profile because there is no home directory. 😉 The error message is a little misleading for a Windows world but makes sense in a UNIX world. Not unsolvable though!
I copied a Default folder from a clean install and reapplied inherited permissions to solve the issue with Windows.
Thanks for the offer of help. Reinstalled NoMachine and all working no errors.