W2K3 Routing & Remote Access Missing PPTP Miniports

After configuring RRAS for VPN access on W2K3 SP1 only L2TP and PPPoE ports
are available in the right (Detail) panel.

The Ports Properties has 128 PPTP and 128 L2TP available ports; however,
only L2TP ports are display in the right panel.

Disabling remote access for L2TP by uncheck the Remote Access Connection
(inbound) and the Demand Dial Routing connections check boxes leaves only the
PPPoE port displayed in the right panel (NO PPTP!!!)

If I try to connect to the VPN server an 800 error message is display in the
client. The event viewer system log on the server displays an error that
states, "No certificate was found...no remote connections will be allow..."

I have reconfigured the RRAS several times with different configuration but
no luck. I believe the PPTP ports are some how being disable for RAS.

Can somebody help me to troubleshoot this?

Thanks in advance

In news:50355B56-21E7-4725-A966-(E-Mail Removed),
Alvaro Soto <(E-Mail Removed)> stated, which I commented
on below:
> After configuring RRAS for VPN access on W2K3 SP1 only L2TP and PPPoE
> ports are available in the right (Detail) panel.
>
> The Ports Properties has 128 PPTP and 128 L2TP available ports;
> however, only L2TP ports are display in the right panel.
>
> Disabling remote access for L2TP by uncheck the Remote Access
> Connection (inbound) and the Demand Dial Routing connections check
> boxes leaves only the PPPoE port displayed in the right panel (NO
> PPTP!!!)
>
> If I try to connect to the VPN server an 800 error message is display
> in the client. The event viewer system log on the server displays an
> error that states, "No certificate was found...no remote connections
> will be allow..."
>
> I have reconfigured the RRAS several times with different
> configuration but no luck. I believe the PPTP ports are some how
> being disable for RAS.
>
> Can somebody help me to troubleshoot this?
>
> Thanks in advance

L2TP connections require IPSec, which requires a certificate to be in IPSec
so it will allow L2TP IPSec connections. I belive that is why it's not
coming up as an option. See if this helps:

How To Configure all aspects of RAS on Windows 2003:
http://www.microsoft.com/resources/d...rras_howto.asp

and more specifically for L2TP:
http://www.microsoft.com/technet/pro...10a9a06e3.mspx


--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

If you are having difficulty in reading or finding responses to your post,
instead of the website you are using, if I may suggest to use OEx (Outlook
Express or any other newsreader of your choosing), and configure a newsgroup
account, pointing to news.microsoft.com. This is a direct link into the
Microsoft Public Newsgroups, and it is FREE and DOES NOT require a Usenet
account with your ISP. With OEx, you can easily find your post, track
threads, cross-post, and sort by date, poster's name, watched threads or
subject.

Not sure how? It's easy:
How to Configure OEx for Internet News
http://support.microsoft.com/?id=171164

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft MVP - Windows Server Directory Services
Microsoft Certified Trainer
Assimilation Imminent. Resistance is Futile.
Infinite Diversities in Infinite Combinations.
=================================

"Ace Fekay [MVP]" wrote:

