Skip to main content
A
Anonymous_User
Contributor
January 31, 2010
Question

SSL VPN DNS Error

  • January 31, 2010
  • 5 replies
  • 7113 views
Hi i made up a ssl vpn, it seems to work, but i can ping o rdp all servers only by ip, when i try to use FQDN ive got the following error name server is not reachable because of dns error i read FortiGate® SSL VPNs FortiOS™ Handbook 4.0 MR1 unsuccessfully can someboy help me? Francesco

    5 replies

    cgofish23
    cgofish23
    New Member
    January 31, 2010
    Do you have your internal DNS servers set in the SSL VPN config? VPN -> SSL, select the Config tab, at the bottom you will see Advanced (DNS and WINS Servers)
    A
    Anonymous_UserAuthor
    Contributor
    February 1, 2010
    Yes i do
    rwpatterson
    rwpatterson
    New Member
    February 1, 2010
    You have to edit the FortiSSLVPN network adapter and add the DNS domain to the advanced section of TCP/IP. This needs to be done on each install. This cannot be pushed with the SSL VPN IP information.
    cgofish23
    cgofish23
    New Member
    February 2, 2010
    We have seen this on some installs and some work fine without it.... one of the things on my list to look into as to why some installs require it. I always assumed it was something with the configuration/security of the internal DNZ server. 1) Anyone have any insight on this? or 2) Anyone know of a way to automate adding the DNZ suffix into the FortiSSL adapter?
    rwpatterson
    rwpatterson
    New Member
    February 2, 2010
    ORIGINAL: cgofish23 2) Anyone know of a way to automate adding the DNZ suffix into the FortiSSL adapter?
    As far as I know, it can' t be done, as of yet...
    A
    Anonymous_UserAuthor
    Contributor
    February 7, 2010
    Solved!! Configured my internal Dns on Fortigate
    RachelGomez123
    RachelGomez123
    New Member
    November 16, 2022

    Go to the Properties of that connection and then further go to TCP/IP Properties. Click on Advanced and make sure that " Use default gateway on remote network" is unchecked. Click on OK and OK again and close the connection properties. Now, connect to the tunnel again and the problem should be resolved.

     

    This may help you,

    Rachel Gomez

    Terms & ConditionsAccessibility statement