I have this identical problem on a MF269DW. Developed after 4 years of service. Spent 21/2 hours with very helpful support and we could not fix it by uninstalling, reinstalling drivers, updating firmware, initializing settings, etc. The error is NOT ...