> In news:50355B56-21E7-4725-A966-(E-Mail Removed),
> Alvaro Soto <(E-Mail Removed)> stated, which I commented
> on below:
> > After configuring RRAS for VPN access on W2K3 SP1 only L2TP and PPPoE
> > ports are available in the right (Detail) panel.
> >
> > The Ports Properties has 128 PPTP and 128 L2TP available ports;
> > however, only L2TP ports are display in the right panel.
> >
> > Disabling remote access for L2TP by uncheck the Remote Access
> > Connection (inbound) and the Demand Dial Routing connections check
> > boxes leaves only the PPPoE port displayed in the right panel (NO
> > PPTP!!!)
> >
> > If I try to connect to the VPN server an 800 error message is display
> > in the client. The event viewer system log on the server displays an
> > error that states, "No certificate was found...no remote connections
> > will be allow..."
> >
> > I have reconfigured the RRAS several times with different
> > configuration but no luck. I believe the PPTP ports are some how
> > being disable for RAS.
> >
> > Can somebody help me to troubleshoot this?
> >
> > Thanks in advance
>
> L2TP connections require IPSec, which requires a certificate to be in IPSec
> so it will allow L2TP IPSec connections. I belive that is why it's not
> coming up as an option. See if this helps:
>
> How To Configure all aspects of RAS on Windows 2003:
> http://www.microsoft.com/resources/d...rras_howto.asp
>
> and more specifically for L2TP:
> http://www.microsoft.com/technet/pro...10a9a06e3.mspx
>
>
> --
> Ace
>
> This posting is provided "AS-IS" with no warranties or guarantees and
> confers no rights.
>
> If you are having difficulty in reading or finding responses to your post,
> instead of the website you are using, if I may suggest to use OEx (Outlook
> Express or any other newsreader of your choosing), and configure a newsgroup
> account, pointing to news.microsoft.com. This is a direct link into the
> Microsoft Public Newsgroups, and it is FREE and DOES NOT require a Usenet
> account with your ISP. With OEx, you can easily find your post, track
> threads, cross-post, and sort by date, poster's name, watched threads or
> subject.
>
> Not sure how? It's easy:
> How to Configure OEx for Internet News
> http://support.microsoft.com/?id=171164
>
> Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
> Microsoft MVP - Windows Server Directory Services
> Microsoft Certified Trainer
> Assimilation Imminent. Resistance is Futile.
> Infinite Diversities in Infinite Combinations.
> =================================
>
>
>
Hello and thanks for your post,

I didn't mention in my post that my VPN server is multihomed and its also
the DC, DNS, DHCP for the domain. Is also important to mention that the WAN
interface in my VPN server is a simple NIC connected by Ethernet to an ADSL
modem, so my WAN interface has an IP of 192.168.1.2 and uses 192.168.1.254 as
the default gateway which is the intranet face of the ADSL modem.

Yesterday I disable the WAN interface (secondary NIC) and configure the RRAS
to use the Intranet interface (primary NIC), which has an IP address of
192.168.1.1, and the PPTP ports were available!!!! I configured the VPN by
PPTP just fine.

The issue is that I want to use the primary NIC only for DNS, DHCP etc for
the intranet clients and the secondary NIC only for VPN users, but when I try
to configure the VPN with this NIC no PPTP ports are available!!! Only L2TP
ports.

I think the problem is with the IP address for my WAN interface, however I’m
not 100% sure, if you have any suggestions or articles please send it to me.

Best regards

In news:14AFAD60-0B78-4C49-A11C-(E-Mail Removed),
Alvaro Soto <(E-Mail Removed)> stated, which I commented
on below:
> Hello and thanks for your post,
>
> I didn't mention in my post that my VPN server is multihomed and its
> also the DC, DNS, DHCP for the domain. Is also important to mention
> that the WAN interface in my VPN server is a simple NIC connected by
> Ethernet to an ADSL modem, so my WAN interface has an IP of
> 192.168.1.2 and uses 192.168.1.254 as the default gateway which is
> the intranet face of the ADSL modem.
>
> Yesterday I disable the WAN interface (secondary NIC) and configure
> the RRAS to use the Intranet interface (primary NIC), which has an IP
> address of 192.168.1.1, and the PPTP ports were available!!!! I
> configured the VPN by PPTP just fine.
>
> The issue is that I want to use the primary NIC only for DNS, DHCP
> etc for the intranet clients and the secondary NIC only for VPN
> users, but when I try to configure the VPN with this NIC no PPTP
> ports are available!!! Only L2TP ports.
>
> I think the problem is with the IP address for my WAN interface,
> however I'm not 100% sure, if you have any suggestions or articles
> please send it to me.
>
> Best regards

Ah, interesting. Being a multihomed DC changes the picture drastically.

Just to let you know, a multihomed AD DC is not advised because of the
implications of the AD DNS domain records. There has been much written about
multi-homed DCs and not being recommended. Here are some steps to fix the DC
to insure internal domain functions are functional and clients can
authenticate to and find the DC. It's honestly easier to acquire an
inexpensive DSL/Cable router to handle the NAT requirements for your DC and
make the DC a single homed machine. You can still configure RRAS and allow
VPN access to it whether choosing L2TP or PPTP.

