"); 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; } //-->

Network Requirements

When installing or recalling authorization on the server, you should be logged in as the administrator or have administrator privileges. If not, the operation will fail.

All networking must be established and working before proceeding with installation. All clients should be able to communicate with and 'see' the server correctly, and log into the correct domain before running the installation routine.

The simplest security organization is where all users log into the DOMAIN for which the server is the domain host. The server must have run User Manager for Domains and added the user before the workstation is set up. Using a common domain for server and workstations means that when a workstation logs in, the user's password gives it access privileges by default on the server. It is also possible to set up the security for workgroups (which are basically independent domains with browsing rights).

See the configuration requirements for:



Additional information on selected topics:

Mixed Network Considerations

Microsoft Windows Terminal Server Considerations