Previous Page | Next Page

  1. Introduction
  2. Installation
  3. Hardware Issues
  4. Filesystems
  5. Networking
  6. Security
  7. Servers
  8. Services
  9. Utilities
  10. Control Panel
  11. Printing
  12. Performance Monitor
  13. Network Monitor
  14. Event Viewer
  15. Other Issues
  16. User Accounts
  17. Groups
  18. Policies
  19. User Rights
  20. Auditing
  21. System Policies
  22. Sharing
  23. Profiles
  24. Roaming Profiles
  25. Domains
  26. Server Management
  27. Directory Replication
  28. License Management
  29. Client Administrator
  30. Netware Tools
  31. Macintosh Support
  32. RAS Server
  33. SNMP
  34. DHCP
  35. DNS
  36. WINS
  37. Mail Service
  38. Internet
  39. Internet Information Server
  40. Routing and Firewalls
  41. Items to Remember
  42. Terms
  43. Credits

Windows NT Netware Tools

NetWare

NWLink alone does not support access to NetWare core services (file and print services). It only allows applications to be run. CSNW or GSNW must be used to allow file and print service access to NetWare servers.

NetWare 4.1 is for larger networks with several servers. Netware 3.12 is an older version for a single server network. Novell 3.12 and 4.1 use different service requestors, but 4.1 will respond to 3.12 requests when bindary emulation is enabled. Novell understands the UNC naming convention.

Terms

  • NDS - NetWare Directory Services
  • DFS - Distributed File System for Windows makes all shared resources available in a graphical tree.
  • DSMN - Directory Service Manager for NetWare. Does not ship with NT 4.0.
  • PFNW - Products File and Print Services for NetWare. This will allow an NT server to act directly as a NetWare server where NetWare clients are concerned. This is now called Service for NetWare. Does not ship with NT 4.0.

Advantages of Microsoft Networking vs NetWare

  • Lower license costs.
  • Better server and network stability
  • Multi protocol support allows for migration to other transport protocols and/or use of them.
  • Support of other platform types within the network scheme due to multi protocol support.
  • Microsoft networking accepts the use of other platforms for other specific functions such as firewalls.

Overall, Microsoft has produced a very versatile networking scheme which allows for a great deal of flexability. It would even allow an easier migration to some better or future networking scheme.

Migration Tools

NT migration tools include:

  • Migration Service for Netware - Used to automatically migrate shared resources to Windows NT servers from NetWare servers.
  • GSNW - Gateway Services for Netware provides access to NetWare servers for clients that do not support NetWare client functions. GSNW or CSNW installation automatically installs NWLink.

Microsoft services for NetWare includes PFNW and DSMN.

NetWare to NT Migration path

  1. Install NT servers and possible GSNW.
  2. Copy NetWare accounts to NT domains.
  3. Create directory structure using DFS as a substitute for the NetWare directory services (NDS) tree.
  4. Add Microsoft redirector to all Windows and OS/2 clients.
  5. Using the migration tool, migrate NetWare resources to NT servers.
  6. Change DOS clients using NetWare networking to NT clients with Microsoft networking ability.
  7. Remove all NetWare client software
  8. Finish resource migration to NT.
  9. Use NT multi-protocol router to replace netware routers.
  10. NetWare servers and clients are not necessary.

GSNW

GSNW attaches to a NetWare server as a client, then serves the resources accessed to clients attaching to the GSNW server. A GSNW server should only perform that function. It requires much processing power to translate the NetWare protocols to Microsoft protocols. Memory is also helpful with this server. Setting up GSNW:

  1. From the properties selection of Network Neighborhood, select the services tab.
  2. Add "Gateway and Client Services for NetWare", installing from the CDROM. The GSNW and CSNW are installed as one piece since both are required to support the gateway.
  3. On the NetWare server, create a group calleds NTGATEWAY. Create a user in the NTGATEWAY group on the NetWare Server or NDS tree that has rights to the resources to be shared.
  4. Set GSNW to attach to the NetWare tree or preferred server adding the resources to the GSNW service.
  5. Set up the group NTGATEWAY and user for NetWare resources on the domain?
  6. Restart the GSNW computer and enter the user created in the above step when the computer restarts.
  7. Connect to the NetWare server.
  8. From the GSNW control panel applet, click "Gateway" and click the checkbox "Enable Gateway". Enter the name of the created user and password in the password boxes.
  9. Click "Add" and enter a name for the NT side of the share and the UNC path to the NetWare directory to be shared. The GSNW permissions are set on the NT Gateway shares for specific users. Other controls:
    • Permissions button - allows you to set permissions for the share to the NetWare resource. This is done for the Microsoft network clients.
    • Add button - Allows addition of additional NetWare shares.
  10. In the "Use Drive" list, enter a drive letter that is free on your system and click OK.

