Change licenseing Mode

Per-Seat Licensing
If the customer is using per-seat Client Access Licenses (CALs) for the application, those licenses apply when a client is accessing the application on either server in the cluster.

Per-Server Licensing
If the customer is using per-server (or concurrent use) Client Access Licenses for the application, each computer in the cluster should have a sufficient number of per-server Client Access Licenses for the expected peak load of the application on that computer

For example, if both nodes of a cluster were running Microsoft SQL Server Enterprise Edition, the following licenses are needed to install a SQL Server based MSCS implementation:
Two fully licensed nodes of Windows NT 4.0 Server, Enterprise Edition or two licensed Windows 2000 Advanced servers.

Two licensed copies of SQL Server Enterprise 6.5 or 7.0. (Two SQL server licenses are required even if only one instance of the server is run at a time in active-passive mode and four licenses are required for an Active-Active configuration).
SQL Server Client Access Licenses (CAL?s). Both the nodes of the cluster must be licensed even if only one node at a time is being run as in active passive mode. In an environment running in per-server mode, MSCS does not transfer CAL?s from one node to the other in the event of a fail over. Separate CAL?S have to be purchased for each node even if the clients connect only to one virtual server. However, a cluster does not affect per-seat licensing.

Depending on the network library used for connecting to the SQL server, separate CAL?s might be needed.

If using Named Pipes, an Windows NT 4.0/Windows 2000 CAL is needed for each client as Windows NT 4.0/Windows 2000 authenticates these connections directly.

or

If using TCP/IP sockets, Windows NT 4.0/Windows 2000 CAL?s for each client are not needed because Windows NT 4.0/Windows 2000 does not authenticate these connections directly.