If your GroupWise system includes both Linux and Windows, you can administer Linux domains and post office from Windows ConsoleOne and administer Windows domains and post offices from Linux ConsoleOne.
NOTE:If your GroupWise system still includes NetWare domains and post offices, see Migrating Away from NetWare
in Update
in the GroupWise 2012 Installation Guide for NetWare-specific considerations.
This section helps you set up the cross-platform connections that enable ConsoleOne to successfully access GroupWise databases on any platform.
In order for you to be able to use Linux ConsoleOne to administer domains and post offices that are located on Windows, the domain and post office directories on the Windows servers must be mounted as Linux filesystems.
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. For more information, see Linux Mount Directory
in Planning a Basic GroupWise System
in the GroupWise 2012 Installation Guide. For convenience, you can later change the Linux mount directory, as described in Section 2.1.6, Changing the Linux Mount Directory.
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.
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,noserverino The noserverino option uses client-generated inode numbers instead of server-generated inode numbers, which produces a more reliable CIFS mount. |
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.
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.
Replace share_name with the name of the Windows share on the Windows server, such as C.
Replace linux_mount_directory with the full path for the directory that you created in Working with the Linux Mount Directory.
Replace windows_administrator with the user name of the administrator user of the Windows server, such as Administrator
Create a script in the /mnt directory with the resulting mount command, then run the script.
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.
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.
After you have made the Windows server visible from Linux:
Mount the domain directory to the Linux server.
In Linux ConsoleOne, authenticate to the eDirectory tree where the Domain object is located.
Click
.Browse to and select the domain directory, then click
.You can now use Linux ConsoleOne to administer all GroupWise objects that belong to the domain that is located on Windows.
In order for you to be able to use Windows ConsoleOne to administer domains and post offices that are located on Linux, the Linux servers where the domains and post offices are located must be accessible from Windows. To make a Linux server visible from Windows, you need to configure it so that you can map a drive to it as if it were a Windows server. There are a variety of ways to accomplish this.
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 Windows. 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.
In a terminal window on the OES server, become root by entering su - and the root password.
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.
Enter the following command to create the NCP volume on the OES Linux server:
ncpcon create volume volume_name /directory
Replace volume_name with a unique name for the location where you want to create the domain and/or post office directory structure
Replace directory with the directory referenced in Step 2 above.
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.
Enable cross-protocol locks so that Windows ConsoleOne can safely access GroupWise databases across the connection between Windows and Linux:
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
Restart the Novell eDirectory daemon:
rcndsd restart
Continue with Mapping a Windows Drive to the NCP Volume.
On the Windows server, right-click on the Windows taskbar, then click
.Select the drive letter to map to the NCP volume on the OES Linux server.
Specify the network path to the NCP volume in the following format:
\\linux_hostname\ncp_volume
Replace linux_hostname with the hostname of the OES Linux server.
Replace ncp_volume with the name of the NCP volume that you just created.
For the network user name, specify the fully qualified administrator user name for eDirectory., such as admin.users.novell.
Select
.Click
.(Conditional) If prompted, log in to eDirectory:
In the
, specify the eDirectory password for the administrator user.In the
field, specify the eDirectory context where the administrator User object is located.Click
.The mapped drive to the OES Linux server opens in Windows Explorer and can now be accessed from Windows ConsoleOne.
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.
In a terminal window on the OES Linux server, become root by entering su - and the root password.
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.
Continue with 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:
Start YaST.
Under
, click , then click .Under
, select , then click .Follow the prompts to install Novell Samba.
Continue with Logging In to iManager.
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.
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 .
Continue with Configuring the eDirectory Universal Password for Samba.
In iManager, click
.Click
.On the
tab, browse to and click the name of the administrator User object that you want to administer the Samba share, then click to add the user to the list.Click
to complete the process.Continue with Setting the eDirectory Universal Password for the Samba Administrator User.
Under
, click .Browse to and click the name of the Samba administrator User object, then click
.Specify the password for the Samba administrator user, retype the password for confirmation, then click
.Click
to close the menu.Continue with Creating a Samba Share.
Click
, then click .Browse to and click the name of the Server object where you are setting up the Samba share.
On the Identifying the Directory Structure for the Samba Share:
tab, create a new Samba share for the directory on the Linux server reference inClick
.Specify a unique name for the Samba share, such as gwsystem.
Specify the full path name on the Linux server for the domain or post office, click
to add the location to the list of Samba shares, then click .Click
to close the menu.Continue with Setting the eDirectory Rights for the Samba Share.
Click
, then click .Browse to and click the name of the Linux partition or directory where you created the new share, then click
.Click
.In the
field, browse to and click the name of the Samba administrator User object, then click .Grant all file system rights to the Samba administrator user, then click
.Continue with Testing Samba on the OES Server.
Double-click the Home Directory icon on the Linux desktop.
Click
In the Location field, type smb://user_name@ip_address
Replace user_name with the user name of the Samba administrator user.
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.
Continue with Mapping a Windows Drive to the Samba Share on the OES Linux Server.
In Windows Explorer, right-click the Computer object, then click
.In the
field, select the drive letter for the new Samba share.In the
field, specify the location of the Samba share in the following format:\\ip_address\share_name
Replace ip_address with the IP address of the Linux server.
Replace share_name with the name of the new Samba share.
Select
.Select
.Specify the Samba administrator user name and password, then click
.The Samba share for the OES Linux file system opens in Windows Explorer and can now be accessed from Windows ConsoleOne.
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.
In a terminal window on the OES server, become root by entering su - and the root password.
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.
Continue with Preparing Your Firewall to Allow Samba Connections.
In YaST, click
, then click .Click
, select , then click .Click
to view the summary, then click .Continue with Configuring the Samba Server.
In YaST, click
.Specify a workgroup or domain name, then click
.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.
Select
, then click .For use in your GroupWise system, the Samba server does not need to be a domain controller.
Under
, select .Because you prepared the firewall in Preparing Your Firewall to Allow Samba Connections, the firewall port for Samba is already open.
Click
to finish the basic configuration of the Samba server.Continue with Configuring the Samba Web Administration Tool (SWAT).
In YaST, click
.Select
.In the swat, then click .
list, selectSWAT is off by default. This turns it on.
Click
.Continue with Accessing SWAT.
Display SWAT in your Web browser with the following URL:
http://localhost:901
Specify the root user name and password, then click .
On the SWAT toolbar, click smbd and nmbd are running.
to verify thatIt is not necessary for winbindd to be running.
Continue with Creating a Samba Share.
On the SWAT toolbar, click
.In the gwsystem, then click .
field, type a unique name for the share, such asIn the Identifying the Directory Structure for the Samba Share.
field, specify the directory that you created inIn the
field, select .In the
field, select .Click
.On the Windows desktop, right-click the Computer object, then click
.In the
field, select the drive letter for the new Samba share.In the
field, specify the location of the Samba share in the following format:\\ip_address\share_name
Replace ip_address with the IP address of the Linux server.
Replace share_name with the name of the new Samba share.
Select
.Select
.Specify the Samba administrator user name and password, then click
.The Samba share on the SLES server opens in Windows Explorer and can now be accessed from Windows ConsoleOne.