I tried something new yesterday when problem happened again. This is what I did:
-- With Epoptes tool I shut down all of the computers that were showing in the 'detected clients' window.
-- Computer "9A" wouldn't shut down, remaining in the detected clients window.
-- I went over to the client to check it out and saw that the small green power light on the computer was on, however, even though the display should therefore have been on, it was dark.
-- I checked the logs for previous few days and nothing unusual about that client, just 3 very ordinary entries.
-- I had tail command on the epoptes log as I powered down the client (client is 192.168.67.175)...
... as the client disappeared from the detected clients window.
This is the first time I've seen anything out of the ordinary in the epoptes logs. Not sure if this is relevant. Anywhere else I should check? I do have other epoptes log results from a week ago but as I mentioned, it doesn't look like there's anything out of the ordinary. It probably won't happen again as school's almost over for the year. Let me know any other place to check, I've got times to check in other logs. Thanks!
I tried something new yesterday when problem happened again. This is what I did:
-- With Epoptes tool I shut down all of the computers that were showing in the 'detected clients' window.
-- Computer "9A" wouldn't shut down, remaining in the detected clients window.
-- I went over to the client to check it out and saw that the small green power light on the computer was on, however, even though the display should therefore have been on, it was dark.
-- I checked the logs for previous few days and nothing unusual about that client, just 3 very ordinary entries.
-- I had tail command on the epoptes log as I powered down the client (client is 192.168.67.175)...
:~$ tail -f /var/log/ epoptes. log eceiver (TLSMemoryBIOPr otocol) ,359,192. 168.67. 231] Connection lost: 192.168. 67.231: 33679 eceiver (TLSMemoryBIOPr otocol) ,360,192. 168.67. 153] Connection lost: 192.168. 67.153: 53229 eceiver (TLSMemoryBIOPr otocol) ,361,192. 168.67. 239] Connection lost: 192.168. 67.239: 41613 eceiver (TLSMemoryBIOPr otocol) ,362,192. 168.67. 106] Connection lost: 192.168. 67.106: 42457 protocols. tls.TLSMemoryBI OFactory] Connected: 192.168. 67.195: 42284 eceiver (TLSMemoryBIOPr otocol) ,363,192. 168.67. 195] Connection lost: 192.168. 67.195: 42284 protocols. tls.TLSMemoryBI OFactory] Connected: 192.168. 67.115: 44655 protocols. tls.TLSMemoryBI OFactory] Connected: 192.168. 67.102: 55488 eceiver (TLSMemoryBIOPr otocol) ,365,192. 168.67. 102] Connection lost: 192.168. 67.102: 55488 eceiver (TLSMemoryBIOPr otocol) ,364,192. 168.67. 115] Connection lost: 192.168. 67.115: 44655 67.175: 56049
2016-06-03 17:36:24-0500 [DelimitedBashR
2016-06-03 17:36:24-0500 [DelimitedBashR
2016-06-03 17:36:24-0500 [DelimitedBashR
2016-06-03 17:36:24-0500 [DelimitedBashR
2016-06-03 17:36:24-0500 [twisted.
2016-06-03 17:36:24-0500 [DelimitedBashR
2016-06-03 17:36:24-0500 [twisted.
2016-06-03 17:36:25-0500 [twisted.
2016-06-03 17:36:25-0500 [DelimitedBashR
2016-06-03 17:36:25-0500 [DelimitedBashR
2016-06-03 17:44:04-0500 [-] Ping timeout: 192.168.
... as the client disappeared from the detected clients window.
This is the first time I've seen anything out of the ordinary in the epoptes logs. Not sure if this is relevant. Anywhere else I should check? I do have other epoptes log results from a week ago but as I mentioned, it doesn't look like there's anything out of the ordinary. It probably won't happen again as school's almost over for the year. Let me know any other place to check, I've got times to check in other logs. Thanks!