*NWLink packages data to be compatible with client/server services on NetWare Networks.*IPX/SPX (Internetwork Packet Exchange/Sequenced Packet Exchange)
To configure the gateway, you can follow this simple procedure:
-Install the NWLink IPX/SPX/NetBIOS compatible protocol on each MetaFrame XP server that you want to use to access NetWare shares. -Install GSNW (Control Panel | Network | Install | Client | Add | Gateway (and Client) Services for NetWare). -Create a group on the NetWare server or in NDS called "NTGATEWAY." -Create a user account and grant it access to the resources that you would like to be available through the gateway. -Add the user account to the NTGATEWAY group. -Configure GSNW via the GSNW icon in the control panel. Click "Gateway" and check the "Enable Gateway" box. Add the name and password of the NDS or bindery account that you just created. -Specify a share name and drive letter that the MetaFrame XP users will use to access the NetWare drive. -Configure the maximum number of users, if you want. This number has nothing to do with licensing.
After GSNW is installed, the first time you log on to the server for connectivity to a NetWare 4.x server using NDS, you are prompted to specify a default tree and context for connecting to the NetWare server. If the NetWare server is running in bindery-emulation mode or is an earlier 2.x or 3.x server, you must specify a preferred server when you log on. You can also configure these settings using the GSNW utility in Control Panel. *NDS (
Gateway Service For NetWare
Joseph Njenga CIS-1-0187-1/2013
Seraphin Mwaura BIT-1-0553-2/2012
Jackson Nderitu CIS-0-0835-3/2013
Clifford Kimathi MAC-1-5896-3/2008
Dennis Waithaka BIT-1-1353-3/2011
Gateway Services for NetWare (GSNW) is a
Microsoft tool that allows you to permanently
map drives to NetWare volumes that are
available to all users on a server.
A gateway works by stripping the
incompatible protocol layers of an incoming
packet and replacing them with the
alternative headers needed for the packet to
reach its destination.
A server that has GSNW installed also must have
the NWLink protocol loaded. This protocol, which
is an IPX/SPX-Compatible Transport, makes it
possible for the Windows server to communicate
with the NetWare server. If it is not already
installed, NWLink will install automatically on the
server when you install GSNW.
The main function of NWLink is to act as a
transport protocol to route packets through
To prepare the NetWare server for the
gateway, you must create a group and a user
account as follows:
-Create a group called Students on the
NetWare server, and give it the necessary
rights for accessing the resources you want
to make available on the server.
-Create a user account on the NetWare server,
and give it the necessary rights for accessing
the resources you want to make available on
the server. Make this user account a member
of the Students group.
GSNW will use this user account for creating a
connection to the NetWare server. The
connection will appear on the server running
Windows NT or Windows 2000 as a redirected
drive that can be shared, as if it were a
resource located on the Windows-based
server. Windows clients can then connect to
the shared resource by browsing Network
Neighborhood, by mapping a drive using
Windows Explorer, or by using the net use
From the perspective of the Windows clients
on the network, the shared resources they
access appear to reside on the Windows-
based server. In actuality, the GSNW service
on the server is performing protocol
conversion between the Server Message Block
(SMB) protocol, which the Windows clients
understand, and the NetWare Core Protocol
(NCP), which the NetWare file server uses.
Below is a diagrammatic representation of the
Gate Service For Netware
Advantages of Gateway Services for NetWare
-Seamless access to NetWare data for your
-Users do not need NetWare accounts.
-No account password synchronization issues.
-You can configure different permissions on
the gateway, so that only some users are
permitted to access it. This is similar to
setting NTFS permissions on a local drive.
Disadvantages of Gateway Services for
- The performance of GSNW is less than stellar.
- From the NetWare standpoint, all users
access the gateway share via the same
- A server list is only obtained from the first
NetWare server that GSNW attaches to,
requiring proper SAP routing in your NetWare
environment to access all NetWare servers.
A service that can be installed on Microsoft
Windows NT Workstation computers to enable
them to directly connect to file and print
resources on Novell NetWare servers.
It supports both Bindery (database that
contains definitions for entities such as users,
groups, and workgroups) and NDS.
How It Works
CSNW is a full-featured, 32-bit client for NetWare
networks that can be installed on Windows NT
Workstation by using the Services tab of the Network
utility in Control Panel (or on Windows 2000
Professional by using the Network and Dial-up
Connections utility in Control Panel). If you are
connecting to a NetWare 3.12 or earlier server, you
must specify a preferred NetWare server for access to
its bindery. If you are connecting to NetWare 4,
specify the Novell Directory Services (NDS) tree and
default context. CSNW supports browsing NDS trees,
but does not support administration of NDS trees.
Additional options are included for printing and login
script support. CSNW requires installation of the
NWLink IPX/SPX-Compatible Transport protocol, but
if it is not installed already, it will be added
automatically when you install CSNW on a machine
-Client Service for NetWare allows for user-level security
-Client Service for NetWare allows you to establish user-
level security rather than share-level security. With Client
Service for NetWare, you can allow users access to
individual user home directories (directories where
individual user data resides) that are stored on a NetWare
volume. Users can then map to their home directory plus
any additional volumes to which they have been granted
user-level security. On the other hand, to allow users
access to individual home directories with Gateway Service
for NetWare, you would need to give each user a separate
-Client Service for NetWare might perform better than
Client Service for NetWare communicates directly with
NetWare servers, avoiding the potential bottleneck caused
by excessive traffic moving through a single network
-Client Service for NetWare requires you to
manage multiple user accounts for each user.
-Client Service for NetWare requires more
installation and management overhead.
- Client Service for NetWare requires you to
add IPX to your entire network.