Guest User!

You are not Sophos Staff.

Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 6 replies
  • Subscribers 29 subscribers
  • Views 676 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

SSL VPN Issue

ferozsyed

Hello,

I have issue with ssl vpn, the connection is established and the pc and server all ping but issue is the map drive not work with dns name, meaning i have to access the map drive by IP address "\\example\share file " like this not work, but  "\\192.168.114.55\share file" like this working,

some application like database not work with IP base access, the dns name need to be resolve.

Any help would be much appreciated.



This thread was automatically locked due to age.
  • 0

    Hello!

    Are you sure you're using the correct DNS server at the SSLVPN config?

    If you're using the correct DNS Server - did you also create all necessary Firewall Rules? Can the Client communicate with the DNS server as expected?

    Thanks!

    If a post solves your question use the 'Verify Answer' button.

    XG 115w Rev.3 8GB RAM v19.5 MR1 @ Home.

  • +1 in reply to Prism

    Hello,

    Try to use FQDN instead of netbios names! So this would be "example.domain.internal" for instance.

    Mit freundlichem Gruß, best regards from Germany,

    Philipp Rusch

    New Vision GmbH, Germany
    Sophos Silver-Partner

    If a post solves your question please use the 'Verify Answer' button.

  • 0 in reply to Prism

    i didn't create any fw rule for dns, i just put the dns ip on DNS configuration

  • +1

    "\\example\share file" isn't using DNS, it's using some other protocol -- I'm not a Windows guy so not sure.

    From your example, below, it appears that you're listing the appliance (not sure if it's the right port though) as your tertiary DNS server. I guess if you then went into the appliance's DNS host page and created a name for that IP address, it could work. But in reality you should have a server somewhere that does Active Directory, etc, that can resolve the name. The bottom line is that "example" might possibly be resolved via DNS in some sense, but it's not a FQDN which is are the kinds of names that DNS actually supports.

    In some environments, like Apple, you can have names like "example.local" but I don't think that's applicable here.

Share Feedback
×

Submitted a Tech Support Case lately from the Support Portal?