no not below layer3, it´s a overfloow of table many connections can cause this problem, try this command: nmap -sP -T5 172.16.0.0/8
on linux you will get a table overflow (cache), wait some time and you will get you network running again (i don´t know how to flush arp cache) 2011/2/7 <[email protected]>: > > Comment #6 on issue 122 by [email protected]: failed to write, and not due > blocking: No error > http://code.google.com/p/memcached/issues/detail?id=122 > > I don't know why one might assume the problem is below layer 3 -- or even > outside of memcached itself. > > It's likely to be related to the Windows port itself (which is not something > we built or planned to support in 1.4.4, though we've done a lot of work > since). > > -- Roberto Spadim Spadim Technology / SPAEmpresarial
