Hmmm. I'm only using 20% of the available addresses in
this scope, so it looks like I have plenty to go around.
-Chris
>-----Original Message-----
> If RRAS is set to "obtain IP addresses automatically"
it will lease IP
>addresses from DHCP to use as its address pool. In some
cases this may
>deplete your DHCP scope.
>
> There is a registry key which determines how many
addresses RRAS will
>lease at a time. Or you can configue RRAS to use a
defined set of IPs, and
>exclude those from your scope.
>
> If you are short of IPs in your DHCP scope, you can
use a different IP
>subnet for your address pool, and route the remote
subnet through the RRAS
>server. (That is, you route all remote clients as if
they were a remote
>site).
>
>"Chris Thomas" <(E-Mail Removed)> wrote in message
>news:0caf01c3bff3$13a144c0$(E-Mail Removed)...
>> I am currently in the progress of upgrading my Windows
NT
>> domain to Windows Server 2003. In an attempt to "do
more
>> with less", I tried to get rid of my old clunky RAS
>> server and put all RRAS services on my 2K3 domain
>> controller that is also running the DHCP, WINS and DNS
>> services. I'd had this domain controller up and
running
>> successfully for a little over a month before making
it a
>> RRAS server. After loading the RRAS service, hooking
up
>> my Digi and configuring my modems, I started receiving
>> complaints from users that could no longer receive an
ip
>> address from DHCP. I manually assigned ip info on each
>> of the problem users until I finally put two and two
>> together and figured out that RRAS was probably causing
>> the problems. I stopped the RRRAS service on this
server
>> and now DHCP is back to working again.
>>
>> My questions are, can I successfully run RRAS and DHCP
on
>> the same server, and if so, how in the heck do I
>> configure RRAS so that it does not interfere with
normal
>> DHCP duties?
>>
>> Thanks in advance for the help.
>>
>> -Chris
>>
>
>
>.
>
|