After installing Windows XP’s second service pack, users tend to come across the below issues when sending a print job to a network printer:
The issues may happen on Windows XP when users set up an open port in the Firewall on their network connection, and configure scopes of an exception for using Custom list or My network (subnet) only settings in the dialog box titled Change Scope. Note that any of the above-mentioned issues may occur on the OS although print notifications are not disabled in the dialog box of Start Menu and Taskbar Properties. It might be set as hidden or inactive. Follow the below steps to change that, and make notification to show when sending print jobs through a printer shared over the network to a server system.
To access the setting namely Hide Inactive Icons on the notification bar, and see incase your printer is configured as Always hide, follow the steps mentioned below:
For notifications to work remotely, the printer spooler needs an RPC channel from a server system in the network to that of the client. This channel cannot be created in case client does not have print and file sharing ports open, which happens since the Firewall treats such notifications as uninvited network traffic. When the Windows application block network traffic the server system uses polling notifications, which can cause a 20 second delay on other network computers.
For improving the performance and avoiding polling notifications, XP first double-checks the port settings of Firewall. In case the network ports are open, or its value cannot be determined, the server systems open a communication channel with client’s system. If ports are closed or in case opened with limited scope, XP falls to polling notifications. That have limitations, especially balloon notifications do not work.
If you come across printer offline error or other issues while printing on a network printer, contact our printer support professionals to resolve the same.