For years now I have been using the addEntitlement feature within some encrypted efs that myself and a number of other eSignal users have been using without any problem.
The text files with the usernames are located in my ISP's web servers, which are located in the metropolitan area of Washington D.C. Since the Sandy hurricane hit the area, whenever we open eSignal with one of the encrypted efs, we get the not authorized error and the efs do not run.
Strangely enough when I open a browser (IE or Chrome) with one of the text files that is located in the same directory as the list of the usernames in my ISP's web servers, then the encrypted efs in eSignal work normally and so do any other efs that I open afterwards. This goes on for a few hours and them the problem re appears and I have to reload the browser again to eliminate the problem.
Any idea why do I connect to my ISP's web servers with a browser without any delay while eSignal does not and only does connect once the route has been found by the browser ?
Thank you
The text files with the usernames are located in my ISP's web servers, which are located in the metropolitan area of Washington D.C. Since the Sandy hurricane hit the area, whenever we open eSignal with one of the encrypted efs, we get the not authorized error and the efs do not run.
Strangely enough when I open a browser (IE or Chrome) with one of the text files that is located in the same directory as the list of the usernames in my ISP's web servers, then the encrypted efs in eSignal work normally and so do any other efs that I open afterwards. This goes on for a few hours and them the problem re appears and I have to reload the browser again to eliminate the problem.
Any idea why do I connect to my ISP's web servers with a browser without any delay while eSignal does not and only does connect once the route has been found by the browser ?
Thank you
Comment