The standard and the future of the access protocols used also in an OES environment is CIFS/SMB.

Today the FTP gateway functionality in OES supports to have one central FTP server that can act as a gateway to access all servers that are reachable "internal" through this gateway by just using "cd \\server\volume\path".

This is a great feature - but today only allows to access NCP shares within the same eDirectory tree.
With the CIFS future this needs to be enhanced and allow also remote CIFS connections.

As with CIFS it does not matter anymore if the server is in the same eDirectory or not (just username and password needs to match) - this should open up access to any other CIFS server in the network.

As in such environments also DFS (Micro Focus or Microsoft) plays a big role in many environments the solution also must support both DFS solutions including junctions pointing to multiple targets (fault tolerance).

For CIFS targets that support / require Kerberos, the solution needs to support that.
For CIFS targets that do NOT support Kerberos (i.e. NAS devices), username/password support / NTLM needs to be supported.

It is a great value to have a central FTP gateway as this makes it easy to ensure security and have auditing.

by: Martin W. | over a year ago | FTP