The Win2k Active Directory will run primarily independent of your current structure. You have to decide if you want the user to log on to Novell primarily, Active Directory primarily or work towards a single sign on. I am not sure what type of "gateway" you are speaking of. However, it sounds like the rest of the city community is using Novell and you need the Novell server so that you can share files between you and them. If this is the case here, it would be my recommendation to create a Win2k Active Directory. Use the Gateway Services for Netware to make Win2k the gateway to the Novell network. Move all of the users and their workstations into the Active Directory domain. Move all of the printers into the Active Directory domain. The way this will end up working is that when the users request a file from the Novell machine, the request will come through the Win2k machine to the Novell machine. A single user account will be used by the Win2k machine to access files on the Novell machine and present them to the user.
This solution reduces the maintenance that you will need to perform. If you load the Client Services for Netware (CSNW) on each Win2k workstation instead, you will have to maintain user accounts in both the Active Directory and the Novell system. In addition, you will need to keep them synchronized. If you use the gateway solution as described, the workstations only need TCP/IP and it will not need IPX. It will only need the Win2k Server operating as the gateway. If you load the CSNW instead, each client will need to run IPX/SPX and TCP/IP (assuming you have internet connectivity).
For more information on how to set this up, look at the Win2k Resource Kit - Windows 2000 Internetworking Guide, Chapter 13.
This was first published in July 2001