DHCP issue / network help needed

Earlier this week we came across a rather perplexing issue with our DHCP.
One of our agents noticed that they were no longer capable of sending /
receiving emails as well as not being able to go online. We had thought it
might of been an issue with our provider but soon noticed that any
workstation with a static IP was unaffected by the problem, which told us it
was something in regards to the DHCP server. While checking the IPs of some
of the workstations Len and I had noticed that one of them had been assigned
the gateway IP as its IP address. I've done some looking around and to no
avail with trying to figure out the why it would have done that.

Currently we have our workstations all set up as Static IPs, and I have
redone the DHCP server settings as well as a fresh install of the DHCP
services and roles on our Windows 2003 Server. I have tried to set the DHCP
back to how it was when we originally installed this server, but everytime it
seems to come across the same problem where a workstation will be given the
Gateways IP as its own or an APIPA address.

If anyone can spare any insight as to what might of caused such a random
problem or what can be done to the DHCP server to get it back up and running
would be greatly appreciated.

If any information is needed I will accomodate as best as possible.

"Nbufalo" <(E-Mail Removed)>wrote:
>
>
> Earlier this week we came across a rather perplexing issue with our DHCP.
> One of our agents noticed that they were no longer capable of sending /
> receiving emails as well as not being able to go online. We had thought it
> might of been an issue with our provider but soon noticed that any
> workstation with a static IP was unaffected by the problem, which told us
> it
> was something in regards to the DHCP server. While checking the IPs of
> some
> of the workstations Len and I had noticed that one of them had been
> assigned
> the gateway IP as its IP address. I've done some looking around and to no
> avail with trying to figure out the why it would have done that.
>
> Currently we have our workstations all set up as Static IPs, and I have
> redone the DHCP server settings as well as a fresh install of the DHCP
> services and roles on our Windows 2003 Server. I have tried to set the
> DHCP
> back to how it was when we originally installed this server, but everytime
> it
> seems to come across the same problem where a workstation will be given
> the
> Gateways IP as its own or an APIPA address.
>
> If anyone can spare any insight as to what might of caused such a random
> problem or what can be done to the DHCP server to get it back up and
> running
> would be greatly appreciated.
>
> If any information is needed I will accomodate as best as possible.
>
>

Hi,

I would suspect that there is a rogue DHCP server on your network, maybe
some Wireless device or a router.

On the affected workstation, run IPCONFIG /all and look at the DHCP server
field.

ThePro

This is the only DHCP in our network, I have checked to make sure that any of
our peripherals are not broadcasting as a DHCP as well. The DHCP server is
not multihomed.

I dont quite understand you when you ask "Does the DHCP release the IP to
the Clients? " The DHCP server was working fine for 9 months prior to this
event. Since the event I have tried to set it back up and the first Client to
connect recieves a working IP address within the scope range but every
subsequent client will recieve the gateway's IP address as its own address
and the dhcp servers address. I hope that answered the last part of your
questions otherwise I will need a little clarification on that one.


"Bob Lin (MS-MVP)" wrote:

> Make sure you have only one DHCP in the LAN. is the DHCP a multihomed
> computer? Does the DHCP release the IP to the Clients? Or this search result
> may help.
>
> DHCP issuesTroubleshooting Windows DHCP. Cannot find DHCP Server. Cause:
> DHCP service is stopped or disable. Authorize the DHCP Server. A DHCP server
> must be authorize ...
> www.chicagotech.net/dhcp.htm
>
> "Nbufalo" <(E-Mail Removed)> wrote in message
> news:01731D0E-A80D-44CD-B960-(E-Mail Removed)...
> >
> >
> > Earlier this week we came across a rather perplexing issue with our DHCP.
> > One of our agents noticed that they were no longer capable of sending /
> > receiving emails as well as not being able to go online. We had thought it
> > might of been an issue with our provider but soon noticed that any
> > workstation with a static IP was unaffected by the problem, which told us
> > it
> > was something in regards to the DHCP server. While checking the IPs of
> > some
> > of the workstations Len and I had noticed that one of them had been
> > assigned
> > the gateway IP as its IP address. I've done some looking around and to no
> > avail with trying to figure out the why it would have done that.
> >
> > Currently we have our workstations all set up as Static IPs, and I have
> > redone the DHCP server settings as well as a fresh install of the DHCP
> > services and roles on our Windows 2003 Server. I have tried to set the
> > DHCP
> > back to how it was when we originally installed this server, but everytime
> > it
> > seems to come across the same problem where a workstation will be given
> > the
> > Gateways IP as its own or an APIPA address.
> >
> > If anyone can spare any insight as to what might of caused such a random
> > problem or what can be done to the DHCP server to get it back up and
> > running
> > would be greatly appreciated.
> >
> > If any information is needed I will accomodate as best as possible.
> >
> >
>

