The Grand Illusionist

Here's an example of how Microsoft File and Print Services for NetWare (FPNW) causes Windows NT and Novell NetWare to map to each other, making an NT server look familiar to NetWare clients. NetWare communicates over the IPX transport protocol via NCP commands, while Windows NT Server and its clients use the SMB protocol over TCP/IP or NetBEUI. FPNW integrates with NT Server and translates between NCPs and SMBs, invoking different components depending on the type of request issued.

For example, if a NetWare client request requires security validation, it gets filtered through the NT Server before being allowed access to the NT File System (NTFS ). If no security is required, the client can directly access the file system.

FPNW responds to Service Advertisement Protocol (SAP) calls as NetWare clients poll for the nearest server when they start up. You can toggle this feature using a check box in Server Manager's NetWare Properties dialog box. The FPNW server then appears when you use the SLIST command-line utility, permitting NetWare-compatible client software to log on to it.

---

Translation Made Easier

illustration_link (9 Kbytes)

FPNW translates between Windows NT's SMB protocol and NetWare's NCP. Highlighted are the components activated during security validation for a NetWare client.