locked
Need help for FTP LDAP Authentication RRS feed

  • Question

  • User-766640730 posted

    Hello everyone,

    I am trying to use the Robert McMurray guide to create an FTP LDAP authentication provider

    to configure my FTP server for user authentication using Active Directory users.

    In my environment, I am using Windows Server 2019 to run the FTP server.

    The first issue I faced was that apparently (according to the output of the code obtained via the troubleshooting guide) the custom provider was not able to read the provided configuration options (i.e. ldapServer and ldapPartition) from applicationHost.config file.

    I then tried to provide the options by hardcoding them, but still I get a message saying: "FtpLdapAuthentication: The server could not be contacted.". Though there is no connection attempt seen in the output of "netstat -an 2" command.

    Please help me get over this issue.

    Regards, Alireza

    Sunday, March 7, 2021 5:59 AM

All replies

  • User1771714573 posted

    Hi goftari,

    Did you enable the port of FTP LDAP Authentication in firewall? If the port is disable, request or connection will be refused.

    By the way, the first link of Robert McMurray guide to create an FTP LDAP authentication provider has been deleted.

    Best regards,

    Brucz

    Monday, March 8, 2021 6:15 AM
  • User-766640730 posted

    Hi Brucz,

    Thanks for your reply,

    I mistakenly linked to the wrong URL, which is now corrected and is:

    https://blogs.iis.net/robert_mcmurray/ftp-and-ldap-part-1-how-to-use-managed-code-c-to-create-an-ftp-authentication-provider-that-uses-an-ldap-server

    For sure I did define the required LDAP port between the FTP server and Active Directory domain controller (i.e. 389) and have tested its connectivity using telnet command.

    Monday, March 8, 2021 6:36 AM
  • User1065476709 posted

    Hi goftari,

    I then tried to provide the options by hardcoding them, but still I get a message saying: "FtpLdapAuthentication: The server could not be contacted.". Though there is no connection attempt seen in the output of "netstat -an 2" command.

    It may also be caused by a firewall, you can try to disable the firewall and try again.

    Best regards,

    Sam

    Thursday, March 25, 2021 8:54 AM