Discussion Locked

Getting XP to release named pipes

0 helpful

2 replies

by be1garath May 26, 2005 last reply Jun 7, 2005

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We have a situation with XP Pro running as a small file/print server, when a shared printer is setup on a client to use the share the connection will not release until you either remove the share or log off. When logging back on or recreating the share the connection is re-establised. This is fine until all the concurrent connections are used up, it seems that the printer shares using the pipes/spoolss does not follow the usual disconnect time out as normal shares. Can anyone shed any light on this please?

2 replies

by blackcurrant May 27, 2005

I don't know how you can do this, but I do know there is a 10 connection limit placed on the number of concurrent connections that may be made at any one time. You can increase this limit to 50. See the last response the this question https://www.techrepublic.com.com/5208-6287-0.html?forumID=47&threadID=169651

Hope this helps

Good luck

by be1garath Jun 7, 2005

Hi Blackcurrant, the solution offered did not solve my problem can you supply the senario you have? I feel the way this is configured is not the same as yours and we may have a slightly different problems.

This discussion is closed to new replies.

2 replies

Trending Windows Forum posts

How are you using AI agents in your daily workflow

Is WSL still relevant in 2026?

What is the most annoying Windows problem you have faced and what finally fixed it

Windows 11 Application Crashing and System Performance Issues

i need help in transferring my bulk emlx files