Some log out records getting lost

[Richard I]

I have a nettalk Timeclock application, accepting log in and log  outs
I have a client with a staff of 80  in approx 20  different locations.
The program is being hosted on their own server using their own static IP address
there are no certificates
The problem started on a retiring server which has subsquently been replaced with a  new Windows 10 server
All can log in and out successfully, except 3 in one location, where they can log in Ok but the log out records  for them,get lost
The logout routine is working correctly because these 3 employees have their status changed in the logout process.and no " if access:nlog.tryInsert = level:notify" messages occur.
The IT has set up different paths to the server for internal and external traffic.
The three staff affected are  logging internally.
This is a consistent problem and it is not simply staff forgetting to log out

I can log these staff out successfully from my remote location.
I am using NT 11.16 but this problem is not  NT version sensitive, as it  was occurring   prior to 11.14

Does anyone please have any idea whats going on, and why it should  fail from one location ?

many Thanks
Richard

[Bruce]

Hi Richard,

>> All can log in and out successfully, except 3 in one location, where they can log in Ok but the log out records  for them,get lost

Are they all the users at this location? Or is it affect 3 out of n?

>> The logout routine is working correctly because these 3 employees have their status changed in the logout process

Status? tell me more about what you mean by this...

>> no " if access:nlog.tryInsert = level:notify" messages occur.

TryInsert does not post messages if it fails. So maybe debug that bit a bit more. Incidentally I'd change it to;

  if access:nlog.tryInsert <> Level:Benign

Cheers
Bruce

[Richard I]

Thanks Bruce,
I think Ive cracked it - the three staff all work at their own workstations  using Excel ,  manipulating data.
Im betting that the  session times out  after they open the browser and app  in the morning and its not closed,and 8 hours later ,when they maximize the browser it appears they can log out.

thanks for your comments about notify and benign - I have locAlerts for the insert  conditions.

Regards,
Richard

[Bruce]

cool.
You could set your session expiry time to say 12 hours to avoid this,
Or set it to go to some "neutral" page (ie not a form) when the session expires.

cheers
Bruce