Guest User!

You are not Sophos Staff.

Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 10 replies
  • Answers 1 answer
  • Subscribers 27 subscribers
  • Views 2107 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

[Sophos Connect] DNS Problem, only reboot helps

StefanS

Hi there,
Sophsos Connect v2.1.20.0309 + SophosXG 18.5.2 + Windows 10 1809

After a certain time the name resolution does not work anymore, only "nslookup".
Restarting the device, this works again for a certain time.
There are some problems with "sophos connect v.2.1x" and DNS, is this problem possibly also ?
Is there a solution to the problem, because it makes little sense to have to reboot the whole device because of a DNS problem.

thx
StefanS



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

    Im not aware of DNS problems with Connect Client but can imagine, they exist.

    Can you please describe:

    which device is DNS server when connected with CC?

    which device is rebooted - computer with CC or Firewall?

    .

    On the endpoint computers:

    what typ of NIC and WiFi hardware is used?

    do you have computers not having the problems?

    what's the output of ipconfig -all when connected with CC and the problem occours?

    what's the output of route print when connected with CC and the problem occours?

    is the configured DNS server pingable when connected with CC and the problem occours?

  • 0 in reply to LHerzog

    Hi
    > which device is DNS server when connected with CC?
    The settings of IPSec (remote access) DNS 1 / 2 server, both domain controllers.

    >which device is rebooted - computer with CC or Firewall?
    NB with CC

    >is the configured DNS server pingable when connected with CC and the problem occours?
    Generally, the DNS resolution then no longer works, of course also no ping. Only nslookup directly, here all DNS entries are resolved correctly.


    The rest will follow as soon as i have more information.

    By the way, we have this "phenomenon" not only on one device, some others are also affected, but not all.
    We had reported a ticket with this bug almost 2 years ago.
    It was not fixed in v17 (did not want it) and should "actually" be fixed in v18 + CC 2.1........

  • 0 in reply to StefanS

    >is the configured DNS server pingable when connected with CC and the problem occours?
    Generally, the DNS resolution then no longer works, of course also no ping. Only nslookup directly, here all DNS entries are resolved correctly.

    does this also apply for internal private domain names or public internet FQDN?

    what is your VPN config? Split or tunnel all?

    maybe this is more an issue with Windows endpoints than Connect client? Have you already tried reordering interface metrics like mentioned on those two websites?

    http://woshub.com/dns-resolution-via-vpn-not-working-windows/

    https://superuser.com/questions/966832/windows-10-dns-resolution-via-vpn-connection-not-working

  • 0 in reply to LHerzog

    >does this also apply for internal private domain names or public internet FQDN?
    only internal.

    >what is your VPN config? Split or tunnel all?
    Split

Reply Children
No Data
Share Feedback
×

Submitted a Tech Support Case lately from the Support Portal?