Re: Connecting to DC using VPN changes IP address for LAN clients
- From: "Bill Grant" <not.available@online>
- Date: Sat, 21 Oct 2006 11:46:58 +1000
That's pretty much my opinion too (unless you have SBS to do it all for
you).
My advice in general terms is leave a DC to be a DC. Don't make it a
router or a remote access server.
"Phillip Windell" <@.> wrote in message
news:eli2gfH9GHA.4712@xxxxxxxxxxxxxxxxxxxxxxx
In other words,...forget it and do it on a different server using 2 nics
that replaces the existing NAT device. :-)
At least that is what I think about it anyway.
I wouldn't consider all that greif to be worth it.
--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
The views expressed are my own (as annoying as they are), and not those of
my employer or anyone else associated with me.
-----------------------------------------------------
"Bill Grant" <not.available@online> wrote in message
news:uybqQ8$8GHA.3280@xxxxxxxxxxxxxxxxxxxxxxx
What you have here is the old NT multihomed PDC problem in a new form.
As soon as a remote user connects, your DC is multihomed (because RRAS
acquires an IP for ther internal interface). Microsoft recommends that
you do not multihome a DC. SBS is the only exception.
You can prevent the RRAS "internal" interface from registering its
Netbios name by disabling Netbios over TCP/IP on it. This requires a
registry edit (see KB 292822 near the end). This can cause other
problems, depending on your client machines. Older clients may have
problems without Netbios over TCP/IP. The current recommended fix is to
put the remotes in their own IP subnet. See KB 830063 . If you use this
method you have to route between the LAN subnet and the remote subnet
through the RRAS server.
You will also see in KB 292822 that you may get DNS problems as well
as Netbios problems because of dynamic DNS registering two IP addresses
for the server's name.
"Jools" <julianchappell2trash@xxxxxxxxxxx> wrote in message
news:8E43489B-E218-4521-B7F7-165332485B54@xxxxxxxxxxxxxxxx
Hi Phillip,
Many thanks for replying. I checked the network properties on the server
and
found that the lan adapter is already the top one and the dial in one is
already bottom. is there anything else it could be? I'm wondering
whether it
would make a differnce if the domain controller handled DHCP rather than
the
router ... but i want to refrain from uninformed hacking. Any ideas
anyone?
--
take out the trash to email me
"Phillip Windell" wrote:
**snip snip snipitty snip**
1. Properties of Network Places
2. Advanced from the menu at the top
3. Advanced Settings... from the dropdown menu
4. In the upper box that shows up use the side-arrows to move the main
LAN
Nic to the top of the List. Any other LAN nics need to be below that.
Any
other types of adapters (like dialup) need to be at the bottom.
--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
The views expressed are my own (as annoying as they are), and not those
of
my employer or anyone else associated with me.
-----------------------------------------------------
.
- References:
- Re: Connecting to DC using VPN changes IP address for LAN clients
- From: Bill Grant
- Re: Connecting to DC using VPN changes IP address for LAN clients
- Prev by Date: Re: NLB with two NICs in server (no not teaming)
- Next by Date: Re: Setting Up Routing using Route Command
- Previous by thread: Re: Connecting to DC using VPN changes IP address for LAN clients
- Next by thread: Re: Connecting to DC using VPN changes IP address for LAN clients
- Index(es):
Relevant Pages
|
