IP address conflict problem with Windows Server 2003

Hello,

I am having a problem with an IP address conflict. I have a domain with
3 domain controllers in it. Two of them are running Windows Server 2003
and one of them is running Windows 2000.

Every computer in the domain is getting their IP address via DHCP,
except one that we are using for beta testing. This one needs to have a
static IP address. We have given it a static IP address of
192.168.0.36.

Everytime we log onto the machine we get the following error:

There is an IP address conflict
with another system on the network

Sometimes the beta computer will talk to the network and sometimes it
won't. I don't why I am getting this error. I have gone into computer
management on the server and looked at the DHCP leases. There is no
other system with an IP address of 192.168.0.36.

On the times when the computer won't talk to the network, running
ipconfig gives an IP of 0.0.0.0

Can this computer be conflicting with itself? If it is what do I do
about it?

Any suggestions would be great.

Only if the machine has two NICs and they are configured with
the same address.
While the beta machine is off attempt to ping the 192.168.0.36
tcp/ip address and see if you get a response. If you do then
run nbtstat -A against that tcp/ip address to get the machine
name / domain name.

"XxLicherxX" <(E-Mail Removed)> wrote in message news:
> Hello,
>
> I am having a problem with an IP address conflict. I have a domain with
> 3 domain controllers in it. Two of them are running Windows Server 2003
> and one of them is running Windows 2000.
>
> Every computer in the domain is getting their IP address via DHCP,
> except one that we are using for beta testing. This one needs to have a
> static IP address. We have given it a static IP address of
> 192.168.0.36.
>
> Everytime we log onto the machine we get the following error:
>
> There is an IP address conflict
> with another system on the network
>
> Sometimes the beta computer will talk to the network and sometimes it
> won't. I don't why I am getting this error. I have gone into computer
> management on the server and looked at the DHCP leases. There is no
> other system with an IP address of 192.168.0.36.
>
> On the times when the computer won't talk to the network, running
> ipconfig gives an IP of 0.0.0.0
>
> Can this computer be conflicting with itself? If it is what do I do
> about it?
>
> Any suggestions would be great.
>