When I had a 4000-N, it used to do this every once in a while. Still worked fine (well, as well as you can expect it to!) otherwise - didn't seem to be a serious problem. I just assumed ntl were running some remote tests on the network or something.
Browneggsandham
