VPN Server getting confused

Scenario:
Windows 2k3 Server in the following roles:
Domain Controller
DHCP & WINS Server
Print Server
File Server
RRAS Server

The RRAS is setup so there is a pool of IP addresses which are assigned to
connected users that fit our addressing range.

The problem: when outside users connect to this server via VPN, the server
gets "confused" and inside users lose printing, logon, and access to network
shares; even after a VPN client has disconnected. My dept head restarted the
server, but I suspect doing an "ipconfig/release" and then a "renew" would
set things to rights. However, I want to avoid this entirely. What do I need
to do to keep the server from getting IP confusion?

mm

it might not be the best idea to have your domain controller use dhcp to get
an address. so the release/renew plan shouldnt work at all.



"El Marko" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Scenario:
> Windows 2k3 Server in the following roles:
> Domain Controller
> DHCP & WINS Server
> Print Server
> File Server
> RRAS Server
>
> The RRAS is setup so there is a pool of IP addresses which are assigned to
> connected users that fit our addressing range.
>
> The problem: when outside users connect to this server via VPN, the server
> gets "confused" and inside users lose printing, logon, and access to
> network shares; even after a VPN client has disconnected. My dept head
> restarted the server, but I suspect doing an "ipconfig/release" and then a
> "renew" would set things to rights. However, I want to avoid this
> entirely. What do I need to do to keep the server from getting IP
> confusion?
>
> mm
>
>

No. The DC itself has a FIXED address. However, it is a DHCP server and
assigns from a pool of addresses to VPN clients.

I did find that cycling the RRAS service clears the second IP address.


