"Jason Hill" <(E-Mail Removed)> wrote in message
news:6a2a01c3e677$f77e6ba0$(E-Mail Removed)...
> I have a windows 2000 active directory running DHCP for
> the clients. Yesterday I had a workstation that is setup
> for DHCP,
I presume you mean "setup as a DHCP CLIENT".
On first reading I thought you meant "DHCP server" however.
> come up with the wrong Default Gateway. I
If you mean a "DHCP client" this is usually cause by the NIC/IP properties
having
a DNS server address listed.
Manual entries override DHCP assigned entries. (This is a useful feature
when you
need it, but an nuance when it happens by accident or through error.)
> replaced the NIC 3 times and still the same error. I
> turned off DHCP client on the workstation side and set a
> static IP and everything worked fine. Today, I have 3
> other systems doing the same thing. Any idea's what would
> cause this?
Or the DHCP server is giving out this address. Perhaps even in a
reservation.
The DNS address is derived three major ways in order of (highest) priority:
Manually at the client
DHCP server reservation for the client
DHCP assignment for the scope in general
(Technically, there follows: DHCP server settings, globally for all
scopes.)
That's it unless you found a bug. (Unlikely)
--
Herb Martin
|
Similar Threads
