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

Client Firewall active location detection failing

Hello,

I'm having problems getting the Client Firewall (from Endpoint Security & Control 9) to recognize the primary location. No matter how I specify this, my laptop clients always believe they are on the Primary Location, even when the user leaves the office and uses the systems at home.

We have a fairly large WAN connected by leased lines and all served by an Active Directory DNS service. On every site our DNS refers back to the server we use to distribute our Sophos Policies. That system does not have a public IP address as it is hidden behind our firewall.

In the central configuration policy for the Firewall I am setting the Location detection by DNS. My belief being that the FQDN and IP address combination I have entered is always correct when my clients are within our network and will fail to to resolve when they are on foreign networks (like their own broadband connections). I should then be able to configure the firewall to behave differently depending upon it finding the primary location or not.

Now I'm probably doing something wrong here, but no matter how I specify the policy servers IP address, my firewall clients are always showing that the active location is the Primary location. Even when used out of the bounds of our LAN/WAN.

I have made various tests to confirm that the DNS resolution is not the cause of this and this always seems to be fine.

Has anybody else seen this behavior, or can you suggest what I may be doing wrong?

Is there a comprehensive Firewall Configuration guide available? I haven't been able to locate one as yet.

Many thanks in advance,

Paul

:1881


This thread was automatically locked due to age.
Parents
  • Hello Christian, thanks for your reply,

    As you suggested, I have already checked various logs, etc., but there seems to be no way of reconciling the selection of the Primary location with what I see on the client systems.

    NSLOOKUP always responds that the FQDN and even just the host name cannot be located when we are out of the office, so that rules out any DNS, Hosts or LMHosts issues. If I ping away directly at the IP address of the IP Address which we are saying must resolve to verify that the active location is the active location, we get no response. I have also tried using a different host and IP pair just in case it was something to do with the servers relationship with the Sophos client that was the issue (it is the Enterprise Manager host). This also made no difference.

    Calling Tech Support is possible, but would probably be a last resort as would have to check the client systems outside of regular office hours and at home on a broadband connection.

    I was hoping someone would say that I had simply forgotten a ticky-box or something or had come across some documentation that I had not yet located.

    Paul

    :1895
Reply
  • Hello Christian, thanks for your reply,

    As you suggested, I have already checked various logs, etc., but there seems to be no way of reconciling the selection of the Primary location with what I see on the client systems.

    NSLOOKUP always responds that the FQDN and even just the host name cannot be located when we are out of the office, so that rules out any DNS, Hosts or LMHosts issues. If I ping away directly at the IP address of the IP Address which we are saying must resolve to verify that the active location is the active location, we get no response. I have also tried using a different host and IP pair just in case it was something to do with the servers relationship with the Sophos client that was the issue (it is the Enterprise Manager host). This also made no difference.

    Calling Tech Support is possible, but would probably be a last resort as would have to check the client systems outside of regular office hours and at home on a broadband connection.

    I was hoping someone would say that I had simply forgotten a ticky-box or something or had come across some documentation that I had not yet located.

    Paul

    :1895
Children
No Data