XP changing allocated IP address

We have set up several sites that we have had to allocated IP addresses. On several occasions after rebooting some PCs the systems have not been able to find the network. With investigation the PCs have gone back to the default XP addresses. One system was allocated 10. numbers while the other 192. . Has anyone else had this problem and how to stop it happening

In article <C65DB897-3F67-48B8-8A8E-D0210D6EABDB@microsoft.com>,
"possumtech" <anonymous@discussions.microsoft.com> wrote:
>We have set up several sites that we have had to allocated IP addresses. On several occasions after rebooting some PCs the systems have not been able to find the network. With investigation the PCs have gone back to the default XP addresses. One system was allocated 10. numbers while the other 192. . Has anyone else had this problem and how to stop it happening

Check for multiple DHCP servers on the network.

If that isn't the cause, the only way I know of that an XP computer
could assign itself a 10. number is if all of these are true:

1. The network connection's TCP/IP properties are configured to obtain
an IP address automatically.

2. The computer is unable to communicate with a DHCP server to get an
address.

3. The "Alternate Configuration" tab has a 10. number set up.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com

>-----Original Message-----
>In article <C65DB897-3F67-48B8-8A8E-
D0210D6EABDB@microsoft.com>,
>"possumtech" <anonymous@discussions.microsoft.com> wrote:
>>We have set up several sites that we have had to
allocated IP addresses. On several occasions after
rebooting some PCs the systems have not been able to find
the network. With investigation the PCs have gone back to
the default XP addresses. One system was allocated 10.
numbers while the other 192. . Has anyone else had this
problem and how to stop it happening
>
>Check for multiple DHCP servers on the network.
>
>If that isn't the cause, the only way I know of that an
XP computer
>could assign itself a 10. number is if all of these are
true:
>
>1. The network connection's TCP/IP properties are
configured to obtain
>an IP address automatically.
>
>2. The computer is unable to communicate with a DHCP
server to get an
>address.
>
>3. The "Alternate Configuration" tab has a 10. number
set up.
>--
>Best Wishes,
>Steve Winograd, MS-MVP (Windows Networking)
>
>Please post any reply as a follow-up message in the news
group
>for everyone to see. I'm sorry, but I don't answer
questions
>addressed directly to me in E-mail or news groups.
>
>Microsoft Most Valuable Professional Program
>http://mvp.support.microsoft.com
>.
>Thankyou for your reply. Sorry I may have not made
myself too clear. The 192 and 10 numbers were allocated.
The systems were not set to obtain IP address
automatically. There is no DHCP servers set as we have
IPAQs accessing W2K terminal services and the program
they run needs the 2K box with a fixed IP address. The XP
machine was the PC that set itself back to a 168 IP
address.