I have 2 old DCs (Windows 2000 Server) and I built an additional DC which is
Win2k3. The DC is configured properly, with DNS working. I installed DHCP on
it and wanted to add the same scope which was there in the old DHCP server
(which is on a DC). After adding it, I disabled the old DHCP server (infact
deactivated and also disabled the service). But, still the clients do not
get the DHCP address from the new server. I am not sure what could be wrong.

I went through this article, and I did as it said, but could not import the
file as it was an .mdb file and here they talk about a text file.

But, when I turn back the old DHCP server again clients start getting the IP
Address. Is there something, I am not aware in Windows Server 2003 DHCP
server.

I appreciate your early response, as I need to get this done by Monday
morning.

thanks in advance.

Hi Felix,

Would it be possible for you to post the ip configuration for both the
windows 2000 and 2003 servers that are in question? A bit more info on
the config is needed for us to help out. Also, did you disable the old
DHCP server before you installed DHCP and created / activated the new
scope? Sometimes this does cause conflict but if it is the only DHCP
server on the network after the old one is kicked off, the workstations
/ appliances should detect it as they only send out a request packet
across the network, i may be wrong.

Cheers,
Matt Byrne

Hi Oz,

Thanks for your reply. Well, yes I found the info in MS KB, where you cannot
deactivate an existing scope unless and until, you plan to totally
decommision that scope. The problem, I am facing is that since the old DHCP
server was already in place, I created the same scope in the new DHCP server
and it has had a conflict. The only way is that I need to decommission the
old server and totally shut it down and then make sure that the clients get
the IP Address from the new DHCP server.

I even disabled the services of the old DHCP server, but it did not help I
think, probably it should be unauthorized from the AD and make the new DHCP
server to be the authorized DHCP server.

Here is the info:
http://support.microsoft.com/kb/197197/EN-US/#top

This might even help for others, who setup new DHCP in the same LAN with the
same scope!. I may have to head today to get this shutdown and make sure
that the other DHCP server is the only server that is advertised on the
network.

What do you think OZ ?

thanks in advance!!

"OzPacific" <matthew@ozpacific.net.au> wrote in message
news:1139719686.056629.239060@f14g2000cwb.googlegr oups.com...

Well I would totally unauthorise the old DHCP server from the network,
deactivate the scope (wont make a difference anyway since its not going
to be authorised) and then setup the new DHCP server, scope and then
authorise that server. It then should be the only DHCP server on the
network and i then can't see a problem with clients obtaining IP
Addresses if the scope is exactly the same.

What's the event logs showing on the new server and possibly on the
workstations?

Cheers,
Matt Byrne

Hi Byrne,

I did disable the old DHCP server and even shut down the server. I
uninstalled the new DHCP server and reinstalled it, created the scope and it
is authorized automatically, may be I did autho
rize it yesterday. But the only error I am seeing now on the event logs is
the following. I even went and addded the domainadmin credentials to this
section and restarted it. It restarted fine, but I am not sure whether I
should wait patiently for another 30 minutes before it could supply IP
addresses to the clients. If I do an ipconfig/release and renew it does not
get it.

Any other thoughts? Well, I may have to wait patiently for sometime maybe.

Event Type: Warning
Event Source: DhcpServer
Event Category: None
Event ID: 1056
Date: 2/12/2006
Time: 10:54:11 AM
User: N/A
Computer: MFDC1
Description:
The DHCP service has detected that it is running on a DC and has no
credentials configured for use with Dynamic DNS registrations initiated by
the DHCP service. This is not a recommended security configuration.
Credentials for Dynamic DNS registrations may be configured using the
command line "netsh dhcp server set dnscredentials" or via the DHCP
Administrative tool.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 00 00 ....



"OzPacific" <matthew@ozpacific.net.au> wrote in message
news:1139756755.272334.136060@f14g2000cwb.googlegs roups.com...

I even wondered whether it could be some kind of DHCP Relay on the Router
that was not enabled. Infact, all these machines are connected to the
switch. And, if that Switch had some issues, how will the other DHCP server
which was available earlier is working fine and the new one is not.

I even dug an article on the client side and this sounds great, but
unfortunately it should be the same for both if there was something that was
not enabled on the switch.

Just a thought!!

The Switch is Cisco Catalyst 3750 POE-48

Here is the article I got for the clients not able to see the DHCP server,
and I have the same message shown the article below (after my cries) as
these clients are PXE clients.

thanks again as if anybody does come across something please do let me know.
I am kinda pulling my head from yesterday, as I never faced this with
another site and this site it is having problems. My Network guy (so called
guru) he would say oh its not a network problem, its a server problem and
will blame it on me.

I have got the old server up and running and its issuing the DHCP address
for now, and hopefully, I can get some solution to fix it. They do not even
have support contract with Microsoft, for me to call them.

What a place? WOW!!
------------------------------------------------------------------------------------
No DHCP or proxy DHCP offers were found / No Proxy DHCP offers

Article #: AKB1420

Author: 1108

Date: 2/23/2004 11:39:58 AM



--------------------------------------------------------------------------------



Question:

What does the error message "No DHCP or proxy DHCP offers were found" or "no
proxy DHCP offers" mean and what are some general troubleshooting steps to
resolve this issue?

Answer:

This error is usually received when the client booting up via PXE is having
difficulty communicating with the DHCP/PXE server. The common
troubleshooting steps and/or causes of this problem are as follows:



1) The PXE client is connected to a managed switch that does not have
portfast enabled and/or is running spanning-tree. Portfast will need to be
enabled. To read more about what spanning-tree and portfast are, please
review knowledge-base article AKB1418.



2) The DHCP/PXE server(s) reside on a different subnet than the PXE client.
Please follow the steps outlined in knowledge-base article AKB1407.



3) If the above steps do not correct the issue, place the DHCP Server, PXE
server and a client machine on a hub. Test PXE to see if the same message is
received. If the same error message is not received, this is a good
indication that there is some factor on the network not permitting the
DHCP/PXE protocols to be passed down to the client machine.



4) Place a hub between the PXE client and the switch the client is
connecting to. If at this point the PXE client works successfully, please
review step 1 of this KB Article.



5) If this problem is still occurring after testing out the above, collect
sniffer traces from the DHCP/PXE server(s) and contact support.














"Felix" <jfkind@hotmail.com> wrote in message
news:uw45Tc$LGHA.3100@tk2msftngp13.phx.gbl...

Thanks guys for all the replies and pulling your head.................. Here
is the answer!!

Thanks for your reply! I have done everything and have done what all you
have told me and then still failed. As, I could not ask my boss who is "THE
SO CALLED CISCO GUY/NETWORK GUY" and I tell him that there is something that
needs to be enabled on the SWITCH as he would say oh there is nothing wrong
on the SWITCH or the ROUTER. I had a tussle with him for another issue like
this. So, I shut my mouth this time.

Later on today I explained to him this problem and then he told me Oh, I
know where it is wrong after 30 minutes and said, I am sorry I forgot to add
the HELPER ADDRESS on the SWITCH to point to the new server. Without this
the clients will not know which server to go for DHCP REQUEST. So, this was
the problem why I had all these issues.

Isn't IT Wonderful?

Whatever!! thanks to all of you and so many others who also replied to me in
other locations. But, you guys are great and I am really thankful for all
the replies.

thanks again!!

"Felix" <jfkind@hotmail.com> wrote in message
news:uFcJzYAMGHA.2600@TK2MSFTNGP10.phx.gbl...