Re: Windows Server 2003 DHCP server - Does not release IP Addresses
- From: "Felix" <jfkind@xxxxxxxxxxx>
- Date: Sun, 12 Feb 2006 12:57:38 -0600
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@xxxxxxxxxxx> wrote in message
news:uw45Tc$LGHA.3100@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxx> wrote in message
news:1139756755.272334.136060@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
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
.
- Follow-Ups:
- References:
- Windows Server 2003 DHCP server - Does not release IP Addresses
- From: Felix
- Re: Windows Server 2003 DHCP server - Does not release IP Addresses
- From: OzPacific
- Re: Windows Server 2003 DHCP server - Does not release IP Addresses
- From: Felix
- Re: Windows Server 2003 DHCP server - Does not release IP Addresses
- From: OzPacific
- Re: Windows Server 2003 DHCP server - Does not release IP Addresses
- From: Felix
- Windows Server 2003 DHCP server - Does not release IP Addresses
- Prev by Date: Re: File Screens and Email Alert problems
- Next by Date: file in use
- Previous by thread: Re: Windows Server 2003 DHCP server - Does not release IP Addresses
- Next by thread: Re: Windows Server 2003 DHCP server - Does not release IP Addresses
- Index(es):
Relevant Pages
|
