Q My Windows Secondary Print Provider fails to connect to the Application Server and I get the following error message in the Print Provider log:
Sep 02 12:24:41 DEBUG: Error initiating connection - The requested address is not valid in its context. (Error: 10049) [3116] Sep 02 12:24:41 DEBUG: unable to establish TCP connection [3116] What can I do?
This can mean that the Application Server hostname is having trouble being resolved to an ip address (i.e. a DNS issue). It would be worth trying an ip address for the Application Server instead of hostname by updating the configuration file of
[app-path]/providers/print/win/print-provider.conf:
ApplicationServer=[the server's IP address] -–
Articles in this section
- PaperCut Mf - SSL Certificates - Windows
- papercut-mf-ssl-certificates-macos
- PaperCut Mf - SSL Certificates - Windows
- macOS Rosetta transition (end of life)
- User details missing from copy jobs on Toshiba devices in the Administrator interface Job Log
- Performing a Laptop Test for Device and Server Testing
- Restoring deleted printers when upgrading macOS
- Scan, Device Functions or other buttons are missing from PaperCut MFD app
- Printer pulls job from local client deprecation
- Devices End-of-life Policy
Comments
0 comments
Please sign in to leave a comment.