EIS blocking program over LAN

Recommended Posts

I use EIS on System A. But when one program, Aquarium, tried to communicate from A to other systems on the LAN, there is no response.

 Nevertheless, I can ping other systems from System A; and can ping System A from other systems on LAN. I can also see/use files in shared folders on A from other systems; and vice versa.

System A can function as a slave to other systems with perfectly good two-way communication with Master system. But System A cannon function as master (server) over the LAN. 

  EIS shows up as an added program under EIS protection. How would I add other programs, e.g., those sending data over LAN, to the Protection list?


Share this post

Link to post
Share on other sites

Lets get some debug logs:

  • Open Emsisoft Internet Security from the icon on your desktop.
  • In the 4 little gray boxes at the bottom, move your mouse into the one that says Support, and click anywhere in that gray box.
  • At the bottom, turn on the option that says Enable advanced debug logging.
  • Either click on Overview in the menu at the top, or close the Emsisoft Internet Security window.
  • Reproduce the issue you are having with Aquarium.
  • Once you have reproduced the issue, open Emsisoft Internet Security again, and click on the gray box for Support again.
  • Click on the button that says Send an email.
  • Select the logs in the left that show today's dates.
  • Fill in the e-mail contact form with your name, your e-mail address, and a description of what the logs are for (if possible please leave a link to the topic on the forums that the logs are related to in your message).
  • If you have any screenshots or another file that you need to send with the logs, then you can click the Attach file button at the bottom (only one file can be attached at a time).
  • Click on Send now at the bottom once you are ready to send the logs.
Important: Please be sure to turn debug logging back off after sending us the logs. There are some negative effects to having debug logging turned on, such as reduced performance and wasting hard drive space, and it is not recommended to leave debug logging turned on for a long period of time unless it is necessary to collect debug logs.

Please note that if you have a lot of debugs logs, then you should not send all of them. There is a size limit, and currently there is no error if the message is rejected due to the size being too large. Normally we only need one copy of the 4 or 5 different logs that have been saved after the time you reproduced the issue (the list shows what time each log was saved). Those logs have the following names:

  • Security Center
  • Protection Service
  • Real-Time Protection
  • Firewall
  • Logs database (contains the logs you can view in Emsisoft Internet Security by clicking on Logs at the top of the window).

Share this post

Link to post
Share on other sites

One of our developers looked over your firewall logs, and said they don't contain anything relevant to the issue. He'd like you to turn on debug logging (steps #1 through #3 above), then restart your computer, and then continue from step #5 above to get new logs and send them to us. He thinks that getting logs from the moment the computer has started may reveal the issue.

Share this post

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Recently Browsing   0 members

    No registered users viewing this page.