Stop Vista from creating connection with XP Print Server (\Pipe\spoolss)

By eppa.rust ·
I am having issues with a Windows XP machine used as a print server. The Vista machines on the network are grabbing the ten open connections (listed as \PIPE\spoolss). Even after net sesssion /delete /y the Vista machines return (usually within a matter of 10-15 seconds).

The Windows XP machines on the network histrically connect to print and then close the sessions. Only the Windows Vista machines on our network grab the connections without needing to print. Also, if I turn off net discovery, the Vista machines do not grab the connections. Instead they leave open sessions after printing, which keeps the XP machines from gaining access.

What I would like to know is how do I get the Vista machines to stop grabbing and/or holding the 10 connections.

I have tried lowering the autodisconnect time.
I have tried most of the suggestions for working around the 10 connection limit.

The trouble is not the limit, but the fact that the Vista machines are grabbing the connections regardless of a need to print.

Does anyone have any suggestions.

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Answers

Collapse -

same here

by jesse In reply to Stop Vista from creating ...

I am seeing this same problem, and eventually it causes the printer share on the xp machine to become unavailable. I have not been able to find a solution so far. Anybody out there have an answer?

Collapse -

Is this any good for you.... Or not....

by Peconet Tietokoneet In reply to Stop Vista from creating ...

Set Permissions on a Shared Resource

A shared resource is a resource that is made available to network users, such as folders, files, printers, and named pipes. It can also refer to a resource on a server that is available to network users. When you share a resource, you use Share permissions instead of NTFS permissions.

Share permissions apply only to users who gain access to the resource over the network. They do not apply to users who log on locally, such as on a terminal server. To restrict access to objects for users who log on locally, set NTFS permissions on the Security tab of the object's Properties page.

Setting permissions on a shared resource
There are two methods to set permissions on a shared resource, depending on the resource type.

Using the File Sharing Wizard to set permissions of a file or folder

You can start the File Sharing wizard by right-clicking the file or folder, and then clicking Share.

The wizard allows you to select the user and group which can share the file or folder, and allows you to set permissions on the file or folder for each user or group.

Using Windows Explorer to set permissions on a resource

You can use Windows Explorer to set permissions through the Share option or through the Properties page on a resource. When you right-click the object, selecting the Share or Properties option displays the Properties dialog box. Permissions can be set or modified by using the Advanced Sharing button on the Sharing tab.

Additional considerations

To open Windows Explorer, click Start, point to All programs, point to Accessories, and then click Windows Explorer.

You can use File Sharing to manage shared resources on both local and remote computers. With Windows Explorer and the command line, you can manage shared resources on your local computer only.

When permissions have been assigned both to the shared resource and at the file system level, the more restrictive permission always applies.

It is usually easier to assign permissions to groups and then add users to groups, rather than assigning identical permissions to individual users.

If you change permissions on special shared resources, such as ADMIN$, the default settings may be restored when the Server service is stopped and restarted or when the computer is restarted. Note that this does not apply to user-created shared resources whose share name ends in $.

Related Discussions

Related Forums