network usage

Well, first counterquestion:
why WOULD you like to restrict?

Advanced server counts the number of client _sessions_, not the NET USE capacity they claim. Of course there is a small extra resource claim per share, but it's relatively insignificant.

Now if there really would be a need to restrict: in 98 would be difficult. In XP there is a policy option limiting the number of available drive letters...

Have fun,

- The Netherlands

In this case I need more information, and can provide a few recommendations:

How are your workstations currently mapping drive letters, i.e., do you have a batch file/group policy, or have you manually mapped the drives on each workstation?

When you say "10 or more network drive letter" do you mean 10 drive letters point to the same shared folder on the server?

Answers to those questions will ease troubleshooting.

For the recommendations:

1. With Windows 98, I recommend using a batch file with the NET USE command setup in the users profile in Active Directory on the server.
2. For Windows XP, it is strongly recommended that you use Group Policy along with a VBS logon script (you can find help for creating those all over the internet).
3. Windows 2000 Advanced Server can support several thousand logons depending on licensing as far as I know, so you have no worries there.

Hope that helps!

Ariston Collander
ariston@coxcomputer.com