DHegler
2007-11-29 13:50:02 UTC
I am having issues on getting DHCP to work on the new server I just installed
on our network. I get:
Event ID 1046:
The DHCP/BINL service on the local machine, belonging to the Windows
Administrative domain ilttoyotalift.local, has determined that it is not
authorized to start. It has stopped servicing clients. The following are
some possible reasons for this:
This machine is part of a directory service enterprise and is not
authorized in the same domain. (See help on the DHCP Service Management
Tool for additional information).
This machine cannot reach its directory service enterprise and it has
encountered another DHCP service on the network belonging to a directory
service enterprise on which the local machine is not authorized.
Some unexpected network error occurred.
Then I get:
Event ID 1044:
The DHCP/BINL service on the local machine, belonging to the Windows
Administrative domain ilttoyotalift.local, has determined that it is
authorized to start. It is servicing clients now.
However, DHCP does not service any clients. Here is the background as to
how this environment was configured...
It was a Windows server 2003 SBS server running everything - DHCP, DNS, AD,
DC, GC, all 5 FSMO, Exchange, etc. We hit the 50-user limit and have
multiple sites, so I decided to buy what we should have bought before my time
here - Standard Server, etc...
I installed a new Standard Server into AD, added as DC, GC, DNS, DHCP, added
Exchange 2003 Standard. I seized all 5 FSMO roles, then demoted the original
SBS Server, removed DNS, DHCP. It still runs Exchange, but there are no
active users on it and our firewall is forwarding SMTP to the new server just
fine.
It still appears as if somewhere in AD, it has records of the original SBS
server being registered as a DNS server. The only live DNS server is the new
server and it has itself listed as its DNS server in its IP settings.
Also, something else weird about this server is that when I look at the IP
settings in the network connection, I set the static IPs, but when I save
them it always shows that it will use DHCP, but even after I reboot the
server it does keep its static settings. I have also tried to reset the
static settings a few times and rebooted, but it always shows it will use
DHCP, but keeps the static settings from an ipconfig.
Any ideas from anyone? It has been a while since I have gotten this far
into networking, as I used to be a MCSE+I, MCDBA and all that good stuff
until I moved into finance.
FYI - I also ran through Microsoft's ntdsutil steps to make sure that the
demotion of the SBS server was graceful, and I have checked the record for
the new server using ADSI Edit under Configuration, Services, Net Services -
it shows up fine. And, yes, I have authorized, unauthorized, restarted and
removed/reinstalled the DHCP service on this machine as well, but the actions
are still the same.
It feels to me that it is trying to authorize itself with the old server,
but can't see it and won't work. However, before I made any changes to the
old SBS server, I had installed DHCP on the new server and it acted the same
way as well, so maybe I'm crazy.
Thanks,
Dan Hegler
on our network. I get:
Event ID 1046:
The DHCP/BINL service on the local machine, belonging to the Windows
Administrative domain ilttoyotalift.local, has determined that it is not
authorized to start. It has stopped servicing clients. The following are
some possible reasons for this:
This machine is part of a directory service enterprise and is not
authorized in the same domain. (See help on the DHCP Service Management
Tool for additional information).
This machine cannot reach its directory service enterprise and it has
encountered another DHCP service on the network belonging to a directory
service enterprise on which the local machine is not authorized.
Some unexpected network error occurred.
Then I get:
Event ID 1044:
The DHCP/BINL service on the local machine, belonging to the Windows
Administrative domain ilttoyotalift.local, has determined that it is
authorized to start. It is servicing clients now.
However, DHCP does not service any clients. Here is the background as to
how this environment was configured...
It was a Windows server 2003 SBS server running everything - DHCP, DNS, AD,
DC, GC, all 5 FSMO, Exchange, etc. We hit the 50-user limit and have
multiple sites, so I decided to buy what we should have bought before my time
here - Standard Server, etc...
I installed a new Standard Server into AD, added as DC, GC, DNS, DHCP, added
Exchange 2003 Standard. I seized all 5 FSMO roles, then demoted the original
SBS Server, removed DNS, DHCP. It still runs Exchange, but there are no
active users on it and our firewall is forwarding SMTP to the new server just
fine.
It still appears as if somewhere in AD, it has records of the original SBS
server being registered as a DNS server. The only live DNS server is the new
server and it has itself listed as its DNS server in its IP settings.
Also, something else weird about this server is that when I look at the IP
settings in the network connection, I set the static IPs, but when I save
them it always shows that it will use DHCP, but even after I reboot the
server it does keep its static settings. I have also tried to reset the
static settings a few times and rebooted, but it always shows it will use
DHCP, but keeps the static settings from an ipconfig.
Any ideas from anyone? It has been a while since I have gotten this far
into networking, as I used to be a MCSE+I, MCDBA and all that good stuff
until I moved into finance.
FYI - I also ran through Microsoft's ntdsutil steps to make sure that the
demotion of the SBS server was graceful, and I have checked the record for
the new server using ADSI Edit under Configuration, Services, Net Services -
it shows up fine. And, yes, I have authorized, unauthorized, restarted and
removed/reinstalled the DHCP service on this machine as well, but the actions
are still the same.
It feels to me that it is trying to authorize itself with the old server,
but can't see it and won't work. However, before I made any changes to the
old SBS server, I had installed DHCP on the new server and it acted the same
way as well, so maybe I'm crazy.
Thanks,
Dan Hegler