- To Resolve this issue, modify the following registry entry.
- Click Start, click Run, type regedit, and then click OK.
- Locate and then click the following registry key:
- On the Edit menu, point to New, and then click Key.
- Type Parameters, and then press ENTER.
- Click the Parameters key.
- On the Edit menu, point to New, and then click DWORD Value.
- Type NSPI max sessions per user, and then press ENTER.
- Double-click NSPI max sessions per user, type the number of the NSPI connections required, and then click OK.
Note: There is no specific upper-limit to this setting beyond the limits that are imposed by it being a DWORD (that is, 0xffffffff or about 4 billion). Configuring the server in this manner will make it function similarly to Windows Server 2003 in terms of the maximum number of NSPI connections that are allowed per user. This modification was made to Server 2008 to limit the ability of one user account depleting the resources of any particular DC. Modifying this entry may cause performance issues on the DC as we create a new page in memory for each NSPI connection.
for other considerations.