2.3 ConsoleOne in a Multiple-Platform Environment

If your GroupWise system includes multiple platforms, you can administer Linux domains from Windows ConsoleOne or administer NetWare or Windows domains from Linux ConsoleOne.

This section helps you set up the cross-platform connections that enable ConsoleOne to successfully access GroupWise databases on any platform.

2.3.1 Using Windows ConsoleOne to Access Domains and Post Offices on Linux

In order for you to be able to use ConsoleOne on Windows to administer GroupWise domains, post offices, and agents that are located on Linux, the Linux servers where the domains, post offices, and agents are located must be accessible from Windows.

Using NetWare Core Protocol to Connect a Windows Server to an OES Linux Server

On OES Linux, if you are using the ext3 or reiserfs filesystem, you use Novell Core Protocol (NCP) to configure the Linux server for access from a Windows server. Then, on Windows, you use the Novell Map Network Drive feature to map a drive from Windows to the Linux filesystem where the domain or post office is located.

Configuring the OES Linux Server for NCP Access from Windows

  1. In a terminal window on the OES server, become root by entering su - and the root password.

  2. If you are creating a new domain or post office on the OES Linux server, create the base directory where you want to use Windows ConsoleOne to create the domain and/or post office directory structure.

    or

    If you are not creating a new domain or post office on the OES Linux server, make sure you know where the existing base directory is located.

  3. Enter the following command to create the NCP volume on the OES Linux server:

    ncpcon create volume volume_name /directory

    1. Replace volume_name with a unique name for the location where you want to create the domain and/or post office directory structure

    2. Replace directory with the directory referenced in Step 2 above.

  4. Verify that the volume has been created:

    more /etc/opt/novell/ncpserv.conf

    The new volume should be listed at the end of the NCP server configuration file.

  5. Enable cross-protocol locks so that Windows ConsoleOne can safely access GroupWise databases across the connection between Windows and Linux:

    1. Enter the following command

      ncpcon set cross_protocol_locks=1

      or

      Add the following line at the bottom of the ncpserve.conf file:

      CROSS_PROTOCOL_LOCKS 1

    2. Restart the Novell eDirectory daemon:

      rcndsd restart

  6. Continue with Mapping a Windows Drive to the NCP Volume.

Mapping a Windows Drive to the NCP Volume

  1. On the Windows server, right-click on the Windows taskbar, then click Novell Map Network Drive.

  2. Select the drive letter to map to the NCP volume on the OES Linux server.

  3. Specify the network path to the NCP volume in the following format:

    \\linux_hostname\ncp_volume

    1. Replace linux_hostname with the hostname of the OES Linux server.

    2. Replace ncp_volume with the name of the NCP volume that you just created.

  4. For the network user name, specify the fully qualified administrator user name for eDirectory., such as admin.users.novell.

  5. Select Check to always map this drive letter when you start Windows.

  6. Click Map.

  7. (Conditional) If prompted, log in to eDirectory:

    1. In the Password, specify the eDirectory password for the administrator user.

    2. In the Context field, specify the eDirectory context where the administrator User object is located.

  8. Click OK.

    The mapped drive to the OES Linux server opens in Windows Explorer and can now be accessed from Windows ConsoleOne.

Using Samba to Connect a Windows Server to an OES Linux Server

On OES Linux, if you are using the Novell Storage Services (NSS) filesystem, you use Samba to create the connection between Linux and Windows. Then, on Windows, you use the Novell Map Network Drive feature to map a drive from Windows to the Samba share.

Identifying the Directory Structure for the Samba Share

  1. In a terminal window on the OES Linux server, become root by entering su - and the root password.

  2. If you are creating a new domain or post office, create the base directory for the new domain and/or post office.

    or

    If you are not creating a new domain or post office, make sure you know where the existing directory is located.

  3. Continue with Installing Samba.

Installing Samba

If you installed Samba when you installed OES Linux, skip to Logging In to iManager.

If you did not install Samba when you installed OES Linux, install it now:

  1. Start YaST.

  2. Under Groups, click Open Enterprise Server, then click OES Install and Configuration.

  3. Under OES Services, select Novell Samba, then click Accept.

  4. Follow the prompts to install Novell Samba.

  5. Continue with Logging In to iManager.

Logging In to iManager

  1. Access the following URL:

    https://ip_address/nps/servlet/webacc?taskid=fw Startup

    Replace ip_address with the IP address of the OES Linux server.

  2. Specify the eDirectory administrator user name, such as admin.users.novell, the password for the user name, and the IP address of the eDirectory tree, then click Login.

  3. Continue with Configuring the eDirectory Universal Password for Samba.

Configuring the eDirectory Universal Password for Samba

  1. In iManager, click Passwords > Password Policies.

  2. Click Samba Default Password Policy.

  3. On the Policy Assignment tab, browse to and click the name of the administrator User object that you want to administer the Samba share, then click OK to add the user to the list.

  4. Click OK to complete the process.

  5. Continue with Setting the eDirectory Universal Password for the Samba Administrator User.

