Op 29-01-15 om 00:00 schreef Gordon Messmer: > On 01/28/2015 12:12 PM, Patrick Bervoets wrote: >> >> ARPING 192.168.1.15 from 0.0.0.0 br0 >> Unicast reply from 192.168.1.15 [AC:16:2D:72:67:D4] 0.723ms >> Sent 1 probes (1 broadcast(s)) >> Received 1 response(s) >> >> Thanks anyway > > I'm not sure what you mean by "thanks anyway". > > You got a response. There's an IPv4 conflict on your network. That's why you're seeing those delays. If there's no conflict, you should see 0 responses. > Gordon, I'm sorry, I misunderstood you (and arping -D) This was the result of arping on another host; I thought I should see 2 responses in case of an ip conflict. Arping on the troublesome server gives 0 responses. I just tried with a physical console on that server and there I got the same unresponsive behaviour. Does this rule out network related problems? Mark (m.roth) suggested the vms eating up the video bus. (2 vms with an Oracle database) But I'm not sure how I could test that. Patrick