I know this is an old thread, but we are having this exact same issue on our 7760. The Network diagnsotics state Packets Jammed ND26. We can then reset the printer and it works, but then the issue returns again.
upgrading to 4.9.6 seems to have fixed the issue.
have been error free for some months now.
havent tried 4.9.10 yet.
I have exerpienced the exact same problem with my 8650MFP printer dropping from the network on a daily basis. It started intermittently back in January, and grew steadily worse. Network diagnostics detected No DNS Response (ND18). Runtime Log stated "No DNS servers configured, can't resulve DNS hostnames or IP address." The only way to resolve it (temporarily) was to reboot the printer. Given that you tried everything, including replacing the printer itself, I decided to look into problem with my Comcast ISP. I searched for "DNS Server Settings Comcast" and came across this webpage: http://www.dnssec.comcast.net/
The first paragraph states, "All Comcast customers will eventually be automatically migrated to our DNSSEC validating servers. If you don't want to wait, you can immediately start using DNSSEC by manually configuring your DNS servers to point to the IP addresses 184.108.40.206 and 220.127.116.11."
I reconfigured my router to the newer DNSSEC server settings, and I believe that fixed the problem. The printer has not dropped connection for nearly a week now and things have been completely stable. Apparently the old DNS settings were only partially working all along and I didn't know it. Perhaps this is the ianswer for other posts on this thread?
I have a similar problem. The 8560MFP in our office will lose connectivity from the network and or lock up during large print jobs. The only fix seems to be shutting down the printer entirely and turning it back on. We've had a certified repair technician come replace the main logic board. We've also updated the firmware and are using the most current drivers. The problem only seems to be getting worse. Any ideas?
what firmware are you on? i see in the rls note of 9.3 this... maybe it can help ?
- lockup from simultaneous cwis/snmp access, network region memory leaks (multiple customer accounts)