RE: Demand Dial Problems



I think you might be right on the License issue. I'm close to my max. and I
didn't know that the dod takes a CAL.

This morning the server that hasn't been connecting (Cleveland Branch
Office) connected and the server that has been connecting (Indy Branch
Office) will not connect.

So, I'm in the process of purchasing more licenses. When I get them
installed, I will update this post.

Thanks


""Crina Li"" wrote:

Hi Warwick,

Thank you for posting in SBS newsgroup.

From the description, I understand the issue to be: you have created site
to site VPN from 2 branch offices to SBS, however 1 branch office can not
connect to SBS and got some error message. If I have misunderstood your
concerns, please do not hesitate to let me know.

Based on my knowledge, the issue could be caused by the following
possibilities:

1. The connection number reaches the limitation configured in RRAS.
2. License issue.

The default maximum connection number is 5 on RRAS. You may try to increase
the number to see if the problem can be resolved. Open Routing and Remote
Access console, navigate to ports snap-in. Right-click it and choose
'Properties'. Double-click WAN Miniport (PPTP). Change the maximum port
number to 10. Click 'OK' to close the dialog boxes. After doing this, open
services.msc and then restart the RRAS related services. Can you then make
more VPN connections?

For the SBS server, each authorized connection may take one CAL. Could you
please let me know how many CAL you have installed on the server? Do you
use dedicated user accounts for the DoD connections? Please open Server
Management console, navigate to licensing snap-in. Check the installed
license number and maximum usage number in the right panel. Also, you may
open event viewer and check to see if there is any licensing warning or
errors.

If the problem still occurs, would you please help me collect the following
information?

1. Can you ping destination VPN Server or gateway when the issue occurs on
problematic branch?
2. The 20111 error is usually due to firewall/NAT devices not passing the
L2TP packages. Do you have NAT server or devices on problematic branch?
3. Have you done any changes on problematic branch? Are there any
difference between normal branch and problematic branch?
4. Are there any hardware devices before SBS and branch office network?
5. Please follow the steps below to enable PPP logging and post the log
files for analysis:

1) On the SBS server, click Start, point to Administrative Tools and click
Routing and Remote Access.
2) Right-click your server, click Properties.
3) On the Logging tab, select Log all events and Log additional Routing and
Remote Access information (used for debugging). Click OK.
4) Right-click your server, point to All Tasks and click Stop.
5) Open Windows Explorer, move the files in the C:\WINDOWS\tracing folder.
6) In Routing and Remote Access right-click your server, point to All Tasks
and click Start.
7) Reproduce the issue.
8) Zip the files in the C:\WINDOWS\tracing folder and post it to newsgroup.

Related information:

824866 List of Event IDs for the Routing and Remote Access Service
http://support.microsoft.com/default.aspx?scid=kb;EN-US;824866

For remote access between two offices, I also provide the following
documents for your reference:

Connecting a Remote Office to a Small Business Server 2000 Network
http://www.microsoft.com/technet/prodtechnol/sbs/2000/maintain/remotofc.mspx

Note: this article is for SBS 2000 network but it can also apply to SBS
2003 network.

323441 How To Install and Configure a Virtual Private Network Server in
Windows
http://support.microsoft.com/?id=323441

305550 How to configure a VPN connection to your corporate network in
Windows
http://support.microsoft.com/?id=305550

I am appreciated your time and look forward to hearing from you.

Best regards,

Crina Li (MSFT)

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.

=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| Thread-Topic: Demand Dial Problems
|| From: =?Utf-8?B?d2Fyd2lja0Bub3NwYW0ubm9zcGFt?=
<warwicknospamnospam@xxxxxxxxxxxxxxxxxxxxxxxxx>
| Subject: Demand Dial Problems
| Date: Wed, 15 Feb 2006 09:05:27 -0800
| | Newsgroups: microsoft.public.windows.server.sbs
| |
| Hi,
| I have 2 windows 2003 servers in branch offices that connect to a SBS2003
| server in the main office by vpn demand-dial interface in rras.
| Both branch office servers have been connect for 2 years.
| Now 1 server will not connect. I get a 20050 error id on the SBS2003 and
on
| the branch office 2003 server I get a 20111 event id.
| I'm using pptp, not ipsec, so this is where I'm getting confused on the
| 20111 error.....can anyone help please??
|


.



Relevant Pages

  • Re: Error 1054
    ... Here I suggest you use the configure site in Active directory to create ... link to synchronize data with SBS server for example 2 hours once. ... be set to be equal to the number of SBS client access license. ...
    (microsoft.public.windows.server.sbs)
  • Re: Licensing question about a Scheduling Resource
    ... licenses in an SBS environment is a 1 to 1 ratio. ... I can't figure out how the server came up with that number. ... License Agreement, Here it discuse the difference between Device / ... Types of SBS CALs. ...
    (microsoft.public.windows.server.sbs)
  • Re: sbs2003 license
    ... the SBS domain, does the server will disconnect the other user if you only ... best interest to call license office. ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • Re: Connection monitor versus licenses
    ... What you might be seeing on the licensing node of standard management is the maximum number of users that SBS has seen connected, ... That isn't there to indicate how many CALs you can purchase. ... There is however another server product, called Windows Server for Small Business Server, which SBS is built upon. ... Some products have only "user" licensing; each user must have a license. ...
    (microsoft.public.windows.server.sbs)
  • Re: Remote Administration
    ... I am connecting directly to the IP address ... The SBS is still ... ISA Server to enable the Remote Desktop connection. ...
    (microsoft.public.windows.server.sbs)

Quantcast