What platforms will CIFS support?
Answer: CIFS will support both the Integrity server and AlphaServer systems. VAX will not be supported.
The OpenVMS CIFS product is being built to take advantage of features added to OpenVMS v8.3 and later. v7.3-2 will not be supported.
For earlier versions of OpenVMS operating system, HP continues to support either Pathworks or Advanced Server as a print and file solution.
What will be the cost for CIFS?
Answer: CIFS will be provided for free with a valid license to operate on OpenVMS operating system for both Integrity server and AlphaServer
How will CIFS be distributed?
Answer: CIFS can be accessed and downloaded from the CIFS home page. CIFS will also be available
as part of the Software Products Library distribution. In future, CIFS will be available with the quarterly distributions in support of both Integrity server
and AlphaServer system.
How will CIFS be supported?
Answer: CIFS will be supported as part of the OpenVMS operating system for Integrity server.
For CIFS on AlphaServer systems, a valid support contract for CIFS will be required and would be similar to that of the Advanced Server.
Why does the CIFS documentation have a Unix flavor?
Answer: The initial file and print solution (Samba) was developed in support of the Unix operating system.
CIFS is a port to OpenVMS of the Samba product with specific text in support of OpenVMS users.
Please provide feedback by using the button below if you require an update to the documentation.
Will CIFS support Active Directory?
Answer: Yes, the production version based on Samba v3.X will support MS Windows 2000
and later of Active Directory. It will be supported in NT compatible mode based on WIN NT v4.0 Server.
Full Active directory will follow based on completion of LDAP and Kerberos on OpenVMS.
Will CIFS allow a server to be a member of an Active Directory domain or a NT4 domain?
Answer: CIFS will support both as an NT4 domain member. CIFS will support active directory as a member, in the future.
How do I convert an OpenVMS directory specification into a UNIX path specification?
Answer: Path specifications in the smb.conf file currently need to be in UNIX format, where an OpenVMS directory specification of
PROJECT_ROOT:[MYPROJ] is /project_root/myproj/ . For example, "PROJECT_ROOT_[XY^.Z]" should be written as "/PROJECT_ROOT/XY.Z/"
Will external authentication be supported?
Answer: We plan to support external authentication on the production version of CIFS.
What tools will be provided with CIFS?
Answer: A variety of administrative tools will be provided with Samba (PDBEDIT, NMBLOOKUP, SWAT, and more).
Migration tools will be provided for migration from Advanced Server to CIFS.
Does OpenVMS CIFS support smbmount?
Answer: The smbmount program is used to mount a remote share on a host system.
The smbmount functionality is only available on LINUX and some BSD variants of UNIX according to the samba.org FAQ on the subject.
For more information, please refer to samba.org FAQ pages. Currently, there are no plans of implementation of
smbmount or an equivalent on OpenVMS.
What do I input for the print command on a printer share in SMB.CONF?
Answer: The print command for an OpenVMS served print share should be:
print command = /delete.
You can add other OpenVMS print qualifiers to the print command. The syntax for setting the print command may change with the production release of OpenVMS CIFS.
Does OpenVMS CIFS support ACLs?
Answer: Both OpenVMS CIFS and Advanced Server will honor ACLs with traditional OpenVMS ACEs. Advanced Server has additional
ACEs that the pending release of OpenVMS CIFS does not understand. This is planned to be addressed in a future production quality release of OpenVMS CIFS.
Advanced Server does not allow client computers to see or manipulate traditional OpenVMS ACEs.
Why does Advanced Server have different ACEs than OpenVMS ACEs?
Answer: The order that a Microsoft based server interprets ACLs is different from the order that OpenVMS uses to interpret ACLs.
Advanced Server simulates the Microsoft ACL handling to provide a more consistent interface to the client computers. These Advanced Server
ACEs also allow the use of group names that cannot be directly represented by traditional OpenVMS ACLs.
Will OpenVMS CIFS be able to show/modify traditional OpenVMS ACEs?
Answer: The OpenVMS CIFS engineering team is primarily focused on providing the same functionality as with Advanced Server.
Allowing the display and manipulation of OpenVMS ACEs is an enhancement that is being investigated.
HP is committed to protecting your privacy. Learn more.