Important note about SSL VPN compatibility for 20.0 MR1 with EoL SFOS versions and UTM9 OS. Learn more in the release notes.

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 1.3/1.4 no entry in local DNS

Sophos Connect 1.4 ist working well and using our internal Windows DNS servers and can resolve our hosts correctly. But:

  • There is no DNS entry of the connected clients in our Windows DNS, so I can not ping the VPN clients from inside our LAN by their hostnames. Pinging the client's IP leased by Sophos XP works.

  • With SSL VPN Client that works. After a client connects by VPN, there is a DNS entry with hostname on our DNS server and I am able to ping the hostname from our LAN.

Does someone know how to solve this?



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

    Thank you for contacting us.

    Could you please provide more details on the scenario and screenshot of DNS entries for Both Sophos Connect and SSL VPN client? It would help us to assist you better.

    Regards,

    Keyur
    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

  • WORKING: Scenario 1 (with Sophos SSL VPN Client)

    Client anwxnbms13 --> SSL VPN Connection (IP 10.81.234.6) established

    OK: Client can resolve all internal hosts
    OK: Pinging anwxnbms13 from local LAN is working (screenshot)
    OK: Entry in Windows DNS Server exists (screenshot)



    SSL-VPN Config:

      

     

     

     NOT WORKING: Scenario 2 (with Sophos Connect 1.3/1.4 Client)

    Client anwxnbms13 --> Sophos Connect Connection (IP 10.81.235.6) established

    OK: Client can resolve all internal hosts
    NOT: Pinging anwxnbms13 from local LAN is NOT working (but pinging IP address works)
    NOT: Entry in Windows DNS Server is missing

    Sophos Connect Config:

     

    Update: The DNS Entries for the Sophos TAP Adapter are correct on the client (172.18.x.x).

  • Hello MVo,

     

    you need to configure the domain name for Sophos Connect policy. You do that using Sophos Connect Admin. Please let me know if you have any questions. Also do let us know if your problem is resolved after you make those changes.

     

    Best Regards,

    Ramesh

  • This reply was deleted.
Reply Children