If your server temporarily loses network, it won't catch that a client has disconnected. Shutting down, rebooting, or powering off the client computer without shutting down the sesame client, can (but usually won't) cause a client misscount. In the admin interface, you could try sending a message to all clients, that may cause the server to notice that those clients have disconnected.

Are you on MS at both ends?

We experienced this same issue again today. I wanted to do some programming changes so I checked to make sure no on else was logged in (not likely at 4:30 a.m.). To my surprise, my machine was shown as being logged on twice. I tried to send a message just to see if one of the log-ins would be dropped, but neither was. I had to wait for our IT to come in and restart Server.

Bseisdes what was mentioned in the above reply, and possibly someone logging off incorrectly, are there other things I can look at that might give me a clue as to what is happening? It seems like we run into this at least every other week.

(Gonna be 35 below zero with the wind chill this weekend - Green Bay, WI - anyone care to come up to the barbecue I'm going to have?? Anyone?? LOL)

Thanks Ray - I'll share this with my IT today.

Fred