Windows Server 2008-based and Windows Vista-based clients do not receive Print Job cancelation notifications, and multiple print jobs may be pending in the print queue

When you configure a Windows Server 2008-based or a Windows Vista-based computer to use a public network, the eventing port of network discovery is closed. This port is used by some Windows Services on Devices printers to send status information. Because this port is blocked, the client does not receive JobEndStateEvent notifications, such as Print Job cancelation notifications. In this scenario, multiple print jobs may be pending in the print queue. Or, a print job may not be canceled, and the print queue is not released for more printing.

This problem occurs for one of the following reasons:

• The client's network location is set to public.
• The client's network discovery is turned off.
• TCP port 5357 is not enabled in Windows Firewall.

Warning This workaround may make a computer or a network more vulnerable to attack by malicious users or by malicious software such as viruses. We do not recommend this workaround but are providing this information so that you can implement this workaround at your own discretion. Use this workaround at your own risk.

To work around this problem, use one of the following methods, as appropriate for your situation.

Method 1: Use a network location that is not set to public

Note If your computer is a member of a domain, you cannot change the network location type because it is controlled by the network administrator. For more information, contact the network administrator.

1. Log on to the network.
2. Open the Network and Sharing Center. To do this, click Start
   Collapse this imageExpand this image

   
   , type Network and Sharing Center in the Start Search box, and then click Network and Sharing Center in the Programs list.
3. Click Customize, and then click Private.
   
   
   Collapse this imageExpand this image

   
   If you are prompted for an administrator password or for confirmation, type your password, or click Continue.
   
   Note When you click Private for a network location, it permanently changes the firewall configuration to enable communication. This can be a security risk.
4. Click Next, and then click Close.
   
   For more information about how to select a network location in Windows Vista, visit the following Microsoft Web site:
   http://windowshelp.microsoft.com/Windows/en-US/Help/6ddfa83c-01c8-441e-b041-1fd912c3fe601033.mspx (http://windowshelp.microsoft.com/Windows/en-US/Help/6ddfa83c-01c8-441e-b041-1fd912c3fe601033.mspx)

Method 2: Turn on network discovery

1. Click Start
   Collapse this imageExpand this image

   
   , type Network and Sharing Center in the Start Search box, and then click Network and Sharing Center in the Programs list.
2. If network discovery is off, click the arrow button to expand the section, click Turn on network discovery, and then click Apply.
   
   
   Collapse this imageExpand this image

   
   If you are prompted for an administrator password or for confirmation, type your password, or click Continue.

For advanced computer users

This section is intended for advanced computer users. If you are not comfortable performing advanced troubleshooting, you might want to ask someone for help or contact support. For information about how to do this, visit the following Microsoft Web site:

Advanced users method 1: Enable TCP port 5357 in Windows Firewall

1. Click Start
   Collapse this imageExpand this image

   
   , click Run, type wscui.cpl, and then click OK.
2. Click Windows Firewall.
3. On the Exceptions tab, click Add Port.
4. In the Add a Port dialog box, type the name that you want to use for the port exception in the Name box, type 5357 in the Port number box, and then click TCP.
5. Select the scope options that you want to use for this exception, and then click OK.
6. On the Exceptions tab, notice that the new exception is listed. To enable the port, click to select the check box next to the exception, and then click OK.

Advanced users method 2: Create firewall rules for the Web Services on Devices application

Printer manufacturers can work around this problem when they install the device. To do this, the printer manufacturers can use Windows Firewall together with Advanced Security APIs to create firewall rules that apply to their Web Services on Devices applications. Specifically, the Add method of the INetFwRules interface can be used to add a new firewall rule. For more information, visit the following Microsoft Web site: