Using the LDP.exe tool and after making the connection to the AD server, I then ran the BIND test, but it was defaulting to port 389 and no SSL.  I remembered you mentioned that about using the BIND credentials, so this time I set it to port 636 and SSL for the Bind test, and it displayed an error about needing SSL in AD.  After some more research on the Internet about that I realized I had to set up AD CS (Certificate Services).  Found instructions on how to get that done for our active directory services and once that was done, the Test Connection worked as it should with no more errors.    
I have tried for several weeks to get this working and even with a few searches on the Internet for possible clues, and I am still having issues getting our OME server to communicate with AD to get directory info.  I have tried both ports, IP addresses and FQDN, different user login methods, I have tried AD and LDAP, I have checked our DNS servers for records for the OME server (which I can access via a browser using the FQDN) and all I get is this same error on the latest version of OME on a Hyper-V hosted 2019 server...    CSEC5026 - Unable to connect to the LDAP or AD server because the provided IP Address or Port number is invalid.    I know I am missing something, but I have no clue what it is.  Any suggestions at this point other than the ones already reference in a similar posting, which I have already tried those solutions as well, will be appreciated.  I really want to get this working so I can retire our old 2.5 OME server.  
CSEC5026 - Unable to connect to the LDAP or AD server