DHCP

  • Thread starter Thread starter rich
  • Start date Start date
R

rich

Any suggestions as to why I can set up an adapter with an
alternate IP address that works just fine, ie resolves
DNS from the server (W2K SBS), but the client cannot find
the DHCP server (the same box). So... W2K Server with a
number of clients (this happens to be set in the
192.0.0.x range) that try to pick up an IP address from
that server but they can't see the DHCP source. These
same clients were able to pick up their IP addresses from
a DLink router without a problem prior to my
reconfiguration (DHCP is now "off" there). Thanks in
advance.
 
Is the DHCP source authorized in Active Directory? Did you create a scope on
dhcp server?
 
Thanks for the response, SaltPeter...
There is an appropriate scope enabled: 192.0.0.130-199
The DHCP server is authorized and shows up in the
Authorized Servers list. When I try to release and renew
a client in a DOS window, the message returned after a
minute or so reads: "An error occurred while renewing
interface Local Area Connection : unable to contact your
DHCP server. Request has timed out."
I can certainly work around this problem, but it seems
too unnatural not to be able to use the server for DHCP
requests when the DLink router isn't having that sort of
problem. (Yes, I have turned off the DLink DHCP every
time I tested the W2K DHCP.) There are two other
serrvers running on this subnet, neither providing DHCP.
One is a Unix box running a line-of-business app and
accessed via a terminal emulator by the client, and the
other server is a W2K member server running a telephony
app. Nothing exotic here.
 
Back
Top