DHCP problems...

  • Thread starter Thread starter Brad Pears
  • Start date Start date
B

Brad Pears

We have a windwos 2000 SBS and a Windwos 2000 member server in our
environment. The Windwos 2000 member server was configured as the DHCP
server quite some time ago and has been working fine.

Recently though, I have noticed event id# 1051 (source DHCPServer) being
logged on this machine which states that the DHCP/BINL service is not
authorized to service clients in the domain {ourdomain.local)

So, after doing some research, I "reauthorized" the server using the DHCP
console on our small busines server to see if this corrects the problem.

After I did that, I logged onto our DHCP server (the win2K member server),
went to DHCP and noticed that nothing was listed in the "authorized" servers
area. Is this that way it is supposed to be? I assumed it would have updated
from Active directory. Or, are the authorized servers only listed on the
domain controller machine (our SBS machine)? Anyway, I clicked on
"authorize", added the servername, clicked OK and got an error "The DHCP
service could not contact Active Directory."

Is this indicating a problem with this machine or is this what I should have
expected? If it is a problem, what should I be trying to resolve the issue?

Thanks,

Brad
 
If it can not contact AD, the most common problem is the DNS is wrong. the
machine should use the DC/DNS in the network settings. There should not be
any other DNS listed.
 
I do have the primary DNS listed as our DC (our SBS machine) in network
settings. There is a secondary DNS listed in there. Should I remove this??

Brad
Phillip Windell said:
If it can not contact AD, the most common problem is the DNS is wrong. the
machine should use the DC/DNS in the network settings. There should not be
any other DNS listed.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

Brad Pears said:
We have a windwos 2000 SBS and a Windwos 2000 member server in our
environment. The Windwos 2000 member server was configured as the DHCP
server quite some time ago and has been working fine.

Recently though, I have noticed event id# 1051 (source DHCPServer) being
logged on this machine which states that the DHCP/BINL service is not
authorized to service clients in the domain {ourdomain.local)

So, after doing some research, I "reauthorized" the server using the DHCP
console on our small busines server to see if this corrects the problem.

After I did that, I logged onto our DHCP server (the win2K member server),
went to DHCP and noticed that nothing was listed in the "authorized" servers
area. Is this that way it is supposed to be? I assumed it would have updated
from Active directory. Or, are the authorized servers only listed on the
domain controller machine (our SBS machine)? Anyway, I clicked on
"authorize", added the servername, clicked OK and got an error "The DHCP
service could not contact Active Directory."

Is this indicating a problem with this machine or is this what I should have
expected? If it is a problem, what should I be trying to resolve the issue?

Thanks,

Brad
Click to expand...
Click to expand...
 
Brad Pears said:
I do have the primary DNS listed as our DC (our SBS machine) in network
settings. There is a secondary DNS listed in there. Should I remove this??
Click to expand...

Is it the ISP's DNS? I would recommend removing it from there and placing
it in the Forwarder's List in the config of the AD/DNS. Just make sure that
the AD/DNS machine is allowed to make DNS qeries to the ISP's DNS.

It really should work even with that being there, but if you set it up "by
the book" as I suggest then you will better know "where you stand" if it
still doesn't work. This way if there is something preventing you from
getting a response from your AD/DNS then you will *know* what you dealing
with becuase you will get no DNS response at all, rather than a DNS response
from "who knows where" that may cloud up the troubleshooting...like the way
it is now, if your AD/DNS doesn't respond if will "fail over" to the ISP's
DNS and that makes if difficult to know what is happening.
 
Yes, it is the IP's DNS.

I'll set it up on the forwarders list... I am assuming you mean to set it
up in the "Forward Lookup" zone?? Would I create a new forward lookup zone
for the ISP's DNS??

Right now there is one forward lookup zone and that is the .local name of
our domain i.e. "tnlhdom.local".

Thanks,

Brad
Please let me know where exactly that is configured...
 
Hi Brad,

You are making things way too difficult for yourself. Let SBS do ALL the
serving, including DHCP, WINS and DNS. If you run ICW, it should put the ISP
DNS numbers in the tab Forwarders of the DNS server.

--
Regards,

Marina
Microsoft SBS-MVP
One of the Magical M&M's
 
Brad Pears said:
Yes, it is the IP's DNS.

I'll set it up on the forwarders list... I am assuming you mean to set it
up in the "Forward Lookup" zone?? Would I create a new forward lookup zone
for the ISP's DNS??
Click to expand...

No. It is not a "zone".

1. Go into the DNS MMC
2. Right-click on the Server itself
3. Choose Properties
4. Choose the Forwarders Tab
5. Enter it there in the lower section.
 
Back
Top