Services for the Novell NetWare Operating System

Services for NetWare (SFN) are compatible with Novell® NetWare® Bindery service for authentication and file access using the internetwork packet exchange/sequenced packet exchange (IPX/SPX) network protocol. Services for NetWare are disabled by default.

For information about enabling SFN, see the file install.rtf, which is located in the c:\sfn directory of your NAS system.

NOTE: SFN is not installed by default.

Sharing Netware Volumes

To add Netware volume shares on Windows Storage Server 2003, perform the following steps:

1.From a Remote Desktop session, click Start, point to Programs→ Administrative Tools, and click Server Manager.

2.In the Server Manager, click the FPNW menu, and then click Shared Volumes.

3.Click Create Volume.

4.In the Create Volume window, specify the volume name and path to share, and click OK. NOTE: The specified volume must have been created earlier.

5.Click Close.

NOTE: You cannot use the NAS Manager to manage NetWare shares.

Viewing Netware System Properties

To view Netware system properties on Windows Storage Server 2003, perform the following steps:

1.From a Remote Desktop session, click Start, point to Programs→ Administrative Tools, and click Server Manager.

2.In Server Manager, click the FPNW menu, and then click Properties

Configuring the NWLink IPX/SPX Compatible Protocol

To configure this protocol, you need the internal network number, frame type, and network number.

Internal Network Number

Internal network numbers are used for internal routing and are generally needed only for servers. You should not need to change this option on your system.

Frame Type and Network Number

Frame types define the packet formats that are used by different networks. All systems in a network must have the same frame type so that they can communicate with the rest of the network.

When you are configuring your system, it attempts to automatically detect the frame type for the client. In most cases, this is successful. However, the automatic detection feature occasionally selects an inappropriate frame type, usually because more than one frame type exists on the network. If this happens, you should manually set the frame type to match the one specified on the server running NetWare.

NOTE: If more than one frame type exists, select the one that is detected first. For example, if the frame types Ethernet 802.2 and Ethernet 802.3 are bound to the same segment, configure frame type Ethernet 802.2. The order of detection is Ethernet 802.2, Ethernet 802.3, Ethernet II, and then