This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Reject Network Connection with DHCP Servers

This may be a limitation or an oversight but have been hitting a problem with having "Reject Network Connections" turned on when the DHCP server is on a windows server when clients login first thing, this causes alot of clients if they have been offline for a day or so to not get issued a DHCP ip as the server rejects the connection because they have been blocked by sophos endpoint, therefore they cannot get an IP to talk to the firewall to then talk to sophos to update to resolve the reason why they are blocked, anyone else found this?

We cannot move the DHCP service as we use options on it and we want protection on all servers, maybe some sort of service exception is required?



This thread was automatically locked due to age.
Parents
  • Hi  

    I'd like to know whether the endpoint has Red health which is not getting IP from DHCP server or otherwise.

    I'd also suggest you to refer the exclusions section in this article if it can resolve your issue.

    Regards,

    Jasmin
    Community Support Engineer | Sophos Support

    Sophos Support VideosKnowledge Base  |  @SophosSupport | Sign up for SMS Alerts |
    If a post solves your question use the 'This helped me' link

  • The endpoint was green and the server is already in the excluded list, this is what makes for the problem as nothing shows the client as Red yet the server still blocks traffic to it and when watching the server the alert toast pops up stating it has blocked connection and the client doesnt get assigned an IP. the fix so far is to add the client to the exclusion list until it connects and then all is fine but doing this for 10/20 machines a morning is unworkable, have had to turn the Reject setting off for now

    Sophos XG Engineer

    Sophos Silver Partner

Reply
  • The endpoint was green and the server is already in the excluded list, this is what makes for the problem as nothing shows the client as Red yet the server still blocks traffic to it and when watching the server the alert toast pops up stating it has blocked connection and the client doesnt get assigned an IP. the fix so far is to add the client to the exclusion list until it connects and then all is fine but doing this for 10/20 machines a morning is unworkable, have had to turn the Reject setting off for now

    Sophos XG Engineer

    Sophos Silver Partner

Children