This article was previously published under Q151307
This article has been archived. It is offered "as is" and will no longer be updated.
This article describes issues related to client access license.
There are two different licensing models that customers can choose, eithera per server or per seat. The per server licensing (concurrent licensing)will cause Windows NT to implement a concurrency check to only allow thenumber of concurrent file/print users as configured in license manager.Per seat licensing does not implement the license manager check, thoughthe customer must still purchase a client access license (CAL) for suchclients.
The following uses require a CAL:
Server Message Block (SMB) file & print (Windows NT Server)
NCP file & print (FPNW)
Remote Access Service (RAS)
Services for Macintosh (SFM)
Examples of SMB connections are: connecting to a Windows NT server fileshare or printer share through Windows for Workgroups 3.11, a MicrosoftNetwork client, a LAN manager client, or a Windows 95 client. A NetWareclient access FPNW requires a separate CAL.
Note the following general exception to Windows CAL requirements. Windows CALs are not required when access to the server software is unauthenticated and conducted through the Internet. Authenticated access is defined as an exchange of user or application credentials between the server software and a user or device. An example of this exception is if unidentified users browse your public Web site. Windows CALs are not required for those users.
For information about Microsoft Windows Server 2003 client access licensing, visit the following Microsoft Web site: