I have a work station that is intermittently losing the network connection.

Local log shows client_note S_COM 510106 Communications error while receiviing a reply.

Server log:server_error  S_COM 510091  Communications error with socket set notice.

Sesame 2.6 on a Windows Server 2012, workstation is Windows 7, machines are cabled, not wireless.

There was an older solution posted that suggested different versions of Sesame might be the cause.  But the server and the workstation are both using 2.6  Two other systems are not having the problem.  All have identical setups.

Recall from history that there might be a INI or SBASIC setting that might fix this?  A setting for reply timing maybe?

Thanks for that link, Ray.

I have made a change in Norton Security re ports management and I have had a solid connection for 30 minutes.  The longest connection I had all day was about 3 minutes.  We may have a solution already.

Client has had the problem for a while, but does not remember any changes to Sesame or Norton.  Will have to disable auto updates.