<(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> it might not be the best idea to have your domain controller use dhcp to
> get an address. so the release/renew plan shouldnt work at all.
>
>
>
> "El Marko" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> Scenario:
>> Windows 2k3 Server in the following roles:
>> Domain Controller
>> DHCP & WINS Server
>> Print Server
>> File Server
>> RRAS Server
>>
>> The RRAS is setup so there is a pool of IP addresses which are assigned
>> to connected users that fit our addressing range.
>>
>> The problem: when outside users connect to this server via VPN, the
>> server gets "confused" and inside users lose printing, logon, and access
>> to network shares; even after a VPN client has disconnected. My dept head
>> restarted the server, but I suspect doing an "ipconfig/release" and then
>> a "renew" would set things to rights. However, I want to avoid this
>> entirely. What do I need to do to keep the server from getting IP
>> confusion?
>>
>> mm
>>
>>
>
>

right. i was only commenting on how if it IS assigned a static address,
ipconfig /renew or release wont work. it will only work on dhcp enabled
adapters



"El Marko" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> No. The DC itself has a FIXED address. However, it is a DHCP server and
> assigns from a pool of addresses to VPN clients.
>
> I did find that cycling the RRAS service clears the second IP address.
>
>
> <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> it might not be the best idea to have your domain controller use dhcp to
>> get an address. so the release/renew plan shouldnt work at all.
>>
>>
>>
>> "El Marko" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>>> Scenario:
>>> Windows 2k3 Server in the following roles:
>>> Domain Controller
>>> DHCP & WINS Server
>>> Print Server
>>> File Server
>>> RRAS Server
>>>
>>> The RRAS is setup so there is a pool of IP addresses which are assigned
>>> to connected users that fit our addressing range.
>>>
>>> The problem: when outside users connect to this server via VPN, the
>>> server gets "confused" and inside users lose printing, logon, and access
>>> to network shares; even after a VPN client has disconnected. My dept
>>> head restarted the server, but I suspect doing an "ipconfig/release" and
>>> then a "renew" would set things to rights. However, I want to avoid this
>>> entirely. What do I need to do to keep the server from getting IP
>>> confusion?
>>>
>>> mm
>>>
>>>
>>
>>
>
>

OK. I see.

Well the renew/release didn't work and cycling the service did.

However, I am trying to avoid this completely.

<(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> right. i was only commenting on how if it IS assigned a static address,
> ipconfig /renew or release wont work. it will only work on dhcp enabled
> adapters
>
>
>
> "El Marko" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> No. The DC itself has a FIXED address. However, it is a DHCP server and
>> assigns from a pool of addresses to VPN clients.
>>
>> I did find that cycling the RRAS service clears the second IP address.
>>
>>
>> <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>>> it might not be the best idea to have your domain controller use dhcp to
>>> get an address. so the release/renew plan shouldnt work at all.
>>>
>>>
>>>
>>> "El Marko" <(E-Mail Removed)> wrote in message
>>> news:(E-Mail Removed)...
>>>> Scenario:
>>>> Windows 2k3 Server in the following roles:
>>>> Domain Controller
>>>> DHCP & WINS Server
>>>> Print Server
>>>> File Server
>>>> RRAS Server
>>>>
>>>> The RRAS is setup so there is a pool of IP addresses which are assigned
>>>> to connected users that fit our addressing range.
>>>>
>>>> The problem: when outside users connect to this server via VPN, the
>>>> server gets "confused" and inside users lose printing, logon, and
>>>> access to network shares; even after a VPN client has disconnected. My
>>>> dept head restarted the server, but I suspect doing an
>>>> "ipconfig/release" and then a "renew" would set things to rights.
>>>> However, I want to avoid this entirely. What do I need to do to keep
>>>> the server from getting IP confusion?
>>>>
>>>> mm
>>>>
>>>>
>>>
>>>
>>
>>
>
>

It is the old multihomed PDC problem from NT in a new form. As soon as a
remote user connects, the server gets a second IP from the pool for the
internal interface (the VPN endpoint). See KB 292822 and 830063 .

El Marko wrote:
> OK. I see.
>
> Well the renew/release didn't work and cycling the service did.
>
> However, I am trying to avoid this completely.
>
> <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> right. i was only commenting on how if it IS assigned a static
>> address, ipconfig /renew or release wont work. it will only work on
>> dhcp enabled adapters
>>
>>
>>
>> "El Marko" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>>> No. The DC itself has a FIXED address. However, it is a DHCP server
>>> and assigns from a pool of addresses to VPN clients.
>>>
>>> I did find that cycling the RRAS service clears the second IP
>>> address. <(E-Mail Removed)> wrote in message
>>> news:(E-Mail Removed)...
>>>> it might not be the best idea to have your domain controller use
>>>> dhcp to get an address. so the release/renew plan shouldnt work at
>>>> all. "El Marko" <(E-Mail Removed)> wrote in message
>>>> news:(E-Mail Removed)...
>>>>> Scenario:
>>>>> Windows 2k3 Server in the following roles:
>>>>> Domain Controller
>>>>> DHCP & WINS Server
>>>>> Print Server
>>>>> File Server
>>>>> RRAS Server
>>>>>
>>>>> The RRAS is setup so there is a pool of IP addresses which are
>>>>> assigned to connected users that fit our addressing range.
>>>>>
>>>>> The problem: when outside users connect to this server via VPN,
>>>>> the server gets "confused" and inside users lose printing, logon,
>>>>> and access to network shares; even after a VPN client has
>>>>> disconnected. My dept head restarted the server, but I suspect
>>>>> doing an "ipconfig/release" and then a "renew" would set things
>>>>> to rights. However, I want to avoid this entirely. What do I need
>>>>> to do to keep the server from getting IP confusion?
>>>>>
>>>>> mm

Thank you.

On the section where DNS is configured, we have no Forward Lookup Zone
configured since we are using forwarders. SHould I just skip the DNS
section?

"Bill Grant" <not.available@online> wrote in message
news:%(E-Mail Removed)...
> It is the old multihomed PDC problem from NT in a new form. As soon as
> a remote user connects, the server gets a second IP from the pool for the
> internal interface (the VPN endpoint). See KB 292822 and 830063 .
>
> El Marko wrote:
>> OK. I see.
>>
>> Well the renew/release didn't work and cycling the service did.
>>
>> However, I am trying to avoid this completely.
>>
>> <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>>> right. i was only commenting on how if it IS assigned a static
>>> address, ipconfig /renew or release wont work. it will only work on
>>> dhcp enabled adapters
>>>
>>>
>>>
>>> "El Marko" <(E-Mail Removed)> wrote in message
>>> news:(E-Mail Removed)...
>>>> No. The DC itself has a FIXED address. However, it is a DHCP server
>>>> and assigns from a pool of addresses to VPN clients.
>>>>
>>>> I did find that cycling the RRAS service clears the second IP
>>>> address. <(E-Mail Removed)> wrote in message
>>>> news:(E-Mail Removed)...
>>>>> it might not be the best idea to have your domain controller use
>>>>> dhcp to get an address. so the release/renew plan shouldnt work at
>>>>> all. "El Marko" <(E-Mail Removed)> wrote in message
>>>>> news:(E-Mail Removed)...
>>>>>> Scenario:
>>>>>> Windows 2k3 Server in the following roles:
>>>>>> Domain Controller
>>>>>> DHCP & WINS Server
>>>>>> Print Server
>>>>>> File Server
>>>>>> RRAS Server
>>>>>>
>>>>>> The RRAS is setup so there is a pool of IP addresses which are
>>>>>> assigned to connected users that fit our addressing range.
>>>>>>
>>>>>> The problem: when outside users connect to this server via VPN,
>>>>>> the server gets "confused" and inside users lose printing, logon,
>>>>>> and access to network shares; even after a VPN client has
>>>>>> disconnected. My dept head restarted the server, but I suspect
>>>>>> doing an "ipconfig/release" and then a "renew" would set things
>>>>>> to rights. However, I want to avoid this entirely. What do I need
>>>>>> to do to keep the server from getting IP confusion?
>>>>>>
>>>>>> mm
>
>

Yes. If this server is not running DNS for your domain, you only
need to worry about the Netbios problems. The article assumes you have DNS
installed on this machine. Dynamic DNS gives similar problems to the Netbios
problem (ie IPs on different interfaces for the same name).

El Marko wrote:
> Thank you.
>
> On the section where DNS is configured, we have no Forward Lookup Zone
> configured since we are using forwarders. SHould I just skip the DNS
> section?
>
> "Bill Grant" <not.available@online> wrote in message
> news:%(E-Mail Removed)...
>> It is the old multihomed PDC problem from NT in a new form. As
>> soon as a remote user connects, the server gets a second IP from the
>> pool for the internal interface (the VPN endpoint). See KB 292822
>> and 830063 . El Marko wrote:
>>> OK. I see.
>>>
>>> Well the renew/release didn't work and cycling the service did.
>>>
>>> However, I am trying to avoid this completely.
>>>
>>> <(E-Mail Removed)> wrote in message
>>> news:(E-Mail Removed)...
>>>> right. i was only commenting on how if it IS assigned a static
>>>> address, ipconfig /renew or release wont work. it will only work on
>>>> dhcp enabled adapters
>>>>
>>>>
>>>>
>>>> "El Marko" <(E-Mail Removed)> wrote in message
>>>> news:(E-Mail Removed)...
>>>>> No. The DC itself has a FIXED address. However, it is a DHCP
>>>>> server and assigns from a pool of addresses to VPN clients.
>>>>>
>>>>> I did find that cycling the RRAS service clears the second IP
>>>>> address. <(E-Mail Removed)> wrote in message
>>>>> news:(E-Mail Removed)...
>>>>>> it might not be the best idea to have your domain controller use
>>>>>> dhcp to get an address. so the release/renew plan shouldnt work
>>>>>> at all. "El Marko" <(E-Mail Removed)> wrote in message
>>>>>> news:(E-Mail Removed)...
>>>>>>> Scenario:
>>>>>>> Windows 2k3 Server in the following roles:
>>>>>>> Domain Controller
>>>>>>> DHCP & WINS Server
>>>>>>> Print Server
>>>>>>> File Server
>>>>>>> RRAS Server
>>>>>>>
>>>>>>> The RRAS is setup so there is a pool of IP addresses which are
>>>>>>> assigned to connected users that fit our addressing range.
>>>>>>>
>>>>>>> The problem: when outside users connect to this server via VPN,
>>>>>>> the server gets "confused" and inside users lose printing,
>>>>>>> logon, and access to network shares; even after a VPN client has
>>>>>>> disconnected. My dept head restarted the server, but I suspect
>>>>>>> doing an "ipconfig/release" and then a "renew" would set things
>>>>>>> to rights. However, I want to avoid this entirely. What do I
>>>>>>> need to do to keep the server from getting IP confusion?
>>>>>>>
>>>>>>> mm