Have you checked to see if the library firmware is up to date? It has been a long time but there was a problem in early firmware builds where some network traffic, usually a security scanner probe, could trigger a routine that had a memory leak and eventually after enough probes the library controller would halt.
I haven't heard of any reason that a recent firmware build would have a similar problem but if there were another similar problem the network connection would be my first guess.