Stop DHCP assignments to RAS devices

  • Thread starter Thread starter Mark St Laurent
  • Start date Start date
M

Mark St Laurent

I have recently enabled DHCP service on W2K Server SP4
w/DNS & AD enabled, into our otherwise statically
configured environment. I have a limited amount of
addressing to use for DHCP enabled clients. When I check
the DHCP lease tables I find that addressing is being
assigned to PC's that are statically configured, not to
there NIC's but to RAS. When I try to ping these
assignments they are not active but I believe that they
will not be assigned to devices requiring them.
What are these RAS assignments and how do I stop this.
 
You are right, RRAS is getting IP addresses from your DHCP server, here are
two things you can do:

1.- Reduce the number of RRAS ports so that it does not take all your DHCP
addresses
2.- Configure RRAS no to use DHCP.
 
As Eduardo said, the RRAS server will lease IP addresses from DHCP to use
for remote access users. You can prevent this by using a static pool of
addresses for RRAS. To prevent RRAS (or any other device set to use DHCP)
from using IP addresses you have statically assigned, you must exclude these
addresses from the DHCP scope.
 
Routing & Remote Access is not running on the DHCP server
or any other server on my network, which means the config
problem is at the local machine level any thoughts as to
which devices are configured to request these addresses
and how to correct.
 
Some machine on your network must be configured to act as a RAS server. It
could be one (or more) workstation(s) configured to accept an incoming
connection.
 
Back
Top