Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 7 replies
  • Subscribers 1 subscriber
  • Views 4710 views
  • Users 0 members are here
Options
Suggested
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

Starkadder

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
  • 0

    Hi Christian,

    I agree, there are some curious things going on here, and I will investigate with wireshark on the same laptop when I can get away from the office again.

    However, if this is simply the way that SCF works, I will never be able to achieve what I am looking for as the location will never be correctly identified. What I want is a relaxed configuration as long as the laptop is on the primary site (that is can resolve the address of my Enterprise Management Server), but a more agressive configuration when the laptop is off-network.

    In the tests I made yesterday, the laptop could not see the client, nor could it resolve it's address. So there is no reason for the SCF to switch to the primary location just because I applied a network cable.

    If I can't resolve it over the weekend, I will have to pass it on to Sophos Tech. Support.

    Thanks for all your help so far.

    :1947
Reply
  • 0

    Hi Christian,

    I agree, there are some curious things going on here, and I will investigate with wireshark on the same laptop when I can get away from the office again.

    However, if this is simply the way that SCF works, I will never be able to achieve what I am looking for as the location will never be correctly identified. What I want is a relaxed configuration as long as the laptop is on the primary site (that is can resolve the address of my Enterprise Management Server), but a more agressive configuration when the laptop is off-network.

    In the tests I made yesterday, the laptop could not see the client, nor could it resolve it's address. So there is no reason for the SCF to switch to the primary location just because I applied a network cable.

    If I can't resolve it over the weekend, I will have to pass it on to Sophos Tech. Support.

    Thanks for all your help so far.

    :1947
Children
No Data
Unfiltered HTML