IP Conflict
Windows is giving me a warning that I have an IP conflict on a network that is totally static. Even though it says there is a conflict the IP address in question cannot be pinged. When scanning for all live IP addresses the IP address in question is listed as "Dead". This IP Address is for a server and changing it will cause a great deal of problems.
I have attempted to use IPCONFIG /RELEASE /RENEW to no avail. I've changed the IP Address and then changed it back to no avail. I've rebooted the server to no avail.
How can there be an IP conflict? How do I remove that conflict? Can there be such a thing as a bad IP Address?
I have attempted to use IPCONFIG /RELEASE /RENEW to no avail. I've changed the IP Address and then changed it back to no avail. I've rebooted the server to no avail.
How can there be an IP conflict? How do I remove that conflict? Can there be such a thing as a bad IP Address?
After the above steps (I do similar), run IPCONFIG. What IP do you get? 169.254.x.x is the auto configuration IP indicating no IP.
Do you know the network card is good?
Do you know the network card is good?
"...on a network that is totally static."
"I have attempted to use IPCONFIG /RELEASE /RENEW to no avail. "
These two things are mutually exclusive. Is the server configured with a static IP or not? Is DHCP in use on the network or not?
"I have attempted to use IPCONFIG /RELEASE /RENEW to no avail. "
These two things are mutually exclusive. Is the server configured with a static IP or not? Is DHCP in use on the network or not?
ASKER
When attempting to run the ipconfig /release /renew I get the error: The Operation Failed As No Adapter Is In The State Permissable For This Operation.
The ipconfig /flushdns & netsh winsock reset did nothing
The ipconfig /flushdns & netsh winsock reset did nothing
Try either reinstalling the driver for the Network card, or try a new Network card.
ASKER
The network is configured with static IP's. DHCP is not in use.
Also run:
netsh winsock reset catalog
netsh int ip reset reset.log
Then reboot
netsh winsock reset catalog
netsh int ip reset reset.log
Then reboot
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
For troubleshooting purposes, could you try to change the server's IP to something else to verify connectivity?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
If you have access to the network switch, display the arp table and that should show you what has the Conflicting IP Address.
If you are using managed switches where the ports have been set differently than the PC's NIC's you can also get strange issues like that. Make sure duplex settings on the switch and the connected NIC are exactly the same. Usually everything set to "Auto" on both sides works best and avoids such issues.
ASKER
Here is/was the problem. There was indeed an IP conflict but still unable to figure out why. There was a printer/copier/fiery that I unplugged from the network and this allowed the server to connect to the assigned IP. My confusion comes from not being able to ping that address before I unplugged it from the fiery. Why wouldn't the fiery have been able to be pinged? The Fiery was also purported to have a different IP Address anyway. So - a little egg on my face but confusing nonetheless.
The fiery may be set to not respond to ICMP.
Glad you got it figured out.
Glad you got it figured out.
I always do:
ipconfig /release
ipconfig /flushdns
netsh winsock reset
Then reboot your PC and see if it picks up a new IP. You may also want to check on your server DNS to see if that IP is listed and what against - delete if no longer in use.