Network Connection Limit on Windows XP

I look after a small network of usually 4, sometimes 5 users. connected to a Windows XP Pro server. A couple of the users have had problem connecting to the network shares with error message stating that no further connections can be made to the server....
Having checked the connection status in "Shares"  I see
the following...Data Share 1    4 connections
                        Data Share 2    3 connections
                         IPC$                 7 connections
I restart the PC and all is well for a few days
I assume it's the IPC$ shares that are the problem...

Is there anything I can do to limit the IPC$ connections
There are no remote desktop sessions or remote administration taking place.
This really is frustrating.  Any Help Please

Blaggy3780Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Darr247Commented:
See http://support.microsoft.com/kb/328459

It says to use NET SESSION to view open connections, and those rows with the entry under USER NAME blank are considered 'null sessions' - those count as a connection on the license count limit.

There are essentially 2 different resolutions given, one restricting null session connections using either group policy or a direct registry edit, and the other by removing print shares on the machine exhibiting the problem.


You could also check the
net config server /autodisconnect:[time in minutes]
setting. If you just run
net config server
by itself it should show what the idle time is currently set to. The default is 15 minutes, but according to http://support.microsoft.com/kb/314882 that value is supposed to be self-tuning... once the /autodisconnect parameter is used it's no longer self-tuning, so maybe someone ran net config server /autodisconnect:300 or something.

If autodisconnect is not killing the IPC$ shares, you may have found a bug. :-|
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Blaggy3780Author Commented:
Thanks for your help.  I removed print sharing on the XP Server and this has stopped the problem.... Thanks
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Networking

From novice to tech pro — start learning today.