Setting the eDirectory Universal Password for the Samba Administrator User

  1. Under Passwords, click Set Universal Password.

  2. Browse to and click the name of the Samba administrator User object, then click OK.

  3. Specify the password for the Samba administrator user, retype the password for confirmation, then click OK.

  4. Click Passwords to close the Passwords menu.

  5. Continue with Creating a Samba Share.

Creating a Samba Share

  1. Click File Protocols, then click Samba.

  2. Browse to and click the name of the Server object where you are setting up the Samba share.

  3. On the Shares tab, create a new Samba share for the directory on the Linux server reference in Identifying the Directory Structure for the Samba Share:

    1. Click New.

    2. Specify a unique name for the Samba share, such as gwsystem.

    3. Specify the full path name on the Linux server for the domain or post office, click OK to add the location to the list of Samba shares, then click Close.

    4. Click File Protocols to close the File Protocols menu.

  4. Continue with Setting the eDirectory Rights for the Samba Share.

Setting the eDirectory Rights for the Samba Share

  1. Click Files and Folders, then click Properties.

  2. Browse to and click the name of the Linux partition or directory where you created the new share, then click OK.

  3. Click Rights.

  4. In the Add Trustee field, browse to and click the name of the Samba administrator User object, then click OK.

  5. Grant all file system rights to the Samba administrator user, then click OK.

  6. Continue with Testing Samba on the OES Server.

Testing Samba on the OES Server

  1. Double-click the Home Directory icon on the Linux desktop.

  2. Click

  3. In the Location field, type smb://user_name@ip_address

    1. Replace user_name with the user name of the Samba administrator user.

    2. Replace ip_address with the IP address of the Linux server.

      The File Browser should display all Samba shares, including the new one that you created for the domain and/or post office.

  4. Continue with Mapping a Windows Drive to the Samba Share on the OES Linux Server.

Mapping a Windows Drive to the Samba Share on the OES Linux Server

  1. In Windows Explorer, right-click the Computer object, then click Map network drive.

  2. In the Drive field, select the drive letter for the new Samba share.

  3. In the Folder field, specify the location of the Samba share in the following format:

    \\ip_address\share_name

    1. Replace ip_address with the IP address of the Linux server.

    2. Replace share_name with the name of the new Samba share.

  4. Select Reconnect at logon.

  5. Select Connect using different credentials.

  6. Specify the Samba administrator user name and password, then click OK.

    The Samba share for the OES Linux file system opens in Windows Explorer and can now be accessed from Windows ConsoleOne.

Using Samba to Connect a Windows Server to a SLES Server

On SLES, you use YaST and the Samba Web Administration Tool (SWAT) to configure Samba. Then you use the Windows Map Network Drive feature to map a drive from Windows to the Samba share.

Identifying the Directory Structure for the Samba Share

  1. In a terminal window on the OES server, become root by entering su - and the root password.

  2. If you are creating a new domain or post office, create the base directory for the new domain and/or post office directory structure.

    or

    If you are not creating a new domain or post office, make sure you know where the existing directory is located.

  3. Continue with Preparing Your Firewall to Allow Samba Connections.

Preparing Your Firewall to Allow Samba Connections

  1. In YaST, click Security and Users > Firewall, then click Interfaces.

  2. Click Change, select Internal Zone, then click OK.

  3. Click Next to view the summary, then click Finish.

  4. Continue with Configuring the Samba Server.

Configuring the Samba Server

  1. In YaST, click Network Services > Samba Server.

  2. Specify a workgroup or domain name, then click Next.

    For use in your GroupWise system, the Samba server does not need to be part of a workgroup or domain, so it does not really matter what you put in this field. For example, you could use GWSYSTEM.

  3. Select Not a Domain Controller, then click Next.

    For use in your GroupWise system, the Samba server does not need to be a domain controller.

  4. Under Service Start, select During Boot.

    Because you prepared the firewall in Preparing Your Firewall to Allow Samba Connections, the firewall port for Samba is already open.

  5. Click OK to finish the basic configuration of the Samba server.

  6. Continue with Configuring the Samba Web Administration Tool (SWAT).

Configuring the Samba Web Administration Tool (SWAT)

  1. In YaST, click Network Services > Network Services (xinetd).

  2. Select Enable.

  3. In the Currently Available Services list, select swat, then click Toggle Status (On or Off).

    SWAT is off by default. This turns it on.

  4. Click Finish.

  5. Continue with Accessing SWAT.

Accessing SWAT

  1. Display SWAT in your Web browser with the following URL:

    http://localhost:901

  2. Specify the root user name and password, then click OK.

  3. On the SWAT toolbar, click Status to verify that smbd and nmbd are running.

    It is not necessary for winbindd to be running.

  4. Continue with Creating a Samba Share.

