"); gbWndPopupLinks.document.close(); if (!s_bNS3 && gbWndTemp != null) { gbWndTemp.close(); }else { gbWndPopupLinks.focus(); } return true; } return false; } onload = BSSCOnLoad; document.onclick = BSSCOnClick; onunload = BSSCOnUnload; onerror = BSSCOnError; function reDo() { if (innerWidth != origWidth || innerHeight != origHeight) location.reload(); } if ((parseInt(navigator.appVersion) >= 4) && (navigator.appName == "Netscape")) { origWidth = innerWidth; origHeight = innerHeight; onresize = reDo; } //-->

NT Server Introduction

Welcome to the NPLSecure - NT Server Setup. This setup procedure is designed for networks that have an NT Server available to perform security functions. The NPLSecure service will be installed to that server. All workstations will require access to that server in order to operate this software.

NOTE: If the target network does not have a Windows NT or 2000 Server, or if all clients do not have access to that server, or if the Novell or NetBIOS Network Setup procedure may be more appropriate, or if you are not sure, please exit the setup procedure and contact your Authorized Niakwa Distributor for assistance.

Overview

The NPLSecure - NT Server Security Enhancements are part of an entirely new security mechanism designed to improve reliability and ease of administration for Windows NT Server-based networks. The "new security" provides the same features as the previously available security, but is protocol independent. That is, it does not require NetBIOS or a Netware server to be installed.

NOTE: The installation routines will require TCP/IP to be operational (so that they can automatically acquire a server name). It may also be that TCP/IP is required for the RunTime to function. However no additional protocol will be required at any time.

This product is included on all Release V Windows RunTimes and enabled for use with all "Supported Networks" licenses. Standard NetBIOS RunTime licenses will not support the NT Security Enhancements. Upon installation of a Supported Networks RunTime, the user is given the option of what type of security method to use: Novell Netware (semaphore) or NetBIOS (NiakNetW) vs. NT (service process).

The security mechanism operates as an "NT service process" under Windows NT 4.0 Server or Windows 2000 Server variants. This service process manages concurrent user counts as users start and end RunTime sessions on connected workstations. The workstation can be any valid Windows 32-bit operating system (Windows 98, ME, NT, 2000, XP Pro).

NOTE: At the time of publication it appeared that XP Home Edition does not have the ability to log into an NT / 2000 Server. Therefore XP Home Edition cannot be used with NPLSecure.

Microsoft's DCOM is used to handle the communication between the workstation RunTime session and the security service on the server. DCOM hides the networking details from the program, and (supposedly) works with various networking protocols, including TCP/IP, IPX/SPX, NetBIOS, and NetBEUI, so the software should be independent of the network configuration. The rule of thumb is: if the Windows workstation can 'see' the server (access files), the user-counting mechanism should work.

The RunTime connects to the user-counting service process when it starts and disconnects when it quits, thereby allowing the service to keep track of how many RunTimes are currently executing. If the network connection is broken, the RunTime will display a warning and try to reconnect; if it cannot reconnect within 15 minutes it will quit. On the server, the user-counting service will also detect the broken connection, and will wait 15 minutes for the RunTime to reconnect before subtracting it from the user count.

For more information on network configuration requirements, see the Network Requirements section.

To begin the installation process, see the Running Setup on Server section.