1 Reply Latest reply on May 29, 2017 4:00 AM by Robin Rowe

    Help... after upgrade datanow 3.5 to FileDirector 4.2, NO DFS resouces available

    Michel.Herbiet Rookie

      Hi,

      We have upgraded the Appliance to version 4.2, install from scratch 4.0, import config and update to update 4.2.

       

      From browser (IE) we do NOT have access to the map points that are configured via DFS.
      Direct access to the shares on the fileserver is OK from the browser (IE)

       

      We tested on a tablet with the application, access is OK

      Via Browser only direct FileServer links are OK, all DFS publications are NOT OK.

       

      This mornig we opened a call for the access to the admin console, we needed to DISABLE TLS1.0 in the config of our browser, reading the doc, this is ONLY for admin console, not for clients although we have tested ALSO with TLS 1.0 disabled and only using TLS 1.1 and 1.2.

       

      Can you help?

       

      Thx,

      Michel.

      VBy Browser:

      FileDirWITH-InternetExplorer.png

      By Application:

      FileDirWITH-IpadApplication.png.jpg

        • 1. Re: Help... after upgrade datanow 3.5 to FileDirector 4.2, NO DFS resouces available
          Robin Rowe SupportEmployee

          Hi Michel,

           

          The most likely cause here is either:

          - One or more of your DFS map points point to folder targets that only support SMB v1 (File Director 4.x and above only support SMB 2/SMB 3)

          A method of checking the available SMB version of a given file server is detailed in the following blog - https://www.ivanti.com/blog/performance-improvements-in-datanow-v4/

          - Your file server(s) does not have a valid reverse DNS record (PTR record) that matches its A record - File Director 4.0+ has strict requirements for PTR records in order to support file servers that are behind NLB devices. Use NSLookup to confirm that the required PTR records are in place, and if not, add them. Verifying Your Basic DNS Configuration

           

          Re TLS 1.0 - the experience between client and browser can be different - In Windows, the browser uses WinINET settings, and the client uses WinHTTP, which may have differences in support with TLS. by default Windows 7 WinHTTP does not support TLS1.1/1.2 and needs additional configuration. The setting in the admin console also applies to client connections.

           

          I hope this helps

           

          Robin