Creating a Samba Share

  1. On the SWAT toolbar, click Shares.

  2. In the Create Share field, type a unique name for the share, such as gwsystem, then click Create Share.

  3. In the Path field, specify the directory that you created in Identifying the Directory Structure for the Samba Share.

  4. In the Read Only field, select No.

  5. In the Available field, select Yes.

  6. Click Commit Changes.

Mapping a Windows Drive to the Samba Share on the SLES Server

  1. On the Windows desktop, right-click the Computer object, then click Map network drive.

  2. In the Drive field, select the drive letter for the new Samba share.

  3. In the Folder field, specify the location of the Samba share in the following format:

    \\ip_address\share_name

    1. Replace ip_address with the IP address of the Linux server.

    2. Replace share_name with the name of the new Samba share.

  4. Select Reconnect at logon.

  5. Select Connect using different credentials.

  6. Specify the Samba administrator user name and password, then click OK.

    The Samba share on the SLES server opens in Windows Explorer and can now be accessed from Windows ConsoleOne.

Accessing a Domain or Post Office on Linux from Windows ConsoleOne

After you have made the Linux server visible from Windows:

  1. Map a drive to the domain directory on the Linux server.

  2. In Windows ConsoleOne, click Tools > GroupWise System Operations > Select Domain.

  3. Browse to and select the domain directory, then click OK.

You can now use Windows ConsoleOne to administer all GroupWise objects that belong to the domain that is located on Linux.

2.3.2 Using Linux ConsoleOne to Access Domains and Post Offices on NetWare or Windows

In order for you to be able to use ConsoleOne on Linux to administer GroupWise domains, post offices, and agents that are located on NetWare or Windows, the NetWare or Windows servers where the domains, post offices, and agents are located must be accessible from Linux.

Working with the Linux Mount Directory

The first time you run Linux ConsoleOne on a server, you are prompted to provide a Linux mount directory on that server. The default location is /mnt.

Underneath the Linux mount directory, you must create a subdirectory for each directory where a domain or post office resides on a Windows server, that you want to be able to access from Linux ConsoleOne. For example, if you have a domain directory named provo1 on a Windows server, you would create a provo1 subdirectory under /mnt on the Linux server where you want to run ConsoleOne.

Making a Windows Server Visible in Linux ConsoleOne

  1. Use the appropriate command to mount the Windows share to the Linux server where you want to run ConsoleOne:

    SLES 11:

    		 
    mount -t cifs //fully_qualified_hostname/windows_share_name 
        /linux_mount_directory -o username=windows_administrator

    SLES 10:

    		 
    mount -t smbfs //fully_qualified_hostname/windows_share_name 
        /linux_mount_directory -o username=windows_administrator

    NOTE:The SLES 11 mount command does not accept smbfs as a valid mount type. CIFS (Common Internet File System) is an update to the SMB (Samba) protocol.

    1. Replace fully_qualified_hostname with the name of the Windows server that you are mounting the Linux server where you want to run ConsoleOne, such as provo1.novell.com.

    2. Replace share_name with the name of the Windows share on the Windows server, such as C.

    3. Replace linux_mount_directory with the full path for the directory that you created in Working with the Linux Mount Directory.

    4. Replace windows_administrator with the user name of the administrator user of the Windows server, such as Administrator

  2. Create a script in the /mnt directory with the resulting mount command, then run the script.

  3. Change to the domain or post office directory that you have mounted, then enter the following command:

    touch test

    This creates a file named test across the mount and shows that Linux ConsoleOne will also be able to write across the mount.

  4. To make the mount persistent, so that it is automatically available whenever you reboot the Linux server, edit the /etc/fstab file with the same information that you used in the mount command.

Making a NetWare Server Visible in Linux ConsoleOne

To make a NetWare server visible from Linux, you mount the directory you need to access as a Linux file system.

mount -t ncpfs NetWare_server_full_DNS_name_or_IP_address
               /Linux_mount_location/mount_point_directory
               -o user=fully_qualified_username
               -o ipserver=NetWare_server_full_DNS_name

A NetWare server full DNS name should have the format of mail2.provo.corporate.com. A fully qualified username should have the format of Admin.Users.Corporate. A typical Linux mount location would be /mnt.

Accessing a Domain or Post Office on NetWare or Windows from Linux ConsoleOne

After you have made the NetWare or Windows server visible from Linux:

  1. Mount the domain directory to the Linux server.

  2. In Linux ConsoleOne, authenticate to the eDirectory tree where the Domain object is located.

  3. Click Tools > GroupWise System Operations > Select Domain.

  4. Browse to and select the domain directory, then click OK.

You can now use Linux ConsoleOne to administer all GroupWise objects that belong to the domain that is located on NetWare or Windows.