- Aug 23, 2013
- 65
- 0
- 10,660
This problem was presented to me by one of my professors because it only happened after switching from 100Mb cards to Gigabit NICs. The second arp request that comes from the computer being pinged (to send a reply back) doesn't get sent until after the pings have gone through.
I decided to do some testing at home with a couple VMs and see if I could find the cause.
After clearing the arp cache on both machines (arp -d) and pinging I got the same results as my professor, but I can't seem to figure out why.
I did some googling and found someone with a similar issue using linux (I'm using Windows 10), it said something about there being a stale entry within the arp table as well as something called a first probe delay, but I was never able to find any information about either of those things for Windows.
Does anyone know why this might be happening?
I decided to do some testing at home with a couple VMs and see if I could find the cause.
After clearing the arp cache on both machines (arp -d) and pinging I got the same results as my professor, but I can't seem to figure out why.
I did some googling and found someone with a similar issue using linux (I'm using Windows 10), it said something about there being a stale entry within the arp table as well as something called a first probe delay, but I was never able to find any information about either of those things for Windows.
Does anyone know why this might be happening?
Facebook
Twitter
Instagram