5.8 Server configuration for enabling CIFS

To enable file access to Content Services as a network folder for Windows clients of LiveCycle, you need to enable Common Internet File System (CIFS) in Content Services.

Note: If you are enabling CIFS in an IPv6 environment, you must explicitly enable IPv6 configuration after you configure your LiveCycle installation using Configuration Manager. See “Enabling CIFS in IPv6 mode” in the guide for your application server.

5.8.1 Creating a virtual interface (AIX, Linux, and Solaris only)

If you want to enable CIFS on LiveCycle deployed on AIX, Linux, or Solaris platform, you must create a virtual interface and assign it an IP address on the server that runs LiveCycle. This is required because the CIFS protocol uses the same ports that are used by Samba service on AIX, Linux, or Solaris computers. You specify this virtual IP address as the alternate IP address when you enable CIFS using the Configuration Manager.

If your LiveCycle implementation is on IPv6, you should create virtual IPv6 interfaces on the CIFS server. The interfaces that you create should be within the same network as the CIFS clients. See the documentation related to your operating system for more information.

Note: You should add the virtual interface that you create to the /etc/hosts file to make them persist across reboots.

5.8.2 Configuring Windows Server for CIFS

You will need to manually configure the Windows Server 2003 and 2008 computers that host LiveCycle to enable CIFS on them. When CIFS is enabled, users can access the Content Services repository as a network folder and perform various file operations on their local file system. In Content Services, CIFS is supported for enterprise domain users with ActiveDirectory as their directory provider.

Note: Ensure that the CIFS server has a static IP address for Java-based CIFS implementation. For Windows native implementation, a static IP address is not required.
Note: The user who has enabled remember password would be able to log in to the repository even after his Contentspace role is revoked.

5.8.2.1 Enable NetBIOS over TCP/IP

You need to enable NetBIOS over TCP/IP so that clients connecting to the LiveCycle Server can have their requests resolved for the server host name.

  1. In the Local Area Connection Properties dialog box, on the General tab, select Internet Protocol, and then click Properties.

  2. In the General tab of the Internet Protocol (TCP/IP) Properties dialog box, ensure that the server has a static IP address. Click Advanced.

  3. In the Advanced TCP/IP Settings dialog box, select the WINS tab and select Enable NetBIOS over TCP/IP.

5.8.2.2 Add additional IP address

Note: This step is required only for Java-based CIFS implementation.
  1. In the Local Area Connection Properties dialog box, on the General tab, select Internet Protocol, and then click Properties.

  2. In the General tab of the Internet Protocol (TCP/IP) Properties dialog box, ensure that the server has a static IP address. Click Advanced.

  3. In the Advanced TCP/IP Settings dialog box, select the IP Settings tab and click Add.

  4. Specify a static IP address and click Add.

5.8.2.3 Disable SMB over NetBIOS registry (Windows 2003 only)

You must disable SMB over NetBIOS by editing the Windows registry.

  1. In the Windows Registry Editor, navigate to HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Services > NetBT > Parameters.

  2. Set the DWORD SMBDeviceEnabled to 0. If it is not present, add a new DWORD value with name SMBDeviceEnabled and set it to 0.

5.8.2.4 Disable File and Printer Sharing (Windows Server 2008 only)

Important: After you disable file and printer sharing with this step, you will not be able to access the server directly using Windows file sharing protocol. This computer will not display in the Windows network view.
  • Go to Network Settings and deselect File and Printer Sharing for Microsoft Clients and click Apply.

For additional settings to enable CIFS on Windows Server 2008, see this article.

// Ethnio survey code removed