PPTP ports missing in RRAS Manoj (Oman)
- From: "Manoj R Oommen" <manojoommen@xxxxxxxxx>
- Date: 8 Aug 2006 21:46:42 -0700
I need some help to determine why there are no available
PPTP ports in my Routing & Remote Access Server on my
ISA. They were there until we restarted after
downloading some updates from MS, but now all I see are
L2TP ports. I have tried disabling RRAS and restarting
it, but to no avail. Nothing has changed on the ISA
firewall - all of the protocol rules etc are still there
as they were when this was working, and when I check the
properties of the Ports container in RRAS, it shows that
PPTP is enabled. No ports show up as available, and if I
disable the L2TP ports, the list of available ports is
completely empty. Any ideas? on a multihomed PC
Thanks!
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\Services\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/treeview/default.asp?url=/technet/prodtechnol/windowsserver2003/proddocs/standard/sag_dns_pro_no_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.aspx?scid=kb;en-us;825036
291382 - Frequently asked questions about Windows 2000 DNS and Windows
Server 2003 DNS
http://support.microsoft.com/default.aspx?scid=kb;en-us;291382
296379 - How to Disable NetBIOS on an Incoming Remote Access Interface
[Registry Entry]:
http://support.microsoft.com/?id=296379
.
- Prev by Date: PPTP ports missing in RRAS
- Next by Date: Re: PPTP ports missing in RRAS
- Previous by thread: PPTP ports missing in RRAS
- Next by thread: VPN on NT4 + Firewall
- Index(es):
Relevant Pages
|
Loading
