bad address in DHCP

  • Thread starter Thread starter JR Trent
  • Start date Start date
J

JR Trent

We are getting numerous references to bad_address in our
DHCP on our W2K DC. We've recently (in the last 2 days)
activated RAS for one of our application servers and I was
wondering if this could be the cause of the problem.
 
RRAS servers MAY be configured to use a "static pool of addresses"
or to use a DHCP server for them. Check that first.
 
Our RRAS is configured to use DHCP and what I'm noticing
after a couple of days of running is that everytime one of
these PC's connects they acquire a new address from my
pool. Is static a better way to go for this type of
application?
 
JR Trent said:
Our RRAS is configured to use DHCP and what I'm noticing
after a couple of days of running is that everytime one of
these PC's connects they acquire a new address from my
pool. Is static a better way to go for this type of
application?
Click to expand...

I don't believe static would be better. My general recommendation
is that if you have DHCP, let RRAS defer to it.

How many possible connections do you have configured in RRAS,
especially for VPNs? (The default is a LOT.)
 
The RRAS server grabs leases in batches of 10. the leases should be given
back when the lease expires though.
 
That may be part of my problem. While I see it using a
batch of 10 (and remember this from set up), but we've
always used the default expiration of 8 days. Is there a
way to limit this on particular logins/PC's, as opposed to
having it set to the default of the scope?
 
Possibly with a User Class on the DHCP and clients.

I have never tried to set a class for the RAS server but it
might work. Especially if the RRAS server is a DHCP
relay agent (you can ask, but just trust me: RAS servers
defer to the DHCP server better if they, the RAS servers,
are DHCP relay agents.)

User Classes can define and alternative LEASE period.
 
Hello All,


Conflict detection is done by the DHCP server by pinging an IP address
before offering that ip to a requesting client. By default this is not
enabled. To enable it:

Right click on the server in the DHCP management and select properties.
Go to the Advanced tab and add a value to the Conflict detection attempts
(0 to disable)

This value will determine the number of times an attempt will be made to
ping the address being offered. If no response is given then the address is
offered to the client. If a reply is given then the server attaches a
BAD_ADDRESS value to that IP address in the scope. This method can be used
as a troubleshooting method to help if you suspect duplicate IP addresses
in use on your network.


Shane Brasher
MCSE (2003,2000,NT),MCSA Security, Network+, A+
Microsoft Technical Support

This posting is provided "AS IS" with no warranties, and confers no rights.
 
Shane Brasher said:
Hello All,
Conflict detection is done by the DHCP server by pinging an IP address
before offering that ip to a requesting client. By default this is not
enabled. To enable it:
Click to expand...

Irrelevant to the message to which you replied and generally to
the current question.

It is also not a good thing to depend upone but a way you HOPE
you will avoid serious errors when you make another mistake.
 
Back
Top