Jump to content

Firewall and Home WiFi network

Recommended Posts


Hello.  We have 2 PCs, one old Win7 desktop and one brand new win10 laptop.  Both have EIS 2017..5.0.7538. Both are connected to a home wifi network through a router. 

After setting up sharing options (not Homegroup), the two machines are unable to 'see' each other. I noticed that the EIS firewall on the Win10 machine recognizes that there is a wifi network, but the firewall on the win7 machine does not. Please see the attached images.  The firewall rules on both are the same except on Win7 there is an extra rule to allow access to a NIST (Institute of Standards) time server in Colorado (allow UDP port 123 for NIST).

If I turn off the firewall on Win7, everything works and the effect is immediate.  Turn it on, and it breaks.

Please advise.  Thank you. 



EIS WIN10 Firwall wifi.jpg

EIS WIN7 Firewall no wifi recognized.jpg

Link to comment
Share on other sites

Lets get debug logs from the system where EIS isn't seeing your network:

  1. Open Emsisoft Internet Security from the icon on your desktop.
  2. 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.
  3. At the bottom, turn on the option that says Enable advanced debug logging.
  4. Either click on Overview in the menu at the top, or close the Emsisoft Internet Security window.
  5. Restart the computer, and then verify that Emsisoft Internet Security does not show your wireless network in Manage Networks.
  6. Once you have done the above, open Emsisoft Internet Security again, and click on the gray box for Support again.
  7. Click on the button that says Send an email.
  8. Select the logs in the left that show today's dates.
  9. 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).
  10. 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).
  11. 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).

Link to comment
Share on other sites

Thank you. I have forwarded them to our developers so that they can have a look at them.

While we're waiting, lets try getting a diagnostic log so that we can verify that our NDIS driver is properly installed for your wireless adapter. You can find the instructions and download at this link.

When it's done, it will open a log in Notepad (as explained in the instructions). Please save this log somewhere easy to find, such as on your Desktop or in your Documents folder, and then send it to me in a Private Message so that I can take a look at it.

Important: Don't post the log publicly. It contains a copy of your a2settings.ini file, which contains encrypted license information. If someone were to figure out how to break that encryption, then someone else could use your license key.

Link to comment
Share on other sites

From a preliminary look at the logs, we don't think it's a problem in the firewall itself. The logs show that EIS thinks it is configured for a Public network, however from your screenshots the UI appears to be showing a "Private" network. Also, there don't appear to be any problems with the firewall detecting your active network connection, however in your screenshot it doesn't show it in Manage Networks. This will have to be forwarded to the developers who maintain the UI so that they can look in to why this is happening. Note that this team of developers is not as quick to look at logs, so I won't get any info from them right away.

Link to comment
Share on other sites

In my attempts to deal with the other problem described tin the threads abouyt slow boot, unable to connect to service, etc. I ended up uninstalling in safe mode and the reinstalling the  product.

As others have said, this did NOT fix that issue.  

However, reinstalling DID result in our home wifi network finally showing up in the firewall under manage networks. Whether it stays that way remains to be seen.

Regarding the other problem, I did get the beta but did it under the full system. Your GUI won't open in safe mode (just a small window offering to scan) so couldn't do an update there with the beta option.

Too soon to declare that problem fixed.


Link to comment
Share on other sites

17 hours ago, hemlock40a said:

However, reinstalling DID result in our home wifi network finally showing up in the firewall under manage networks. Whether it stays that way remains to be seen.

OK. Let me know if there are any changes in regard to that issue, and if you continue to notice any networking related problems like you were before.

Link to comment
Share on other sites

This topic is now closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Create New...