MAC OS X Popup Client Error: "Remote host did not accept control file (54)"
- 02 Apr 2024
- 1 Minute to read
- Contributors
- Print
- DarkLight
- PDF
MAC OS X Popup Client Error: "Remote host did not accept control file (54)"
- Updated on 02 Apr 2024
- 1 Minute to read
- Contributors
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
When printing on OS X machines that have Popups installed, the Mac Printer box displays:
"Sending control file (xxx bytes)"
then after some seconds:
"Remote host did not accept control file (54)"
The Pharos Popup Client never comes up.
The most likely cause of this problem is that the Macs have multiple DNS records.
Symptoms:
1) Some Macs work, and some don't
2) Error message "Remote host did not accept control file"
More details:
"Remote host did not accept control file (54)", is a known problem for Apple.
In short, if a machine has multiple DNS records in the site's DNS, printing from Mac OS X is likely to fail with the given error. This is because the OS X printing system sends up all of the machine's host names, when in fact the server only expects one. The problem will occur whether or not Popups is installed (when printing via LPR/LPD) .
Currently, the only fix is to go through DNS and remove duplicate machine records, then restart the affected Macs (to refresh the client DNS caches). However, this bug has been reported to Apple and will be fixed in an upcoming version of the operating system.
Was this article helpful?