"Ace Fekay [Microsoft Certified Trainer]" wrote:

> "dirtyBit" <dirty***@discussions.microsoft.com> wrote in message
> news:014946B9-369B-4E74-9C66-A51428514442@microsoft.com...
> > Hi,
> >
> > My DHCP server (Win2003) has stopped handing out addresses.  Basically
> > when
> > using a packet sniffer, I can see only Discover packets on the wire but no
> > Offers.  The strange thing is that when I look at statistics on the dhcp
> > mmc
> > it states that offers are being sent.  So DHCP "thinks" it's working but
> > there is nothing on the wire.  Anyone have any clues.  Thanks.
>
>
> diryBit,
>
> It's kind of tough analyzing this without additional info regarding any
> errors in the eventLogs, if there are any firewalls in place, any services
> disabled on the client side or the server side (perhaps for security
> reasons) that may be required, etc. Are the offers on the interface the DHCP
> client is on? How about the client side, what errors show up? If you restart
> the DHCP Server service, does it start working again?
>
>
> --
> Ace
>
> This posting is provided "AS-IS" with no warranties or guarantees and
> confers no rights.
>
> Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSA Messaging, MCT
> Microsoft Certified Trainer
> ace***@mvps.RemoveThisPart.org
>
> For urgent issues, you may want to contact Microsoft PSS directly. Please
> check http://support.microsoft.com for regional support phone numbers.
>
> "Efficiency is doing things right; effectiveness is doing the right
> things." - Peter F. Drucker
> http://twitter.com/acefekay
>
>
>

"dirtyBit" <dirty***@discussions.microsoft.com> wrote in message
news:C2ACD00C-5597-4769-B390-AEDA094DB222@microsoft.com...
> First of all thanks for replying I really appreciate it.
> I believe I have tried all the obvious basic things like, Make sure it's
> authorized, service is running, no packet filtering enabled, no firewall,
> etc.  This is not just one client not getting addresses, it's all of them.
> I've been using static addresses as a temp. fix.  When I plug another
> server
> on the network computers recieve addresses just fine.  It's just this one
> server.  I'm starting to think it's a bad nic card.  There are no errors
> in
> the log files becuase DHCP thinks (or maybe it is) sending out Offers but
> they never make it on the wire.  I just find it strange that a bad nic
> would
> kill DHCP Offers but everything else works just fine.

"Ace Fekay [Microsoft Certified Trainer]" wrote:

> "dirtyBit" <dirty***@discussions.microsoft.com> wrote in message
> news:C2ACD00C-5597-4769-B390-AEDA094DB222@microsoft.com...
> > First of all thanks for replying I really appreciate it.
> > I believe I have tried all the obvious basic things like, Make sure it's
> > authorized, service is running, no packet filtering enabled, no firewall,
> > etc.  This is not just one client not getting addresses, it's all of them.
> > I've been using static addresses as a temp. fix.  When I plug another
> > server
> > on the network computers recieve addresses just fine.  It's just this one
> > server.  I'm starting to think it's a bad nic card.  There are no errors
> > in
> > the log files becuase DHCP thinks (or maybe it is) sending out Offers but
> > they never make it on the wire.  I just find it strange that a bad nic
> > would
> > kill DHCP Offers but everything else works just fine.
>
> You've done a lot of homework on it. At least that's good. If you think it's
> a bad NIC, can you remove it, or disable it, and install another known
> working NIC to verify your suspicions?
>
> Ace
>
>
>
>

"dirtyBit" <dirty***@discussions.microsoft.com> wrote in message
news:95002C51-8821-4F39-A0E7-F4635D18BCDD@microsoft.com...
> Ok I figured it out.  It's not a bad NIC.  Group Policy is to blame.  The
> server I plugged in wasn't part of the domain so it was working fine.
> When I
> added the server as a second DC it stopped working as well.  Apparently
> IPSec
> policy was blocking DHCP.  Even though it was set for "request encryption"
> it
> blocks communication because it's broadcast traffic and the workstation
> does
> not yet have an IP.  To fix it, I added an exception on the DC IPSec
> policy
> that allows UDP traffic from DC to Any on port 67.  Wow.  This was driving
> me
> crazy.  I'm glad it's over.  Thanks for taking the time to look into this.