To attach to the NetWare 4.1 server as a client:

  1. Select the GSNW applet in control panel.
  2. Select the "Default Tree and Context" radio button and enter the tree name in the "Tree" text box and the User account context in the "Context" box..

To attach to NetWare 3.12, select the "Preferred Server" radio button (Bindary Mode) rather than the "Default Tree and Context" radio button (NDS -NetWare Directory Services). NT 3.51 and before only support bindary mode.

To share a NetWare printer using GSNW, click on "Start", "Settings", "Printers". Click "Add Printer" and select the NetWare printer to add, install appropriate drivers if necessary. Then right click the installed printer and make it shared.

Avoiding File Duplication

When migrating from NetWare to NT using GSNW, as migration continues, there will at some points be a mix of NetWare and NT clients. If a copy of NetWare server files is put on NT servers and NT clients use the files on the NT server and NetWare clients use files on the NetWare server, there will be version control problems. This is because NT client changes will not match NetWare client changes. The way to migrate properly is to allow the GSNW server to get the NetWare files from the NetWare server for Microsoft clients when requests are made. This way there is only one copy of the file and the file can be appropriately locked for version control purposes. Once all the clients are converted to use the Microsoft server, only then should the NetWare files be placed directly on the NT server and made directly available.

Using Migration Tool to complete Migration

When GSNW is installed, the migration tool is also installed. To start, select "Migration Tool for NetWare" in Administrative Tools. There is a list of servers that can be migrated and the following buttons:

  • Add - Used to add NetWare fileservers to be migrated.
  • Delete
  • User Options - Brings up the user and group options dialog box. There are four tabs:
    • Passwords - Allows configuration of password options for migrated users.
      • Transfer Users and Groups checkbox.
      • Use Mappings in File checkbox - This allows a specified file to be used to set up passwords for individual users to create better security. To use:
        1. Check the box.
        2. Enter the name of the file you want to create and click the "Create" button.
        3. Click "OK" and you will see a created mappings file for your users. You can add passwords to the file.
      • "No Password", "Password is Username", and "Password is:" radio buttons allow a choice of no password, username to be the password, or a specific password for all migrated users respectively.
    • User Names - Specifies handling of duplicated user names. The choice is one of the following four radio buttons:
      • Log Error
      • Ignore - If there is a conflict, no action is performed.
      • Overwrite with new info - The NT account information is replaced.
      • Add Prefix - Prefixes may be added if any names are found to be duplicate between the NetWare environment and Windows environment.
    • Group Names - Specifies handling of duplicated group names. The choice is one of the following three radio buttons:
      • Log Error
      • Ignore
      • Add Prefix
    • Defaults - How account restrictions will be handled.
      • Use Supervisor Defaults checkbox - If checked, the account policy is migrated from the NetWare server and NetWare defaults will apply to the accounts migrated to the NT server..
      • Add supervisors to the Administrators Group checkbox.
      • Migrate Specific NetWare Account Information checkbox
  • File Options - Can select files and volumes to be transferred from NetWare and where they are to be put on NT. The NetWare directories \SYSTEM, \LOGIN, and \ETC are not transferred by default. Buttons are:
    • Add
    • Delete
    • Modify - Used to Specify a different NT destination directory.
    • Files - Allows Specification of files and directories to be transferred.
  • Start Migration
  • Trial Migration - A method of testing to see how the migration works before actually doing the migration.
  • Logging - Sets the options for event logging during the migration. Options are:
    • Pop up on errors
    • Verbose User/Group Logging
    • Verbose File Logging
Items that can be migrated are:
  • User accounts
  • Group accounts
  • Directories and files
  • Permissions to files and directories.

Items that can not be migrated are:

  • Passwords
  • Workgroup and user account managers
  • Logon scripts
  • Print server and print queue information.

Passwords cannot be migrated from the NetWare server. Multiple NetWare server user and database informations may be migrated at the same time to one NT Server. Selection of handling duplicate NetWare and NT names can be done. The best option is to prefix any duplicate user names with "nw". NetWare account policies may be transferred or default NT policies may be used.

CSNW Installation and Configuration

NWLink IPX/SPX is installed when CSNW is installed. CSNW Installation:

  1. From the control panel network applet, select the "Services" tab, click add and select "Client Service for Netware".
  2. Restart the computer,

Configuration:

  1. Run the control panel CSNW applet that was created at installation time.
  2. Select the "Services" tab. You can now select the following Options:
    • Preferred Server radio button (bindary context) for NW 3.12 or before with "Select Preferred Server" dropdown box..
    • Default Tree and context radio button with "Tree" and "Context" text boxes.
    • Three checkbox print options, "Add Form Feed", "Notify When Printed", and "Print Banner".
    • One checkbox, "Run Logon Script".