Disconnect Net User from Server

I'm using XP Pro on my pc which serve as a server (Server PC). i had created
a shared folder to let others access it.

The pc only allow not more than 9 users to access this Shared folder. Why is
it so?

another problem is that whenever a PC go to the this Shared folder. the
connection of this PC will remain in the Server PC, even after the PC closed
the Shared folder. in the long run, the shared folder will be jammed to 9
users, from there onsward, the shared folder is no longer accessible.

is that a way to connect a user(PC) in the network?

--
Air Lancer

Your problem is that you're trying to use a desktop operating system as a
server. Windows XP Professional Edition only allows ten simultaneous
connections, and there's no way to change this. If you need that many
connections at once then you need a server operating system.

--
Richard G. Harper [MVP Shell/User]
* In fond memory ... Alex, you shall be sorely missed
* http://www.aumha.org/alex.htm



"Air Lancer" chesserhawk-email.yahoo.com.sg wrote in message
...
I'm using XP Pro on my pc which serve as a server (Server PC). i had
created
a shared folder to let others access it.

The pc only allow not more than 9 users to access this Shared folder. Why
is
it so?

another problem is that whenever a PC go to the this Shared folder. the
connection of this PC will remain in the Server PC, even after the PC
closed
the Shared folder. in the long run, the shared folder will be jammed to 9
users, from there onsward, the shared folder is no longer accessible.

is that a way to connect a user(PC) in the network?

--
Air Lancer

As Richard notes, XP Pro has a 10 connection limit.
Re. the 2nd part of your question - Closing the shared folder will not
disconnect the share. To disconnect the share and free a slot you can run
this in a command prompt on the workstation
net use \\computername\sharename /delete or net use X: /delete if a
drive letter was mapped.

(This isn't practical or user friendly if you need more than 10 connections
on a regular basis. Using a server OS would be the way to go.)
--

"Air Lancer" chesserhawk-email.yahoo.com.sg wrote in message
...
I'm using XP Pro on my pc which serve as a server (Server PC). i had
created
a shared folder to let others access it.

The pc only allow not more than 9 users to access this Shared folder. Why
is
it so?

another problem is that whenever a PC go to the this Shared folder. the
connection of this PC will remain in the Server PC, even after the PC
closed
the Shared folder. in the long run, the shared folder will be jammed to 9
users, from there onsward, the shared folder is no longer accessible.

is that a way to connect a user(PC) in the network?

--
Air Lancer

thk a million for the reply. appreciate it!

i found a command: net config server /autodisconnect:x, where x represents
the minutes the server pc will disconnect the connection when the guest pc is
not using/assessing the shared folder.

it works well with Win 98 OS, but for XP, it doesn't work sometimes. i guess
MS know that people will may continue to use this command to avoid using MS
Server OS, so they modify something to the XP OS.

So is there any reason why for XP OS, the command, mentioned above, work
only sometimes.

Is that a command need to be keyed into the guest pc in order for the
autodisconnect command to work well?

Thk for suggesting using MS server OS. I do not want to use MS Server OS,
because my network server (15-16 PCs) is not very heavy, it is just for
transferring of files, there is no sharing of software or printer. At no
time, there will be ten persons transferring files at the same time.



"GTS" wrote:

As Richard notes, XP Pro has a 10 connection limit.
Re. the 2nd part of your question - Closing the shared folder will not
disconnect the share. To disconnect the share and free a slot you can run
this in a command prompt on the workstation
net use \\computername\sharename /delete or net use X: /delete if a
drive letter was mapped.

(This isn't practical or user friendly if you need more than 10 connections
on a regular basis. Using a server OS would be the way to go.)
--

"Air Lancer" chesserhawk-email.yahoo.com.sg wrote in message
...
I'm using XP Pro on my pc which serve as a server (Server PC). i had
created
a shared folder to let others access it.

The pc only allow not more than 9 users to access this Shared folder. Why
is
it so?

another problem is that whenever a PC go to the this Shared folder. the
connection of this PC will remain in the Server PC, even after the PC
closed
the Shared folder. in the long run, the shared folder will be jammed to 9
users, from there onsward, the shared folder is no longer accessible.

is that a way to connect a user(PC) in the network?

--
Air Lancer

thk guys for the replies. appreciate it!

i found a command: net config server /autodisconnect:x, where x represents
the minutes the server pc will disconnect the connection when the guest pc is
not using/assessing the shared folder.

it works well with Win 98 OS, but for XP, it doesn't work sometimes. i guess
MS know that people will may continue to use this command to avoid using MS
Server OS, so they modify something to the XP OS.

So is there any reason why for XP OS, the command, mentioned above, work
only sometimes.

Is that a command need to be keyed into the guest pc in order for the
autodisconnect command to work well?

Thk for suggesting using MS server OS. I do not want to use MS Server OS,
because my network server (15-16 PCs) is not very heavy, it is just for
transferring of files, there is no sharing of software or printer. At no
time, there will be ten persons transferring files at the same time.


"Air Lancer" wrote:

I'm using XP Pro on my pc which serve as a server (Server PC). i had created
a shared folder to let others access it.

The pc only allow not more than 9 users to access this Shared folder. Why is
it so?

another problem is that whenever a PC go to the this Shared folder. the
connection of this PC will remain in the Server PC, even after the PC closed
the Shared folder. in the long run, the shared folder will be jammed to 9
users, from there onsward, the shared folder is no longer accessible.

is that a way to connect a user(PC) in the network?

--
Air Lancer

Air Lancer wrote:
snip

Thk for suggesting using MS server OS. I do not want to use MS Server
OS, because my network server (15-16 PCs) is not very heavy, it is
just for transferring of files, there is no sharing of software or
printer. At no time, there will be ten persons transferring files at
the same time.


With 15/16 PCs, I would not want to manage a workgroup. More than a handful
of computers makes workgroups a pain. You don't even need to use Windows for
a server OS, note - but if you want to, look into SBS2003.

snip