Forum Replies Created
-
AuthorPosts
-
bsammon
Participantemail has been sent.
The output of step 1 is in “netuser.out”
The output of step 2 is in “wmic.out”
The output of step 4 is in “Get-WinEvent.out”
My concern about the suspicious whitespace in step 3 turned out to be unnecessary/irrelevant, since the first version of the secedit command invocation worked.
bsammon
ParticipantI also have an additional question, how much time passed before the last Windows restart and the NoMachine service issues?
Roughly, I’d say less than 3 weeks.
If you think more precise answer would be useful, I’ll need to figure out how to get that information. Do you know offhand where such information is found?
bsammon
Participantsecedit /export /areas USER_RIGHTS /cfg C:\Temp\ privileges.txt
I’m not familiar with this secedit command, but it looks suspiciously like there’s a mistaken space between “C:\Temp\” and “privileges.txt”.
I’ll be trying this soon, so I’ll try doing exactly what your message says first, and hopefully that’ll work.
bsammon
ParticipantThe problem has reoccurred.
As I write this message, the computer is inaccessable via NoMachine. It is on the network, and HTTP and SMB and ICMP traffic seems to be working fine.
I have made a snapshot of the logfiles while the computer is inaccessible. The logging level is currently at “7 – Verbose” (and has been for a few days), so the log file is rather large, but the entire log directory tree zips up to a manageable 4MB.
The error message I receive from the client app is “A connection timeout has occurred while trying to connect to <machine> on port <port>” followed by some boilerplate troubleshooting advice.
bsammon
ParticipantEmail sent.
My sense of the exact timetable of events is a little fuzzy, unfortunately.
If/when this problem recurs, I hope to gather more detailed and precise information.
-
AuthorPosts