Thanks Ray, I will try your suggestion.

lksseven wrote on Nov 4^th, 2022 at 6:29pm:


Those are Write/Ping errors to the Sesame client meaning that client is offline/unavailable/unresponsive/Ports were closed/or communications are so slow that they timed out.

-Ray

lksseven wrote on Nov 10^th, 2022 at 7:39pm:


If it only affects certain client systems, I would be looking at the client systems.

Quote:


When you say "Disconnected" do you mean the client is showing up in the Disconnected list of Sesame Server? I'm asking as Sesame clients closed normally do not show up there. It makes no difference to Sesame but could leave records locked.

As a test, here's a screenshot of the Server after a laptop client was disconnected from the network(turned off WIFI completely) so the Sesame Server disconnected it after 10 failed pings. Closed the Sesame Client, reconnected to Network(same IP) and then I restarted the Sesame client. At the time of the screenshot it had no issues in a little over 11 minutes. It's now been over 40 minutes and still no issues, failed Pings, or network errors.

-Ray

Looking at that picture, Your client has already been disconnected once and is failing pings again(which are on the 20,001 port, not the main 20,000 port). That Server also has something else trying to connect to it at 11:31 PM and 3:04 AM. Are you running an Internet Security program or other program that might be sniffing open ports on the Server?

-Ray

So, here's my workaround (I don't have a theory; this is just what appears to be working)...
- client computer logs on network and boots up sesame.
- work work work
- laptop is closed and taken home
- next day, laptop opened and logged on, and Sesame engine starts showing read write errors and then shortly thereafter kicks off the Sesame client, stating that 192.168.1.36 has been disconnected.  If I re load Sesame client (still with ip .36), Sesame engine starts showing read write errors (red strip) and again Sesame server engine kicks off the client.
------ 
But, if I go into laptop network adaptor and change the MAC address (spoof, in other words), then when the network adaptor reenables itself with the new MAC (just changed the last digit), it gets a new IP address from the router (192.168.1.38), and Sesame engine welcomes the new load of Sesame client with open arms.

If I repeat the laptop shutdown , reopen and reconnect, keeping the MAC so that the ip .38 stays the same, Sesame engine doesn't like it, read write (red strip) errors, and soon a kickoff of the client , stating not only line client 192.168.1.36 has been disconnected, but adding a second line that client 192.168.1.38 has also been disconnected.

If I change MAC address to '..c3', then get new ip of .39, and Sesame engine loves it.  IF I disconnect Sesame client, a repeat of the above, resulting with 3 disconnected lines .36, .38, .39 . 
But if I go back and change MAC back to original '..c1', router reassigns ip .36, and Sesame engine so far in an hour loves it - no red strip, no client kicked off. 

Does the Sesame server have a cache that gets rotated out, so third time's a charm and the original offending 'ip.36' gets dropped out of the cache, making Sesame engine then think a subsequent request from 'ip.36' is virginal ?

In any case, having to take 40 seconds to change MAC address upon opening laptop each day is far better than having to take 15 minutes shutdown/reload server sesame engine and reloading clients