DHCP info to XP Clients

I have a network all on one subnet: 192.168.0.xx. We have several Server
2003 servers and over a hundred WIndows XP client, some on SP1 and some on
SP2. Two of the servers are running DHCP server, offering addresses in the
subnet. The scope options include pushing the DNS server addresses of
192.168.0.8 & .9. Things were working great until.....

..... several PCs stopped finding things on the network. IPCONFIG /ALL
showed that their IP address, subnet, subnet mask and gateway all were
correct, but their DNS server was incorrectly pointing to 192.168.1.1. We
also noticed some PCs whose DNS was correct immediately after bootup, but
then soon changed to the incorrect value.

Investigation showed that we had a broadband/wireless router on the network
that had reset itself to its factory defaults, which are IP=192.168.1.1 and
DHCP turned ON. Once we removed this from the network, our problems went
away.

Here's my question: How is a PC able to get the correct DHCP information
from a Server 2003 DHCP server, but then get DNS info from a different DHCP
server?

DHCP has several different commands. When a machine boots, it broadcasts
to find a DHCP server. When a DHCP server replies, it accepts its offer and
loads the values given.

After it is on the network it can use DHCPINFORM messages rather than
DHCPDISCOVER to obtain info from a DHCP server. This info will overwrite the
previous data.

This method is often used for remote clients so that they get their
settings from the DHCP server after connection. At connection time, they get
their settings (WINS and DNS) from the RRAS server directly.

"R Harrigill" <rharrigillatmsndotcom> wrote in message
news:(E-Mail Removed)...
>I have a network all on one subnet: 192.168.0.xx. We have several Server
>2003 servers and over a hundred WIndows XP client, some on SP1 and some on
>SP2. Two of the servers are running DHCP server, offering addresses in the
>subnet. The scope options include pushing the DNS server addresses of
>192.168.0.8 & .9. Things were working great until.....
>
> .... several PCs stopped finding things on the network. IPCONFIG /ALL
> showed that their IP address, subnet, subnet mask and gateway all were
> correct, but their DNS server was incorrectly pointing to 192.168.1.1.
> We also noticed some PCs whose DNS was correct immediately after bootup,
> but then soon changed to the incorrect value.
>
> Investigation showed that we had a broadband/wireless router on the
> network that had reset itself to its factory defaults, which are
> IP=192.168.1.1 and DHCP turned ON. Once we removed this from the
> network, our problems went away.
>
> Here's my question: How is a PC able to get the correct DHCP information
> from a Server 2003 DHCP server, but then get DNS info from a different
> DHCP server?
>