Static IP addresses -- destination host unreachable / request timed out

I have 10+ Cisco switches on an old
Windows 2003 DC that will be upgraded soon.

How can I flush ARP cache/etc so the below .90 static IP works again
or could I just keep .90 unplugged for a few days, let the ARP cache
expire, plug it back up, and it should work ?
o      user needed a static IP and gave a “Request timed out”, showing it was usable
o      turns out something just needed rebooting for it to get assigned the .90 IP
o      changed above user's IP to
o      everything seemed to work
o      below .90 IP has no valid route from the 24.11 Cisco switch since
        router begins sending ARP request packets on its local network,
        asking for the MAC address of a host with an IP address, but is
        confused, therefore .90 IP does not want to work
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

To clear arp cache on a Cisco switch, just type "clear ip arp" on the switch. I have no idea how to help you on the "Today" part without knowing how things connect, what the subnet is (with subnet mask), and how the switch is configured, whether you have routing enabled, etc.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Craig BeckCommented:
Just some info first...
o      user needed a static IP and gave a “Request timed out”, showing it was usable
That's not necessarily the case.  If the device is firewalled and is blocking ICMP (for example) the reply will be "Request timed out" but a device will actually be using the .90 address.  Don't always assume "Request timed out" to mean the IP isn't being used.  Always check the ARP table from a device on the same VLAN/subnet as the host you're trying to ping first.

The ARP entry is refreshed after 4 hours on a Cisco switch, so that's unlikely to be your problem.  As well as that, the ARP entry is refreshed 60 seconds before it expires on the switch, so if it was incorrect it would only be incorrect for 3 hours and 59 minutes at most, unless you still have an IP conflict.

It's most likely a gateway issue at the client side.  Can you ping 24.11 from 24.90?
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Switches / Hubs

From novice to tech pro — start learning today.