High performance PPTP server

[Guest]

We have a Win2k3 server at work configured as a PPTP server. Each time the
server hits > 60 simultaneous connections new clients cannot connect to the
server. The server has enough free IP addresses to allocate, but doesn't seem
to respond to further queries. Is there a limitation in the number of
connections for Win2K3? As a side question, can anyone suggest some
whitepapers/sites for load balancing PPTP servers?

 

[Bob Lin \(MS-MVPS\)]

what's the error code?

 

[Guest]

Most of the times, users are not getting an error code. The client hands when
trying to connect to the server. It hangs in the "authenticating username and
password" screen. Users have to cancel and try connecting several times
before they are successful. When they do get an error, it is error code 800.
Thank you.

- V.

 

[Puja Pandey[MSFT]]

Can you also check if the number of ports on the RRAS server for PPTP is
more than 60.

Thanks,
Puja

 

[Guest]

Puja - The server is set for 100 PPTP ports and 10 L2TP ports. The IP range
spans 100 addresses. Thank you.

- V

 

[Janani [MSFT]]

Vinay,
Can you enable tracing on the server and share out the logs here?
You can enable tracing with the following command
netsh ras set tracing * ena

After the 61st connection fails, disable tracing(as this flushes the logs)
using the command "netsh ras set tra* dis" and share out the logs on the
server from the %windir%\tracing directory.

Additionally, can you give us information regarding your server setup? Is
the internet side of your server behind a firewall or a NAT?

 

[Colin M. McGroarty]

Janani,

Thank you for your response. The server itself is a
Windows 2003 member server running as a dedicated VPN server which has no
other applications running on it. A NS50 performing 1 to 1 NAT sits in
between the server and the internet. 50 MB of bandwidth are available to
the connection.

Specifically which of the logs would be most beneficial to look at? I've
tried attaching the entire tracing directory as a zip file (1.39 MB) and am
receiving a message from MS that the file is too large to post.

Thanks in advance for your assistance.

Kind Regards,

--
Colin M. McGroarty, MCSE, MCP+I, NT-CIP
2004 Microsoft MVP, Windows Server - General
www.McGroarty.org


Vinay,
Can you enable tracing on the server and share out the logs here?
You can enable tracing with the following command
netsh ras set tracing * ena

After the 61st connection fails, disable tracing(as this flushes the logs)
using the command "netsh ras set tra* dis" and share out the logs on the
server from the %windir%\tracing directory.

Additionally, can you give us information regarding your server setup? Is
the internet side of your server behind a firewall or a NAT?