The virtual private network wizard for client access does not seem to change the number of available virtual private network ports

When you configure Microsoft Internet Security and Acceleration (ISA) Server to be a virtual private network (VPN) server by using its VPN wizard, the Routing and Remote Access feature does not show the number of ports configured for VPN client connections after creating the VPN server through the ISA Server management console.

This wizard is supposed to be able to increase the number of VPN ports on the server. However, the number of ports listed does not change after the wizard has finished and the Routing and Remote Access feature has restarted.

This behavior may occur because the wizard changes the number of ports directly in the registry.

To resolve this behavior, restart the server.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

In some cases, when you try to set the incoming connections to a value larger than 1000, the total number of client connections remains at 1000, even after you restart the server. To resolve this problem, follow these steps:

1. Click Start, click Run, and then type rrasmgmt.msc.
2. In Routing and Remote Access Management, expand the node that corresponds to the server.
3. Right-click Ports, and then select Properties.
4. Double-click the WAN miniport protocol that you have enabled for incoming client VPN connections (PPTP or L2TP).
5. In Maximum Ports, type the value that you set in ISA Management.
6. Click OK two times, and then exit Routing and Remote Access Management.
7. Restart the server.

Note Client connections have the following limits:

• ISA 2004 Standard Edition, when used with any version of Windows: 1024
• ISA 2004 Enterprise Edition, when used with Microsoft Windows Server 2003, Standard Edition: 1024
• ISA 2004 Enterprise Edition, when used with Windows Server 2003, Datacenter Edition or with Windows Server 2003, Enterprise Edition: unlimited