Jump to content

Network Profile Selection Error


Recommended Posts

We have an ESET network profile for our company with a single activator: "Windows profile: Domain".

Users in branch offices get this profile correctly.  However, remote employees, who are connected to company-provided gateways, do not - even though Windows shows that the connection profile is indeed "Domain".  This was verified by running `Get-NetConnectionProfile`.

The only thing that seems to link the affected systems is that they are on remote gateways in their home instead of a branch office.  The DNS, hostname, and connection profiles are otherwise identical.

Expected:

Company network profile be applied by ESET.

Actual:

Public network profile is applied by ESET.

 

Link to comment
Share on other sites

  • Administrators

This will need to be checked by the technical support or developers. Please raise a support ticket.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

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