CHAPTER 10
MAPI-BASED CLIENTS IN
A NOVELL NETWARE
ENVIRONMENT
The integration of Windows 2000 Server in a Novell NetWare-based environment introduces
several issues. You need to determine a common network protocol for both systems, for instance.
You will learn about configuring networking components such as the NWLink IPX/SPX-
compatible transport, Gateway services for NetWare (GSNW) and the SAP agent.
The Internetwork Packet Exchange/Sequenced Packet Exchange (IPX/SPX) protocol is
used when often in NetWare networks. The corresponding Windows impleme1 ntation is
known as the NWLink IPX/SPX Compatible Transport, often simply called IPX/SPX as well.
SPX, a part of the IPX/SPX protocol, is similar to TCP in that it provides a tranport-level
communication mechanism between computer systems, One of its tasks is data package
sequencing, which ensures that data move in chronological
order.
Outlook 2000 must contact the Information Store service using RPCs to provide you with
access to your server-based mailbox. This means that a communication interface for
NetWare workstations that allows use of IPX/SPX for RPC communication must exist.
To support workstations using IPX/SPX, you must install NWLink at the Windows 2000 level
on your Exchange 2000 server. You can accomplish this via the Properties of your Local Area
Connection.
=======================================================================
winexc10.html
PAGE 2
2002/06/12
By default, only TCP/IP is installed, but you can add the NWLink protocol in the Local Area
Connection Properties dialog box by clicking the Install button.
NOTE: It is not necessary to reboot the server to have the changes take effect.
Frame Types
In the Local Area Connection Properties dialog box, by selecting the NWLink IPX/SPX/NetBIOS
Compatible Transport Protocol and clicking the Properties button, you can manually specify
frame types for IPX/SPX.
By default, frame types are detected automatically; however if you experience communication
problems, disabling automatic frame type detection is a good idea.
The Frame type corresponds to the format of data packets sent through the network at the
data link layer, which is handled by Ethernet. Frame type is a factor for any network layer
protocol, but it is particularly important on NetWare networks because different versions
of NetWare support different frame types.
======================================================================
======================================================================
Ethernet II, 802.3, 802.2, SNAP Ethernet
Token Ring, SNAP Token Ring
802.2, SNAP FDDI
ArcNet-Frames ArcNet
======================================================================
The default frame type for NetWare 2.0 through 3.11 Ethernet networks is 802.3; later versions use
802.2. For token ring, as you might expect, the default is token ring and for Fiber Distributed Data
802.3. Interface or FDDI it is 802.2. If you are not sure which frame type your NetWare servers
802.4. are using, type config at the NetWare server’s system console, and check the Frame Type
802.5. settings for your network adapter.
Setting the Frame Network Number
When manually configuring frame types, you will also need to specify the corresponding external
network number with each frame type added. An external network number is an eight-digit
number known as the IPX network ID, which identifies every NetWare number. All resources
that belong to a particular NetWare network must use the same external network number.
=======================================================================
winexc10.html
PAGE 3 2002/06/12
NOTE: Windows 2000 typically detects the external network number automatically, but you
must adjust it manually if you use multiple frame types or network adapters.
The internal network number identifies every NetWare server and possibly every computer
running Windows 2000 Server. This number is frame type independent and must be unique
within your NetWare network. It must not be 0 if the Windows 2000 computer is supposed
to provide any services to NetWare clients or if it is used to route IPX in the network. In the
NWLink IPX/SPX/NetBIOS Compatible Transport Protocol Properties, use the Internal
Network number box to set this parameter.
As you can see on the LAN properties, NWLink NetBIOS is installed automatically with
IPX/SPX.
NetWare/IP is available with Novell NetWare 4.0 and later versions. However, NetWare/IP
uses a different IP implementation that cannot communicate with Microsoft’s TCP/IP stack.
It is advantageous to configure TCP/IP in your NetWare-based environment because TCP/IP
greatly simplifies the integration of Exchange 2000 Server.
Installing Gateway (and Client)
Service for NetWare
GSNW is an additional service that enables Windows 2000 Server to access resources on
NetWare servers. Installing GSNW allows you to access NetWare resources from the
Exchange 2000 Server.
=======================================================================
winexc10.html
PAGE 4
2002/06/12
Using the LAN Properties, you can install GSNW from the Windows 2000 Server installation
CD-ROM. Click the Install button, and select client. Click Add, and from the Select
Network Client Dialog box, select Gateway (and Client) Service for NetWare, then click
OK. This time, you must restart the Windows 2000 Server.
NOTE: Gateway (and Client) Services for NetWare requires NWLink and is not supported
in TCP/IP-only environments.
Communications between Windows 2000 Server (configured as a NetWare client by GSNW)
and Novell NetWare servers is accomplished through the NetWare Core Protocol (NCP).
The good news is Windows 2000 Server can act as a gateway to NetWare translating incoming
Microsoft client requests into the correct NetWare format and thus providing NetWare resources
to native Microsoft workstations.
NOTE: Windows 2000 Server connects to NetWare servers on behalf of a special NetWare
account that must be a member of a special NetWare group called NTGATEWAY. A Novell
NetWare administrator must create the account and the group on the NetWare server before
you can configure GSNW through the GSNW applet in the Control Panel.
File and Print Services for
NetWare
File and Print Services for NetWare (FPNW) allows users on NetWare workstations to access
files, printers, and applications on a Windows 2000 server. The machine running Windows 2000
Server acts just like a NetWare server.
Server Advertising Protocol Agent
To ensure that native NetWare workstations can locate a computer running Windows 2000
Server in a NetWare network, you must install the SAP Agent on the server in addition to the
GSNW. Support for SAP is required because NetWare clients rely on this protocol to perform
name resolution.
=======================================================================
winexc10.html
PAGE 5
2002/06/12
To install the SAP Agent on Windows 2000 Server, open the Network and Dial-up Connections
program from the Control Panel and display the properties of the LAN. Click Install and select
component type and select SAP Agent, and click OK. Because SAP Agent has not properties
to configure, you can close the LAN Properties box immediately. A server reboot is not necessary.
The SAP Agent itself does not announce a Windows 2000 Server to the NetWare network. This
the task of the GSNW. Using both components, the Windows 2000 Server computer advertises
itself across the IPX network using the SAP broadcast packet, which contains the server name
and the IPX internal network number.
When integrating Exchange 2000 Server into your Netware environment, you need to maintain
user account and mailbox information in an Active Directory forest in addition to the NetWare
directory.
Automatic logon allows you seamless access to network resources on the basis of a single
authentication when initially accessing the network. If you are working on a native NetWare
workstation, you will log on to NetWare first.
To support automatic logon, you need to keep the account information in both environments
the same. When you log on to your workstation running Windows 2000 Professional, you
supply your NetWare account information, which is cached by the operating system. Outlook
2000 can obtain this information and supply it to Exchange 2000 Server automatically, provided
that you are using the NT Password Authentication mechanism.
It is difficult to keep the NetWare and Windows 2000 account information synchronized
manually.
Fortunately, an automatic synchronization mechanism is available from Microsoft, known as
Microsoft Directory Synchronization Services (MSDSS).
=======================================================================
winexc10.html
PAGE 6
2002/06/12
MSDSS allows you to synchronize Active Directory accounts with accounts in NDS or
Bindery, including password information. However, password synchronization is only
supported from Active Directory to NDS (or Bindery) because access to encrypted
NetWare passwords is not provided. If you change your password later on in Active
Directory, MSDSS can transfer the password information into the NDS. See page 331.
IMPORTANT: MSDSS requires the Novell Client Software to be installed on Windows
2000 Server, which cannot coexist with GSNW. If you are using interoperability solutions
that require GSNW, consider installing and additional Windows 2000 domain controller for
Novell NetWare Client 5 and MSDSS.
MSDSS and the Connector to
Novell GroupWise
When integrating Exchange 2000 Server in an environment with NetWare and Novell GroupWise,
it is important to adjust the MSDSS configuration to avoid the synchronization of GroupWise
addresses (that are stored in NDS) with Active Directory.
The integration of Exchange 2000 Server into NetWare networks requires only a few
configuration steps on the NetWare workstations. Most of the steps achieve client
optimization rather than essential configuration.
Network Communications
Requirements
One of the following important NetWare communication components is the redirector,
which allows the client to communicate with NetWare servers using NCP. On a computer
running MS-DOS or Microsoft Windows 3.1 or later, you must load a component called
NETX.EXE or a Virtual Loadable Module (VLM) redirector.
If you are using Microsoft Windows 95/98, Windows NT Workstation, or Windows 2000
Professional, you can install the Microsoft Client Services software, which provides the full
set of NetWare functionality including contextless logon.
=======================================================================
winexc10.html
PAGE 7
2002/06/12
Communicating with an Exchange
2000 Server Computer
Outlook 2000 can communicate with an Exchange 2000 server in an IPX/SPX-based
NetWare network using RPCs over SPX. However, TCP/IP can be used instead if your
Novell NetWare 5 environment supports it.
NOTE: RPC over SPX uses the Winsock interface and does not require a NetWare
redirector. You do not have to configure the Exchange 2000 Server computer as a
NetWare server using FPNW.
Every user who wants to access a mailbox or any other resource on a computer running
Exchange 2000 Server must be validated. Outlook 2000 running on Windows 2000
Professional will automatically use the supplied account information used to log on to
NetWare. Only when the NetWare account information does not match the Windows
2000 account are you asked for your account, domain, and password.
Novell NetWare Client
If you have installed the Novell NetWare Client software on your workstation, make
sure your computer is a member of your Windows 2000 domain; otherwise the
automatic logon to Exchange 2000 will fail.
Client Connectivity Issues and
the RPCPing Utility
Implementing an Exchange 2000 server in a Netware network means managing two
different and complex network operating systems.
RPCPing is a program family rather than a single utility, which allows examining the
RPC-based client/server communication. All parts of RPCPing come with the
Exchange 2000 Server installation CD-ROM. The programs can be found in the
\Support\Rpcping
directory.
The server component has been implemented in a file called RPINGS.EXE. It must be
started on the server before the client component can be used to measure the quality of
the connectivity.
=======================================================================
winexc10.html
PAGE 8
2002/06/12
You can run RPINGS.EXE without any command-line options, but
additional parameters may be used to restrict the RPC test to specific protocol sequences.
The following options can be set:
· p ipx/spx
· p namedpipes
· p netbios
· p tcpip
· p vines
To exit the server component, you need to enter the string @q at the RPINGS.EXE
command prompt.
The client component is dependent on the operating system. A separate version exists
for MS-DOS, Windows 3.1 and later, and Windows 95/Windows NT/Windows 2000.
Typically, you use RPINGC32.EXE to test RPC connectivity. This is a 32-bit Windows
program that displays the connection status, available protocol sequences, endpoints, and
the quality of the RPC connection as you attempt to check the RPC connection.
The following are required RPCPing
client parameters:
The name of the computer running Exchange 2000 Server (or the IP address).
The protocol sequence, which specifies the RPC mechanism that will be used such as named
pipes (default).
The endpoints, which specify a protocol-specific port, that will be used by the RPCPing client
to communicate with the server. This endpoint can be the Information Store (Store), the
Directory Service (Admin), or the RPCPing server (Rping).