Read thru this carefully and understand the implications of a multihomed DC
and altering it's default functions by the following steps. Maybe a Linksys
router, at approx $30.00 USD is starting to sound a whole lot better.

+++++++++++++++++++++++++++++
1. Insure that ALL NICS only point to your internal DNS server(s)' IP
address only
and none others, such as your ISP's DNS servers' IP addresses.

2. In Network & Dialup properties, Advanced Menu item, Advanced Settings,
move the internal NIC (the network that AD is on) to the top of the binding
order (top of the list).

3. Disable the ability for the outer NIC to register. The procedure, as
mentioned, involves identifying the outer NIC's GUID number. This link will
show you how:
246804 - How to Enable-Disable Windows 2000 Dynamic DNS Registrations (per
NIC too):
http://support.microsoft.com/?id=246804

4. Disable NetBIOS on the outside NIC. That is performed by choosing to
disable NetBIOS in IP Properties, Advanced, and you will find that under the
"WINS" tab. You may want to look at step #3 in the article to show you how
to disable NetBIOS on the RRAS interfaces if this is a RRAS server.
296379 - How to Disable NetBIOS on an Incoming Remote Access Interface
[Registry Entry]:
http://support.microsoft.com/?id=296379

Note: A standard Windows service, called the "Browser service", provides the
list of machines, workgroup and domain names that you see in "My Network
Places" (or the legacy term "Network Neighborhood"). The Browser service
relies on the NetBIOS service. One major requirement of NetBIOS service is a
machine can only have one name to one IP address. It's sort of a
fingerprint. You can't have two brothers named Darrell. A multihomed machine
will cause duplicate name errors on itself because Windows sees itself with
the same name in the Browse List (My Network Places), but with different
IPs. You can only have one, hence the error generated.

5. Disable the "File and Print Service" and disable the "MS Client Service"
on the outer NIC. That is done in NIC properties by unchecking the
respective service under the general properties page. If you need these
services on the outside NIC (which is unlikely), which allow other machines
to connect to your machine for accessing resource on your machine (shared
folders, printers, etc.), then you will probably need to keep them enabled.

6. Uncheck "Register this connection" under IP properties, Advanced
settings, "DNS" tab.

7. Delete the outer NIC IP address, disable Netlogon registration, and
manually create the required records

a. In DNS under the zone name, (your DNS domain name), delete the outer NIC's
IP references for the "LdapIpAddress". If this is a GC, you will need to
delete the GC IP record as well (the "GcIpAddress"). To do that, in the DNS
console, under the zone name, you will see the _msdcs folder. Under that,
you will see the _gc folder. To the right, you will see the IP address
referencing the GC address. That is called the GcIpAddress. Delete the IP
addresses referencing the outer NIC.

i. To stop these two records from registering that information, use the
steps provided in the links below:
Private Network Interfaces on a Domain Controller Are Registered in
DNShttp://support.microsoft.com/?id=295328

ii. The one section of the article that disables these records is done with
this registry entry:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Netlogon\Parameters
(Create this Multi-String Value under it):
Registry value: DnsAvoidRegisterRecords
Data type: REG_MULTI_SZ
Values: LdapIpAddress
GcIpAddress

iii. Here is more information on these and other Netlogon Service records:
Restrict the DNS SRV resource records updated by the Netlogon service
[including GC]:
http://www.microsoft.com/technet/tre...o_rr_in_ad.asp

b. Then you will need to manually create these two records in DNS with the
IP addresses that you need for the DC. To create the LdapIpAddress, create a
new host under the domain, but leave the "hostname" field blank, and provide
the internal IP of the DC, which results in a record that looks like:
(same as parent) A 192.168.5.200 (192.168.5.200 is used for illustrative
purposes)

i. You need to also manually create the GcIpAddress as well, if this is a
GC. That would be under the _msdcs._gc SRV record under the zone. It is
created in the same fashion as the LdapIpAddress mentioned above.

8. In the DNS console, right click the server name, choose properties, then
under the "Interfaces" tab, force it only to listen to the internal NIC's IP
address, and not the IP address of the outer NIC.

