Static IP address still issues DHCP Request - XP Pro

Did you tried to disable the DHCP client services on the XP machines ?

fmarshall: I manage the IP addresses for the network, so I feel pretty confidant that I do not have an IP conflict.

Eric_Gennaoui:  I turned off the DHCP Client Service and the request is still being sent out.  The DHCP Client Service is running on all systems, the ones that don't send the request an the ones that so.

Thanks for both of the suggestions.

I understand that you manage the IPs.  However, you also said:

"but the pcs that a coworker setup send out the requests even though they have been configured with a static IP."

And, I *have* seen this happen with the only thing needed was to get rid of the conflicting IP.  
So, I'd encourage you to make sure.  Even a typo could cause a well-managed system to do this.

fmarshall:  Have checked once again and no duplicate IPs.  Have checked numerous ways and have even turned off one of the PCs.  Then ran ping and arping (Linux) and can not detect any dups.

Eric_Gennaoui: The service is up and does not seem to make a difference either way on the pcs sending dhcp requests.   Have tried to determine if some software app is sending the requests and it appears that there is nothing different on the PC sending and the PC not sending.

I may have a solution to this issue.  On the PCs that were sending out the DHCP Requests I went into the TCP properties and told it to use DCHP and rebooted. When the PC came up a then reassigned the static IP address and rebooted once again.  THe DHCP Requests have stopped.  I'm not sure if this exact sequence of events is required, but so far it seems to have fixed this issue.

Are you saying that you assigned manually the SAME IP that had been assigned by DHCP?  That would be very understandable.  Presumably DHCP is not in the same range as the static addresses you allow.  But then, this would break that self-imposed rule even as an expedient.

But, if you're saying that you assigned manaually the SAME STATIC IP that you'd tried before then that's not so understandable.  Then I might wonder if there's a rogue DHCP service running somewhere on the network.

Pinging won't guarantee that an IP is not in use.  At least one reason is because not all clients are set to respond to PING.  That depends on a variety of things including the PC's firewall, etc.  So, if it tells you that an IP is in use then that's great but it's not conclusive.

What I'm saying is that the PC was originally setup with a static IP, but it still broadcast DHCP requests.  So, I told the PC to get a DHCP Address by selecting the radio button in the TCP/IP properties that states "Obtain an IP address automatically" and rebooted.  No DHCP address was obtained during the reboot since we have no DHCP server.  I then selected "Use the following IP address:" in the TCP/IP properties and set the IP to the same one the PC was using before.  Now no DHCP requests are coming from the PC.  Maybe by toggling the DHCP settings, it repaired a registry setting.  Hopefully that clears the confusion up on the steps that was taken.

I understand that pinging alone will not verify a pc is using an IP.  Other steps were taken including but not limited to using an arping from a Linux machine.  Arping does not use icmp request.  This is just another method of trying to see if a pc is alive and on the network.

Toggling is often a good idea!  Glad you solved the problem.

Although the suggested solutions did not directly solve the issue, they helped greatly in the troubleshooting process.  Thanks for the suggestions.