# Windows NT Server 4.0 Notes
Module 14: Interoperating with Novell Netware Review Intro: The software included in NT includes: NWLink: NWLink enable computers running NT to communicate with NetWare servers and clients. NWLink is included in both NTS and NTW. CSNW: CSNW enables computers running NTW to make direct connections to file and printer resources at NetWare servers. Furthermore, CSNW supports NDS which provides NT clients with the ability to browse resources, use authentication, and use printing services on NDS hierarchies GSNW: GSNW enables computers running NTS and NWLink to both directly access files and printers at NetWare servers, and create gateways to NetWare resources for Windows clients FPNW: FPNW enables NetWare clients to access file, print, and application resources on computers running NTS. DSMN: DSMN copies NetWare user and group account information to NTS and then incrementally propagates any account changes back to NetWare servers. Migration Tool for NetWare: Migration Tool for NetWare enables transfer of user and group accounts, volumes, folders and files from a NetWare server to a computer running NTS. Some Background Primarily, NetWare is used for file and print services, with user accounts and privileges stored in the NetWare bindery. Bindery is the NetWare 3.x equivalent of the Windows NT directory database. In NetWare 4.x, the NDS tree is used. Microsoft Windows NT Server and Workstation provide several features and services that enable computers running Windows NT to coexist and interoperate with NetWare servers. Some are included in Windows NT, while others are available as separate products, called add-ons. First the basic Novell protocol must be present to do anything : ### NWLink NWLink is a native 32-bit NT implementation of IPX/SPX and supports application servers in a NetWare environment. It is a TRANSPORT protocol. By itself it doesn't allow access to NetWare File and Print resources (or vice versa). It does provide a method of transporting data to the NetWare server. NWLink allows computers running NT to communicate with other computers running NT as well as with NetWare servers. Two networking APIs are supported to allow these communications. Windows Sockets: This interface supports existing NetWare applications written to comply with the NetWare IPX/SPX interface. NetBIOS: This interface supports sending and receiving Novell NetBIOS packets between a computer running Novell NetWare and Novell NetBIOS, and a computer running NT and NWLink NetBIOS.
Client Service for NetWare (CSNW)
What's it for? Enables NT Workstations to make direct connections to file and print resources at NetWare servers running NetWare 2.x, 3.x or 4.x REMEMBER CSNW IS ONLY AVAILABLE ON NT Workstation Supports NetWare 4.x servers running either NDS or bindery emulation.
Note
NT will attach through the bindery emulation by default, so if you want an NT Workstation to see the NDS tree, you must disable bindery emulation on the NetWare file server with the following NetWare console command: SET BINDERY CONTEXT = ""
Login script is also included. Is implementation provided by Microsoft for NetWare redirector it also supports NetWare MS-DOS console applications like SYSCON and other console programs. ### In order to use CSNW to access NetWare resources, these conditions must be met: To access the directory, you must have a valid user account with appropriate permissions on the NetWare file server Your logon account and password on the NT side must match the logon account and password on the NetWare side NWLink IPX/SPX must be running on NT Workstation CSNW must be running on NT Workstation (the user can connect to desired resources through Network Neighbourhood or the NET USE command utility.) ### CSNW CSNW enables computer running NTW to make direct connections to file and printer resources at NetWare servers running NetWare 2.x or later. NT computer with CSNW and NWLink will support NCP (NetWare Core Protocol). NCP is a file and printer sharing protocol similar to Microsoft SMB (server message blocks). LIP (Large Internet Protocol). LIP determines and uses the largest allowable frame size when communicating with a server across a router. LFN (Long File Name). LFN can be used when the NetWare server is running OS/2 Name Space. CSNW Support for NDS. NDS (NetWare Directory Services) organizes shared objects on participating NetWare Servers into a hierarchical tree. Thus, installing CSNW on NT provides NT clients with the ability to browse resources, use authentication, and use printing services on NDS hierarchies. Note : Although NT 4.0 supports NDS, they do not support administration of NDS trees. CSNW Support for Bindery Emulation. CSNW supports the bindery-based version 3.x of Novell NetWare. User accounts and privileges are stored in the NetWare bindery, which is Novell's equivalent of the NT directory database. Access to the network is validated based on user accounts and Pwd in NT domain through the directory database, or on a Novell NetWare server through the bindery.
NOTE:
You can use Preferred Server OR Default Tree and Context - not both. Use Preferred Server if connecting to a NetWare 3.x server; use Default Tree and Context when connecting to a NetWare 4.x server. You CAN use the Preferred Server setting to connect to a NetWare 4.x server running in bindery emulation mode, but you won't be able to browse the NDS tree.
NOTE:
Compare using CSNW on NT Workstation to connect to a NetWare server AND connecting through NT Server which is running GSNW. CSNW on NT Workstation: will be faster because it's a direct connection to the NetWare server Through NT Server running GSNW: no CSNW is needed on the client. This is the only option for MS-DOS and Win95 clients. The question to answer before deciding is how much access do you need? If a lot, then NT Workstation with CSNW If only occasional or the client isn't NT Workstation, then NT Server with GSNW
Gateway Services for Netware (GSNW)
Some Background:
Generically speaking, the term “gateway” refers to a software component permitting computers that do not share a common set of protocols and services to communicate with one another. In other words, the gateway translates from one protocol and service world to another, and vice versa.
REMEMBER, GSNW can only be implemented on NT SERVER! What's it for? Enables computers running Windows NT Server, and using NWLink to access files and printers on NetWare servers. When you install GSNW on an NT Server, it also automatically installs CSNW.
So you need...
Protocol | NWLink
Service | CSNW
Service | GSNW
To provide a gateway for computers running only Microsoft client software to gain access to NetWare resources. These MS client computers don't need the NetWare requester they don't need CSNW OR even an IPX/SPX protocol running on them to access the NetWare resources. The GATEWAY takes care of that for them so that they have access to the resources through the GATEWAY. Using GSNW, NT Server connects to a NetWare file server's directory, and then shares it, as if it was a directory on Windows NT Server computer. Microsoft Picture:
When to use GSNW
It is designed to provide Windows clients with occasional access to a NetWare network. Serve as a migration path (example NetWare à NT) It's not designed to allow Windows NT Server computer to be a high performance gateway because ALL clients are receiving services through one NetWare connection. RAS clients can use GSNW to access NetWare servers. Using GSNW, business can use NTS as a communications server and enable remote users to have reliable and secure remote access to a NetWare local area network.
Remember this:
The chief selling point for GSNW is that it provides access to NetWare resources for MS Network clients without requiring any additional software, or software changes, to be made to those clients themselves.
Installing GSNW
Installing GSNW to create a NetWare Gateway requires six steps: Remove any existing NetWare client software from the Windows NT server before you start Here's why: Because CSNW is installed and very much part of GSNW, this means that any Windows NT server with GSNW installed also can function as a client to a NetWare server. This explains why you must remove existing NetWare client soft-ware— especially Novell’s NetWare Client for Windows NT—from any Windows NT server before installing GSNW on that machine. Install GSNW on a Windows NT Server (NWLink is installed too if not present; CSNW is installed too) Create a Group account called NTGATEWAY on the NetWare server or NDS tree and make sure the group account set up on NetWare server must have necessary permissions assigned for resources to be accessed Create a User account on the NetWare server using SysCon, NWAdmin or NetAdmin and make the user a member of the NTGATEWAY group. Windows NT will use this account to login to the NetWare server or NetWare tree. Configure GSNW to attach to that preferred server (NetWare 3.x) or default tree and context (NetWare 4.x) Add the server or tree shared resources to the GSNW service (Using Gateway button) and then Add in the Configure Gateway dialog box.)
Note: Like CSNW, GSNW can also support NDS and bindery-based 3.x version of NetWare
Another note:
If you want to support NT long filenames on the NetWare file server, you must have OS/2 name space on the NetWare volumes that will store long file names if you have NetWare 4.11, then use Long Name Space Otherwise, you must use DOS FAT 8.3 naming conventions.
File and Print Services for NetWare (=add-on)
What's it for? To integrate NetWare clients into Windows NT network and allow them to gain direct access to resources on Windows NT Server computers. It functions as a NetWare 3.12 compatible file and print server. No change in NetWare client side software is needed. AND SMB (Server Message Block) support doesn't have to be added to each NetWare client. Not included with Windows NT. Can be added to an existing application server to maximize usage of hardware resources.
Directory Service Manager for NetWare (=add-on)
What's it for? Extends Windows NT Server directory service features to NetWare servers. It Allows management of mixed Windows NT and NetWare 2.x, 3.x and 4.x (in bindery emulation) environments with Windows NT Directory Services. Copies NetWare user and group information to PDC and incrementally reproduces any account changes back to NetWare servers. If NT users are added, this info is copied to the NetWare server. Windows NT add-on utility. It allows NetWare clients to have a single network login for by synchronizing accounts across all NetWare servers. DSMN can be used to copy ALL NetWare user accounts to a specified domain. This allows all accounts in the domain to be managed from User Manager for Domains. Use DSMN to accomplish these tasks: Specify which NetWare user and group accounts to manage centrally from Windows NT Server computer. Those are copied to PDC and become NT Server accounts. They are bound by the account policy of the NT Server domain Merge account names from multiple NetWare servers into one account name when adding them to the domain. E.g., DavidS and DavidSm could become DavidS. Specify which Windows NT Server domain accounts to copy back to NetWare servers. This ensures that changes made to domain accounts are synchronized with NetWare server.
Migration Tool for NetWare (Nwconv.exe)
> What's it for? Enables easy transfer of user and group accounts files and directories from a NetWare server to a Windows NT Server computer. If destination server runs FPNW, login scripts can also be migrated
> NOTE: a migration leaves the NetWare server intact and only copies the information to the NT Server
It provides a Windows NT Server computer to perform functions: Preserve appropriate user account information, including NetWare specific information, such as logins and station restrictions. Preserve login scripts with the user account; Windows NT supports NetWare login script. Control how user and group names are transferred Set passwords for transferred accounts Control how account restrictions and administrative rights are transferred Create a volume for NetWare users Select directories and files to transfer and select destination Preserve effective rights on directories and files
Now, Migration Tool for NetWare in DETAIL...
Migration Tool for NetWare is used to migrate NetWare users, groups, selected files and directories, and rights on files and directories (security) to Windows NT domains. Migration tool for NetWare will not migrate: User passwords Logon Scripts Print server and Print Queue information Workgroup and User Account Managers for NetWare. (not often used) Leaves the NetWare server intact. It only copies information to the NT server. Can migrate several NetWare file servers to a single NT domain controller or member server. Prerequisites for using NWCONV.EXE : There may be a question on what components you need to perform a Migration from NetWare --> NT These are the top three, but don't ignore the rest. Must be running GSNW (Gateway Services for NetWare) on the NT server. Must have CSNW running (which is installed with GSNW) Must be running NWLink protocol on the NT server. If you are transferring users and/or groups, the NT server must be a PDC If you are transferring directory and file information, the NT server can also be a member server or a domain controller. Must have supervisory rights (Netware 2.x or 3.x) or Admin rights (NetWare 4.x) on the NetWare server. Must have the be in BINDERY EMULATION on the NetWare server. Must be a member of DOMAIN ADMINS on the NT server. ## The destination drive on the NT server must be NTFS to successfully migrate file and directory security information from the NetWare server. Migration Tool for NetWare Is accessed from the command line (NWCONV.EXE) It is located in the \WINNT\system32 folder The main Migration Tool for NetWare screen. Press the ADD button and you get this Select Servers for Migration dialog box: The User and Group dialog box allows you to customize how users and groups will be transferred. Click User Options on the Main screen to access User and Group Options: The default setting is to migrate all users and groups. Let's go through all the tabs here to review the options and DEFAULT for each: ### 1. Password migration (Click on the Passwords tab see above) Migration tool for NetWare cannot read NetWare passwords AND won't transfer them By default, migrated user accounts will have no passwords. The following options are available: No Password (DEFAULT)- User will have no password. Password is Username Password is - Will let you select a password for all migrated user accounts. There is also a checkbox for "User must change password at next logon." None of this is very secure, so you can use a mapping file to specify passwords - see the Use Mappings File below. 2. Duplicate user names (Click on the Usernames tab) By default, users with duplicate user names will not migrate. The following options are available: Log Error (DEFAULT) - Do not migrate user accounts with duplicate names and log it as an error. Ignore - Take no action when conflicting user names are encounterd. Overwrite with new Info - Replace existing NT account information with NetWare account information. Add Prefix - Will allow you to choose a prefix and add it to the user name. For example, if two users names are "gwilson", the NetWare account would become Nwgwilson if "NW" was the prefix you specified. ### 3. Duplicate group names (Click on the Group names tab) By default, duplicate group names will be ignored and will not migrate. The following options are available: Log Error - logs an error and does not migrate the group. Ignore (DEFAULT) - Does not migrate the group or log an error. Add Prefix - Will allow you to choose a prefix to be added to the duplicate group name. Same as user names: if NW is prefix, then SALES from the NetWare server would become NWSALES. 4. Account restrictions (policies and profiles) (Click on the Defaults tab) this tab specifies how the default account restrictions will be handled By default, migrated user accounts will retain their NetWare account restrictions (password length, logon hours, etc.). The following options are available: Use supervisor defaults (DEFAULT) - Migrates NetWare user account restrictions. Add Supervisors to the administrators group - Will add NetWare user accounts with administrative rights on the NetWare side to the DOMAIN ADMINS Global Group on the NT PDC. Default is that they are NOT added to the Domain Admins Global Group and their administrative rights are lost. 5. User account mapping file (Click on the "User Mappings in file check box") Allows you to specify what the migrated user account names and password will be on the NT Server and what NetWare group names will be used on the NT Server. It is of the format: [users] # OldNetWareName, NewNTName, NewNTPassword [groups] # OldNetWareGroupName, NewNTGroupName ### 6. Configuring File Options for Migration This section allows you to specify how the NetWare volumes, directories and files will be transferred. Click on File Options button on Migration Tool for NetWare By default, files are not migrated. If the "Transfer files" box is checked, the following NetWare files are not migrated by default: \SYSTEM - NetWare operating system files \LOGIN - NetWare login environment files \ETC - NetWare TCP/IP files Files having the NetWare attributes of hidden and/or system By default, the NetWare files to be transferred are the root volumes. By Default, the destination drive is the NTFS partition with the most free space. To change this, click the Modify button Enter the information for the new locations By Default, the NetWare volume SYS is shared with the share name SYS. To change this, click on New Share: ####
NOTE:
If you choose to migrate to a FAT partition, the NetWare file permissions will not migrate
Clicking Files allows you to specify which files to transfer: Remember that ETC, LOGIN and SYSTEM are not selected by default. 7. Trial migration and error logging When you are ready to perform the migration, Migration Tool for NetWare will allow you to perform a trial migration. This will give you a chance to correct errors and will not actually write data. Logfile.log will always log all errors. The following error logging options are also available: Pop up on errors - pops up a message when an error is encountered. Verbose user/group logging - More complete information about user and group migration is added to logfile.log. Verbose file logging - More complete information about file migration is added to logfile.log.
Remote Administration of Novel Networks
Novell NetWare servers cannot be administered directly; instead, a NetWare client acts as the system console and controls the administration of the NetWare server. A computer running NT with GSNW or CSNW enabled can also act as a system console to administer the NetWare servers using the NetWare administrative utilities, such as SysCon, Rconsole, Pconsole. SysCon is the primary administration tool and is used to setup user accounts, define policies and grant user access permissions to the NetWare network. Rconsole provides a remote view of the NetWare system console. The console functions can be performed on the remote console. Pconsole provides the administrator with the tools necessary to manage print servers. Multiple session of the administration tools can be run on a single NT client. This allows you administer multiple NetWare servers. For a NetWare client to access and administer a NTS, FPNW must be installed on the computer running NTS. Once FPNW is installed and configured, a NetWare client can sign on to the computer running NTS and perform administration tasks.
Interoperability with NetWare
Connections over NWLink can be made via Remote Procedure Calls Windows Sockets NWLink NetBIOS NWLink provides client/server application support for IPX-based applications, but by itself does not support access to file and print resources. If NT client requires connections to file and print resources on a NetWare server, CSNW must be installed on NT client. If there are computers on the network that are not running NWLink or another IPX/SPX transport, you can create a gateway for these computers on a computer running NTS by installing can configuring GSNW. If a Novell NetWare client requires file and print access to a computer running NT, FPNW must be installed on that computer running NT.
Platform | Running | Can Connect To
Application | NetWare client | IPX with NetBIOS, Named Pipes, or Windows Sockets support | NT-based computers with NWLink, running IPX applications such as MS SQL server
NT-based computer | NWLink | Client/server applications running on NetWare server
Client/server | NT-based computer | NWLink and CSNW or NWLink and GSNW | Novell NetWare servers for file and print services
NetWare Client | IPX | NTS with NWLink and FPNW installed for file and print services.
Installing and Configuring CSNW
First remove any NetWare redirectors (such as Netware Services for Windows NT) in services tab of Network program (also for installing GSNW). Install through Services tab of Network program; When you restart this dialog box will appear: CSNW icon appears in Control Panel. Double-click it to configure CSNW. Client Service for NetWare dialog box:
Option | Use this option to
Preferred Server | If your network used Bindery emulation use preferred server Computer connects by default to this server and it has information about available resources on NetWare network. If not defined, the name of NetWare server that is connected by default appears in Current Preferred Server.
Default Tree | If network uses NDS enter or change default NDS tree. Default tree defines NDS name of the user name that is used to log in. All resources in default tree can be accesses
Default Context | Enter default context, or position, of user name that is used for login
Print Options: Add Form Feed | Notify printer to eject page after printing document
Print Options: Notify When Printed | Receives notification
Print Options: Print Banner | Notify printer to print banner page before printing document
Run Login Script | Login script is run when user logs in to NetWare server or DNS tree
Overview | Display Help topics for CSNW
BTW, What is NDS? NDS is a global, distributed database that maintains information about every resource on the network in a hierarchical structure (including users, groups, printers, volumes).
Installing and Configuring GSNW
Install through Services tab of Network program; after restarting, the Select NetWare Logon dialog box appears. It prompts the user to select a preferred server. If the network uses NDS click Default Tree and Context. the GSNW icon appears in Control Panel after installation, click it to configure GSNW. The Gateway Service for NetWare dialog box appears. It is the same as CSNW dialog box except that it has an extra button: Gateway. This dialog box is used to enable the gateway to enter the user account and password of the member of the NTGATEWAY group. to share NetWare volumes and directories to set permissions for the gateway. Click the Gateway button and the Configure Gateway dialog box appears.
Option | Use this option to
Enable Gateway | Enable gateway on this server
Gateway Account | Enter user name for gateway account; must exist and must be member of NTGATEWAY group on all NetWare servers to which this server will have gateways
Password | Password for gateway account
Confirm Password | Retype gateway password
Share name | List existing gateways to NetWare resources on the server
Add | Create gateways to additional NetWare volumes or directories à New Share dialog box: Share Name à (MS-DOS client up to 8 others 12 characters) will be used to connect to the shared directory from clients running Microsoft operating systems. Network Path à type path to NetWare volume, including name of Netware Server and volume
Remove | Disconnect clients and stop sharing selected NetWare file resources; warn users
Permissions | Set permissions to control user access to a gateway. The default permission is Full Control for Everyone.
When you click on Add... this is the dialog box that appears to let you define new shares
Sharing NetWare Printers
Setting up a gateway to NetWare printers (called "print queues" in NetWare terminology) is done through Printers settings. HOW?: First you set up a "Gateway" using GSNW, Then Add a Printer just as you would in NT. Then share the printer.
NOTE: The printer management occurs on the NT Server when printing through the gateway, NOT on the NetWare server. The NetWare server still controls the use of the NetWare clients' printer, of course.
Troubleshooting
In general these are the steps to go through when you have a NT client attached to a NetWare server PROBLEM: As a Microsoft client, you have a problem attaching to a NetWare server. Go thru these steps: is the NetWare server working normally with the NetWare clients? (if yes, then the problem isn't there) the problem is probably with the workstation. Can the NT workstation attach to a Microsoft Windows Network Resource? make sure that CSNW and NWLink are installed make sure the <Preferred Server> or the Tree and Context settings are correct. make sure the frame types and network numbers match between the NetWare Server adapter and the NWLink settings on the NT Workstation.
NOTE:
an internal network number is used to uniquely identify NetWare file servers. This option is left at the default "00000000 " unless you are: using File and Print Services for NetWare using IPX routing.
Other Problems: You have established a gateway on a computer running NTS to a NetWare volume. You have assigned full control permissions to your Domain Users group, and yet your users are complaining that they cannot save files to a directory through the gateway. Why? The NTGATEWAY group on the NetWare server has not been assigned the appropriate level of rights on the NetWare server. The gateway cannot grant greater permissions than the NetWare rights allow. A NetWare client needs to access a NT printer server. What software needs to be installed on NetWare client and print server? Nothing needs to be added to NetWare client. You need to install NWLink and FPNW on fNetprint server. Q. How can I disable the print separator page when printing to a NetWare print server? A. If you are using the client services for NetWare, CSNW, then upon installation a new control panel applet would have been created which allows the configuration of all things NetWare. 1.Start the CSNW control panel applet (Start - Settings - Control Panel - CSNW) 2.Under "Print Options" uncheck the "Print Banner" option box and click OK Banners will no longer be printed. You will also notice that options such as notifies and form feeds can also be configured.
Extras
Q. What are the NT equivalents of NetWare Rights? A. The table below outlines the NetWare rights and the NT equivalents:
NetWare | Windows NT
Supervisor (S) | Full Control (All)
Read (R) | Read (RX)
Write (W) | Change (RWXD)
Erase (E) | Change (RWXD)
Modify (M) | Change (RWXD)
Create (C) | Add (WX)
File Scan (F) | List (RX)
Access Control (A) | Change Permissions (P)
Changing the order of the redirectors on the server This is only partly a NetWare issue. You have a client connected to both Microsoft and NetWare networks so you have more than one redirector working. DID YOU KNOW?... Redirectors are searched in the order they are shown in the Services Settings tab of the Network applet in Control Panel. You can change the order by using the Network Access Order button below the Services list box. You can choose the Microsoft Windows Network to search for resource there first, or NetWare network. Choose the one you use the most.
Frames Types
You'll see one, or possibly two, questions on the test referring to problems communicating on a network, or requiring an under-standing of NWLink’s ability to detect automatically 802.2 IPX frame types on a Windows NT Server machine. Here’s what you need to know to deal with such questions: Although NWLink is provided primarily for NetWare access and interoperability, Windows NT-based networks can use only NWLink, where no NetWare is present. Don't be sur-prised if this shows up on a test question! Until NetWare 3.12 shipped, NetWare’s default frame type was raw 802.3, which Microsoft calls simply “802.3 frame type.” For NetWare 3.12 and all 4.x versions (including IntranetWare), the default frame type uses 802.2 headers, atop the native frame type for the network technology in use. Microsoft calls this the “802.2 frame type,” without regard to technology. The total battery of frame types you’re most likely to encounter is: 802.2 frame type (industry standard, default for NetWare 3.12 and higher-numbered versions) 802.3 frame type (so-called “raw 802.3 header” format, developed by Novell, default for older, pre-3.12 versions of NetWare) 802.3 with SNAP header (sometimes called “Ethernet_SNAP frame type” in Microsoft terminology) 802.5 frame type (the native format for Token Ring networks) 802.5 frame type with SNAP header (sometimes called “Token_Ring_SNAP” in Microsoft terminology) (Note: SNAP stands for SubNetwork Access Protocol, and provides a mechanism that permits nonstandard higher-level protocols to appear within a standard IEEE logical link control frame like the frame types previously mentioned. It's often used to transport AppleTalk or SNA in IP network environ-ments. It's not necessary to understand the subtleties of this technology for this MCSE test, however.) If any workstation (or server) is configured for an incorrect IPX frame type (that doesn't match the rest of the popula-tion), an improperly configured machine will not be able to interact with the network. This can occur even though the network may otherwise work properly, and all other machines may communicate successfully. Although Windows NT Server 4 can detect 802.2 frame types automatically, it cannot detect any other type of IPX frame automatically. This means that on networks where versions of NetWare older than 3.12 occur, manual frame type detection must be chosen when configuring NWLink. It also means that the IPX network numbers to which the Windows NT Server is attached and all IPX frame types in use must be identified explicitly as part of NWLink configuration. For client/server applications like SQL Server database access, or NetBIOS-based applications, native NetWare clients using IPX/SPX can communicate directly with a Windows NT server running such an application without requiring anything other than NWLink and the server side of the application to be installed on that machine. In essence, the client side of the client/server application supplies everything the clients and server need to communicate, as long as they have a protocol in common. Because the assumption is that native NetWare clients use IPX/SPX, a Windows NT server must install NWLink to communicate with such clients across the network.
And now the procedure for Installing, Configuring and Enabling GSNW in detail...again....
Here’s a high-level overview of the GSNW installation process, emphas-izing those elements and information that must be supplied during installation that are most likely to appear in GSNW-related test questions: 1. Before installing and configuring GSNW you must create the following accounts on the NetWare server where the gateway will connect: a. A user account on the NetWare server with rights to the NetWare file system directories that gateway users from the NT side will need. b. A group account named NTGATEWAY on the NetWare server with rights to all file and print resources that gateway users will need. [Note: All users who go through a single GSNW gateway have the same access and the same rights to the NetWare resources; the only way to create different collections of access and rights is to set up multiple gateways (only one instance of GSNW per individual Windows NT server is permitted).] 2. To install GSNW, you must log in to the Windows NT server as an Administrator. In the Network applet in Control Panel, select the Services tab, click the Add button, and select Gateway (and Client) Services For NetWare. Supply the NT Server CD or point to a copy of the \i386 directory where the necessary source code files reside. The software will more or less install itself. 3. To configure GSNW, double-click on the GSNW icon in Control Panel. The Gateway Service For NetWare dialog box appears. a. Click on the Gateway button, to elicit the Config-ure Gateway dialog box. b. Check the Enable Gateway box to enable the Gateway Service. c. In the Gateway Account field, enter the NetWare user name you created in Step 1a. Enter the Password into the Password field, then confirm that password in the Confirm Password field. d. Click the Add button to create a NetWare share for use by Microsoft networking clients. A New Share dialog box appears. e. In the Share Name field, enter a name through which the NetWare directory will be shared. f. In the Network Path field, enter a UNC name for the NetWare directory that's being shared. For the SYS:Public directory on a server named NETONE, the syntax is \\NETONE\SYS\ PUBLIC. g. In the Comment field, you can add an optional descriptive phrase that will appear in the Browse window for MS Clients on the network. h. In the Use Drive field, select a drive letter on the Windows NT server to be assigned to the NetWare directory. This drive letter remains taken as long as GSNW runs on the Windows NT server; by default, Z is the letter assigned to the first such share name. i. The User Limit box permits administrators to limit the number of users who can access the NetWare share simultaneously. Because the gateway bogs down under increasing load, it’s a good idea to limit the number of users to 10 or so (unless the server is extremely fast or only lightly loaded). j. Click OK to save all changes. You'll return to the Configure Gateway dialog box. Click OK again to exit the Gateway Service for NetWare dialog box. All changes will take effect upon the next system logon. 4 . The only way to create NetWare shares is through the interface described in Steps 3d through 3j (not through Explorer or My Computer, as is the case for normal Windows NT Server shares). Likewise, you must use the GSNW applet in Control Panel to set permissions for NetWare shares. Here’s how: a. From an administrative logon, launch the GSNW applet from Control Panel. b. When the Gateway Service For NetWare dialog box appears, choose the Gateway button. c. In the Configure Gateway dialog box that appears, highlight the NetWare share name and choose the Permissions button. Use this interface to set permissions for the NetWare share. 5. Using NetWare Print Resources through the Gateway requires none of the shenanigans needed to establish and set permissions for the NetWare shares. Instead, configure NetWare print queues through the Printers icon in Control Panel (as with any other Windows NT server-attached printer). Here’s what's involved: a. From an administrative logon, launch the Printers applet. Select the Add Printer icon. This will display the Add Printer Wizard window. b. Select the Network Printer radio button, then click the Next button. This brings up the Connect to Printer dialog box. c. In this dialog box, you will see two icons—one labeled “NetWare Or Compatible Network” and the other labeled “Microsoft Windows Network.” You can expand and navigate this directory tree the same way you would the Microsoft Windows Network tree: Double-click Network, select a server, then double-click and select the printer you wish to manage. Otherwise, the procedure is exactly the same as install-ing an ordinary Windows NT network printer. Remember that it is necessary to map a drive on the Windows NT server for the NetWare share, and that NetWare shares and their permissions only can be managed through the GSNW applet, not through ordinary file management tools. NetWare printers, on the other hand, can be handled like any other network printers through the Printers applet, once GSNW has been installed on a Windows NT server. Another guy's Essential notes for the NetWare section of the Enterprise exam: Chapter 9 Netware Connectivity NWLink is a default protocol in NT 4.0 Server, install automatically with GSNW Four Frame Types- Ethernet_II, Ethernet_802.2, Ethenet_802.3, Ethenet_SNAP NT Auto-detect will use 802.2 industry standard if available CSNW (workstation only) is a NetWare redirector MS client access to NetWare res. CSNW adds an icon to Control Panel to configure (automatic upon first logon) Set Preferred Server (3.12) or Default Tree, Context (NDS) also Print & Script Options Optional ($) File & Print Svcs for NetWare gives Netware clients access to MS resources GSNW- one NT Server provides access to NetWare file & Print Svcs for all MS clients NT Server does NOT support CSNW, must use GSNW, no client sw required " " " Must have NWLink running, Dom Admin & Supervisor rights, Group NTGATEWAY, and user on Netware, same user and pw on NT with access users need Have NetWare 3.x OS/2 name space on Vol if long filename support is desired. GSNW dialog like CSNW plus Gateway button (opens Configure Gateway dialog) Migration Tool for NetWare (not upgrade, requires 2 machines) \winnt\system32\NWCONV.EXE User Accts (no pw), Groups, selected Dirs, files, Rights [NTFS] (multiple servers to PDC) Can't do PW, Workgroup, User Acct. Mgrs, Login Scripts, Print Queues or Servers Default option- all users & groups, NOT files & dirs. Must decide how duplicates handled, NW acct. policies, NetWare Admins to NT Admin PW choices- No PW, PW is username, Password is, [User Must Chg PW checked] Username/Grp Conflict options-Log Error, Ignore (no action), Replace, Add prefix (given) Default Tab- Use Supervisor Defaults [checked] = Use NetWare policies vs. NT Add Supervisors to Admins [not checked] Use Mappings in File-specify textfile-old, new username, password; groupnames .MAP NetWare \system, \login. \etc hidden and system files not transferred by default Once Transfer Files selected, options appear, default NW root vols-NT vol w/ most space File Options dialog- Modify (destination), Files (Dirs & Files vs. Vols) buttons Trial Migration option runs without changing, summary errors in LOGFILE.LOG Logging 3 options- Pop-up on error, Verbose User/Grp logging, Verbose File logging
| Top of page
Comments and suggestions? E-mail me at grantwil@sk.sympatico.ca
Last Updated: Wednesday, March 10, 1999 | Grant Wilson, Tisdale, SK. Canada