Jump to content

Bootloop

Members
  • Posts

    2
  • Joined

  • Last visited

About Bootloop

  • Rank
    Newbie
    Newbie

Profile Information

  • Location
    U.K.
  1. "..If ESET is installed through an RDP session, the firewall is disabled to prevent the connection from being disconnected.." This is not the case - unless the incorrect installer may have caused this - as soon as the install completed the RDP session was dropped. On the laptops incoming RDP sessions were not connecting even though in the ESET config port 3389 was open via svchost.exe Once I disabled the Network Protection manually RDP sessions were able to get through. I'll get the settings changed as you suggest, but this will require another on-site visit now.
  2. We've been installing ESET for a lot of our clients and it seems the default install blocks all incoming/outgoing network traffic. The issue was found during the recent installs when RDP connections were failing although RDP was enabled within the ESET firewall rules. Completely disabling 'Network protection' allows traffic and connections to the machines. The package is the standard download from ESET and then licensed using a Corp login (Email/password) then assigning the license. The latest problem was when a colleague installed on a remote server then lost all connection. I accessed the server locally and the ESET was sat on the final setup screen after install. Is there anyway we can set a policy per license to prevent this from happening? I've found various posts regarding this dating back 2 years with no firm solution. Thanks
×
×
  • Create New...