9. Since this is also a DNS server, the IPs from all NICs will register,
even if you tell it not to in the NIC properties. See this to show you how
to stop that behavior (this procedure is for Windows 2000, but will also
work for Windows 2003):
275554 - The Host's A Record Is Registered in DNS After You Choose Not to
Register the Connection's Address:
http://support.microsoft.com/?id=275554

10. If you haven't done so, configure a forwarder. You can use 4.2.2.2 if
not sure which DNS to forward to until you've got the DNS address of your
ISP. How to configure a forwarder?
Depending on your operating system, choose one of the following articles:

300202 - HOW TO: Configure DNS for Internet Access in Windows 2000
http://support.microsoft.com/?id=300202&FR=1

323380 - HOW TO: Configure DNS for Internet Access in Windows Server 2003
(How to configure a forwarder):
http://support.microsoft.com/d/id?=323380



**** Additional Reading ****

Here are more links to read up on and understand what is happening:

292822 - Name Resolution and Connectivity Issues on Windows 2000 Domain
Controller with Routing and Remote Access and DNS Insta {DNS and RRAS and
unwanted IPs registering into DNS]:
http://support.microsoft.com/?id=292822

246804 - How to enable or disable DNS updates in Windows 2000 and in Windows
Server 2003
http://support.microsoft.com/?id=246804

295328 - Private Network Interfaces on a Domain Controller Are Registered in
DNS
[also shows DnsAvoidRegisterRecords LdapIpAddress to avoid reg sameasparent
private IP]:
http://support.microsoft.com/?id=295328

306602 - How to Optimize the Location of a DC or GC That Resides Outside of
a Client's
Site [Includes info LdapIpAddress and GcIpAddress information and the SRV
mnemonic values]:
http://support.microsoft.com/?id=306602

825036 - Best practices for DNS client settings in Windows 2000 Server and
in Windows Server 2003 (including how-to configure a forwarder):
http://support.microsoft.com/default...b;en-us;825036

291382 - Frequently asked questions about Windows 2000 DNS and Windows
Server 2003 DNS
http://support.microsoft.com/default...b;en-us;291382

296379 - How to Disable NetBIOS on an Incoming Remote Access Interface
[Registry Entry]:
http://support.microsoft.com/?id=296379

+++++++++++++++++++++++++++++++

Hello Ace:

Thanks you very much for your help, I have follow the articles and
recomendations that you gave me and the VPN is done deal.

thanks again!!!!!


"Ace Fekay [MVP]" wrote:

