NET CONFIG SERVER /AUTODISCONNECT:1 ON WINDOWS 2003 SBS / WINDOWS XP PRO STATION
I Have a group of 7 people in a department that has one shared printer connected to one of the stations in the group of seven. The group is positioned in the building off by themselves, but still connected to the larger network of about 70 stations. (Network is W2003 SBS & Stations are Windows XP Pro SP3)
Quite frequently a user in the group of seven will not be able to print. When researching it, I find that the station sharing the printer can no longer support anymore connections. I KNOW ABOUT THE 10 STATION LIMITATION ON WINDOWS XP.
I run a NET SESSIONS on the PC that shares the printer and find several other PC on the network occupying sessions on that PC. But I only have those in the group of Seven configured to that printer.
I did setup on the PC that shares the printer a startup batch file that runs
NET CONFIG SERVER /AUTODISCONNECT:1
but other stations on the network are still connecting and staying connected for over an hour sometimes two.
So, should I use a different command than the NET CONFIG SERVER...? or is there something that I'm leaving out?
The group of seven should get by with that WinXP limitation, if I could only prevent other stations on the network from connecting to a session on that Print share.
Thanks for your collective help.
Quite frequently a user in the group of seven will not be able to print. When researching it, I find that the station sharing the printer can no longer support anymore connections. I KNOW ABOUT THE 10 STATION LIMITATION ON WINDOWS XP.
I run a NET SESSIONS on the PC that shares the printer and find several other PC on the network occupying sessions on that PC. But I only have those in the group of Seven configured to that printer.
I did setup on the PC that shares the printer a startup batch file that runs
NET CONFIG SERVER /AUTODISCONNECT:1
but other stations on the network are still connecting and staying connected for over an hour sometimes two.
So, should I use a different command than the NET CONFIG SERVER...? or is there something that I'm leaving out?
The group of seven should get by with that WinXP limitation, if I could only prevent other stations on the network from connecting to a session on that Print share.
Thanks for your collective help.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Odd....
Was other machines besides the specified systems making connections to this server? Never would have thought to look at that option in THIS case....
Glad you found it....
Was other machines besides the specified systems making connections to this server? Never would have thought to look at that option in THIS case....
Glad you found it....
Try [HKEY_LOCAL_MACHINE\System
"KeepAliveTime"=dword
"KeepAliveInterval"=dword
If present, try removing it on one, and see if it disconnects..
Actually, I have always used the 'net config server' command for losing mapped drives on the clients.... Might run it to see what they show....