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

Wide Area Network Considerations

Since NetBIOS is not supported across Wide Area Networks (WAN's), it is not possible to remotely access NPL across a WAN when the Gold Key is installed at the central host site.

The proper method to configure NPL to operate in a WAN environment is to install onto an NT server as described in the section titled NT Server Introduction.

If it is not possible to use an NT server, it is also possible to install single or multiuser RunTimes at the remote sites, thus authenticating RunTime security locally using an appropriate NetBIOS configuration. Once security has been passed, the remote sites can access systems across the WAN, given that appropriate remote drive mappings and privileges have been established.

NOTE: NetBIOS is required by NPL to count and determine unique terminal identification in a peer environment. While NPL does not provide direct support for TCP/IP, disk I/O requests are passed to the native operating system, and it decides which transport is used to route the disk request. Whether that request is routed via TCP/IP or NetBIOS is transparent to NPL.