> In news:14AFAD60-0B78-4C49-A11C-(E-Mail Removed),
> Alvaro Soto <(E-Mail Removed)> stated, which I commented
> on below:
> > Hello and thanks for your post,
> >
> > I didn't mention in my post that my VPN server is multihomed and its
> > also the DC, DNS, DHCP for the domain. Is also important to mention
> > that the WAN interface in my VPN server is a simple NIC connected by
> > Ethernet to an ADSL modem, so my WAN interface has an IP of
> > 192.168.1.2 and uses 192.168.1.254 as the default gateway which is
> > the intranet face of the ADSL modem.
> >
> > Yesterday I disable the WAN interface (secondary NIC) and configure
> > the RRAS to use the Intranet interface (primary NIC), which has an IP
> > address of 192.168.1.1, and the PPTP ports were available!!!! I
> > configured the VPN by PPTP just fine.
> >
> > The issue is that I want to use the primary NIC only for DNS, DHCP
> > etc for the intranet clients and the secondary NIC only for VPN
> > users, but when I try to configure the VPN with this NIC no PPTP
> > ports are available!!! Only L2TP ports.
> >
> > I think the problem is with the IP address for my WAN interface,
> > however I'm not 100% sure, if you have any suggestions or articles
> > please send it to me.
> >
> > Best regards
>
> Ah, interesting. Being a multihomed DC changes the picture drastically.
>
> Just to let you know, a multihomed AD DC is not advised because of the
> implications of the AD DNS domain records. There has been much written about
> multi-homed DCs and not being recommended. Here are some steps to fix the DC
> to insure internal domain functions are functional and clients can
> authenticate to and find the DC. It's honestly easier to acquire an
> inexpensive DSL/Cable router to handle the NAT requirements for your DC and
> make the DC a single homed machine. You can still configure RRAS and allow
> VPN access to it whether choosing L2TP or PPTP.
>
> Read thru this carefully and understand the implications of a multihomed DC
> and altering it's default functions by the following steps. Maybe a Linksys
> router, at approx $30.00 USD is starting to sound a whole lot better.
>
> +++++++++++++++++++++++++++++
> 1. Insure that ALL NICS only point to your internal DNS server(s)' IP
> address only
> and none others, such as your ISP's DNS servers' IP addresses.
>
> 2. In Network & Dialup properties, Advanced Menu item, Advanced Settings,
> move the internal NIC (the network that AD is on) to the top of the binding
> order (top of the list).
>
> 3. Disable the ability for the outer NIC to register. The procedure, as
> mentioned, involves identifying the outer NIC's GUID number. This link will
> show you how:
> 246804 - How to Enable-Disable Windows 2000 Dynamic DNS Registrations (per
> NIC too):
> http://support.microsoft.com/?id=246804
>
> 4. Disable NetBIOS on the outside NIC. That is performed by choosing to
> disable NetBIOS in IP Properties, Advanced, and you will find that under the
> "WINS" tab. You may want to look at step #3 in the article to show you how
> to disable NetBIOS on the RRAS interfaces if this is a RRAS server.
> 296379 - How to Disable NetBIOS on an Incoming Remote Access Interface
> [Registry Entry]:
> http://support.microsoft.com/?id=296379
>
> Note: A standard Windows service, called the "Browser service", provides the
> list of machines, workgroup and domain names that you see in "My Network
> Places" (or the legacy term "Network Neighborhood"). The Browser service
> relies on the NetBIOS service. One major requirement of NetBIOS service is a
> machine can only have one name to one IP address. It's sort of a
> fingerprint. You can't have two brothers named Darrell. A multihomed machine
> will cause duplicate name errors on itself because Windows sees itself with
> the same name in the Browse List (My Network Places), but with different
> IPs. You can only have one, hence the error generated.
>
> 5. Disable the "File and Print Service" and disable the "MS Client Service"
> on the outer NIC. That is done in NIC properties by unchecking the
> respective service under the general properties page. If you need these
> services on the outside NIC (which is unlikely), which allow other machines
> to connect to your machine for accessing resource on your machine (shared
> folders, printers, etc.), then you will probably need to keep them enabled.
>
> 6. Uncheck "Register this connection" under IP properties, Advanced
> settings, "DNS" tab.
>
> 7. Delete the outer NIC IP address, disable Netlogon registration, and
> manually create the required records
>
> a. In DNS under the zone name, (your DNS domain name), delete the outer NIC's
> IP references for the "LdapIpAddress". If this is a GC, you will need to
> delete the GC IP record as well (the "GcIpAddress"). To do that, in the DNS
> console, under the zone name, you will see the _msdcs folder. Under that,
> you will see the _gc folder. To the right, you will see the IP address
> referencing the GC address. That is called the GcIpAddress. Delete the IP
> addresses referencing the outer NIC.
>
> i. To stop these two records from registering that information, use the
> steps provided in the links below:
> Private Network Interfaces on a Domain Controller Are Registered in
> DNShttp://support.microsoft.com/?id=295328
>
> ii. The one section of the article that disables these records is done with
> this registry entry:
>
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Netlogon\Parameters
> (Create this Multi-String Value under it):
> Registry value: DnsAvoidRegisterRecords
> Data type: REG_MULTI_SZ
> Values: LdapIpAddress
> GcIpAddress
>
> iii. Here is more information on these and other Netlogon Service records:
> Restrict the DNS SRV resource records updated by the Netlogon service
> [including GC]:
> http://www.microsoft.com/technet/tre...o_rr_in_ad.asp
>
> b. Then you will need to manually create these two records in DNS with the
> IP addresses that you need for the DC. To create the LdapIpAddress, create a
> new host under the domain, but leave the "hostname" field blank, and provide
> the internal IP of the DC, which results in a record that looks like:
> (same as parent) A 192.168.5.200 (192.168.5.200 is used for illustrative
> purposes)
>
> i. You need to also manually create the GcIpAddress as well, if this is a
> GC. That would be under the _msdcs._gc SRV record under the zone. It is
> created in the same fashion as the LdapIpAddress mentioned above.
>
> 8. In the DNS console, right click the server name, choose properties, then
> under the "Interfaces" tab, force it only to listen to the internal NIC's IP
> address, and not the IP address of the outer NIC.
>
> 9. Since this is also a DNS server, the IPs from all NICs will register,
> even if you tell it not to in the NIC properties. See this to show you how
> to stop that behavior (this procedure is for Windows 2000, but will also
> work for Windows 2003):
> 275554 - The Host's A Record Is Registered in DNS After You Choose Not to
> Register the Connection's Address:
> http://support.microsoft.com/?id=275554
>
> 10. If you haven't done so, configure a forwarder. You can use 4.2.2.2 if
> not sure which DNS to forward to until you've got the DNS address of your
> ISP. How to configure a forwarder?
> Depending on your operating system, choose one of the following articles:
>
> 300202 - HOW TO: Configure DNS for Internet Access in Windows 2000
> http://support.microsoft.com/?id=300202&FR=1
>
> 323380 - HOW TO: Configure DNS for Internet Access in Windows Server 2003
> (How to configure a forwarder):
> http://support.microsoft.com/d/id?=323380
>
>
>
> **** Additional Reading ****
>
> Here are more links to read up on and understand what is happening:
>
> 292822 - Name Resolution and Connectivity Issues on Windows 2000 Domain
> Controller with Routing and Remote Access and DNS Insta {DNS and RRAS and
> unwanted IPs registering into DNS]:
> http://support.microsoft.com/?id=292822
>
> 246804 - How to enable or disable DNS updates in Windows 2000 and in Windows
> Server 2003
> http://support.microsoft.com/?id=246804
>
> 295328 - Private Network Interfaces on a Domain Controller Are Registered in
> DNS
> [also shows DnsAvoidRegisterRecords LdapIpAddress to avoid reg sameasparent
> private IP]:
> http://support.microsoft.com/?id=295328
>
> 306602 - How to Optimize the Location of a DC or GC That Resides Outside of
> a Client's
> Site [Includes info LdapIpAddress and GcIpAddress information and the SRV
> mnemonic values]:
> http://support.microsoft.com/?id=306602
>
> 825036 - Best practices for DNS client settings in Windows 2000 Server and
> in Windows Server 2003 (including how-to configure a forwarder):
> http://support.microsoft.com/default...b;en-us;825036
>
> 291382 - Frequently asked questions about Windows 2000 DNS and Windows
> Server 2003 DNS
> http://support.microsoft.com/default...b;en-us;291382
>
> 296379 - How to Disable NetBIOS on an Incoming Remote Access Interface
> [Registry Entry]:
> http://support.microsoft.com/?id=296379
>
> +++++++++++++++++++++++++++++++
>
>
>
>

In news:36D57119-8795-42EC-A040-(E-Mail Removed),
Alvaro Soto <(E-Mail Removed)> stated, which I commented
on below:
> Hello Ace:
>
> Thanks you very much for your help, I have follow the articles and
> recomendations that you gave me and the VPN is done deal.
>
> thanks again!!!!!

My pleasure, I'm glad it helped. Very good to hear!!

Ace

I have only one NIC on my Server and pptp ports are missing. Also i cant have
another one because on my firewalll i have a mapped ip to this server for
pptp. i dont ave sp1 installed. after installing a security patch pptp ports
are disappeared. i dont know which security patch is it?

Thanks Manoj Muscat.

"Ace Fekay [MVP]" wrote:

> In news:36D57119-8795-42EC-A040-(E-Mail Removed),
> Alvaro Soto <(E-Mail Removed)> stated, which I commented
> on below:
> > Hello Ace:
> >
> > Thanks you very much for your help, I have follow the articles and
> > recomendations that you gave me and the VPN is done deal.
> >
> > thanks again!!!!!
>
> My pleasure, I'm glad it helped. Very good to hear!!
>
> Ace
>
>
>