The affected workstations ipconfig /all currently looks like this

Windows IP Configuration

Host Name . . . . . . . . . . . . : *
Primary Dns Suffix . . . . . . . : *.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : *.local

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme 57xx Gigabit
Cont
roller
Physical Address. . . . . . . . . : 00-19-B9-3A-A6-4C
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 69.69.69.253
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 69.69.69.253
DHCP Server . . . . . . . . . . . : 69.69.69.253
DNS Servers . . . . . . . . . . . : 69.69.69.129
69.69.69.11
Lease Obtained. . . . . . . . . . : Thursday, March 12, 2009 2:31:52
PM
Lease Expires . . . . . . . . . . : Thursday, March 12, 2009 3:31:52
PM

The only correctly working client with the dhcps log looks like this :

Windows IP Configuration

Host Name . . . . . . . . . . . . : *
Primary Dns Suffix . . . . . . . : *.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : *.local
*

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : *
Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network
Connecti
on
Physical Address. . . . . . . . . : 00-07-E9-27-33-9D
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 69.69.69.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 69.69.69.253
DHCP Server . . . . . . . . . . . : 69.69.69.129
DNS Servers . . . . . . . . . . . : 69.69.69.129
69.69.69.11
Lease Obtained. . . . . . . . . . : Thursday, March 12, 2009 2:24:08
PM
Lease Expires . . . . . . . . . . : Friday, March 20, 2009 2:24:08 PM

We do have a wireless access point set up on site but it has been disabled
since this issue as to figure out if it was the problem or not.

"ThePro" wrote:

> "Nbufalo" <(E-Mail Removed)>wrote:
> >
> >
> > Earlier this week we came across a rather perplexing issue with our DHCP.
> > One of our agents noticed that they were no longer capable of sending /
> > receiving emails as well as not being able to go online. We had thought it
> > might of been an issue with our provider but soon noticed that any
> > workstation with a static IP was unaffected by the problem, which told us
> > it
> > was something in regards to the DHCP server. While checking the IPs of
> > some
> > of the workstations Len and I had noticed that one of them had been
> > assigned
> > the gateway IP as its IP address. I've done some looking around and to no
> > avail with trying to figure out the why it would have done that.
> >
> > Currently we have our workstations all set up as Static IPs, and I have
> > redone the DHCP server settings as well as a fresh install of the DHCP
> > services and roles on our Windows 2003 Server. I have tried to set the
> > DHCP
> > back to how it was when we originally installed this server, but everytime
> > it
> > seems to come across the same problem where a workstation will be given
> > the
> > Gateways IP as its own or an APIPA address.
> >
> > If anyone can spare any insight as to what might of caused such a random
> > problem or what can be done to the DHCP server to get it back up and
> > running
> > would be greatly appreciated.
> >
> > If any information is needed I will accomodate as best as possible.
> >
> >
>
> Hi,
>
> I would suspect that there is a rogue DHCP server on your network, maybe
> some Wireless device or a router.
>
> On the affected workstation, run IPCONFIG /all and look at the DHCP server
> field.
>
> ThePro
>