Slow Connection with Windows Print Servers

“Help! I’m a print server administrator and I’ve noticed that not only are documents slow to print, but it’s really slow to connect to a shared Windows print queue on our server. Why does this happen and how do we fix it?”

We’ve seen this issue happen many times when Windows Print Spooling Ports are blocked. This issue happens whether or not PaperCut is installed and can affect any Windows print environment.

The Windows Print Spooler service uses a high dynamic TCP port range including ports 49152 through 65535. When these ports are blocked, you may notice delays around 45 seconds when connecting to a shared print queue on the server or when submitting a print job, or when PaperCut redirects a print job from one Windows print server to another (called Cross-server redirection).

This happens because it takes this amount of time before the client fails to connect, and reverts to the range of ports used by Windows Server 2003 (445 and 139).

To confirm, you can open an elevated command prompt window on your Print Server and run netstat -b -n to show which ports the spooler is using. If spoolsv.exe is using 445 and 139, instead of randomly assigned ports 49152 through 65535, then you have found your problem.

The solution is to make sure that ports 49152–65535 are whitelisted on any firewalls between the clients and print server. You may also need to restart the Windows Print Spooler service for the change to take effect.

Check out this article here for a full list of ports used by the WIndows Printing system and PaperCut.

Still have questions?

Let us know! We love chatting about what’s going on under the hood. Feel free to leave a comment below or visit our Support Portal for further assistance.


Categories: Troubleshooting Articles, Print Queues

Comments