>Hi,
>
>I don't want to use API (if it wouldn't be necessary).
>
>I created new user on W95 machine and shared folder on W2K machine, but when I want to set permission for access the folder on W2K,I can not see the user from W95 machine.
>
>Where is the mistake?
>(W95 machine is on and user is logged.)

(1) The user account must exist on the W2K machine
(2) The password for the user must match the password used when the user logs into the Win95 machine
(3) The user must be granted rights (Permissions) to the share on the W2K machine
(4) The userid and password will be case-sensitive
(5) Unless in a domain, the account exists only in context to the single local machine. If another Win2K machine exists, the user will not exist on it unless you create that user explicitly on that machine. In a domain environment, you can create the user in the context of the domain, and then grant domain-level users rights to shares on members of the domain.

IE:

Create a user on the Win2K machine (I'll assume the name of the machine is Win2KBox)

UserID: Bozo
Password: clown

Create a share Foo on Win2KBox, and grant the local user Bozo rights to share Foo.

Log onto a Win95 machine with the userid Bozo, with the password clown - you should now be able to access the shared folder with the command:

NET USE S: \\Win2kBox\Foo

This will map the shared folder as the local drive S:, or you can use the GUI tools through Network Neighborhood or Explorer to access the share.

Log onto another Win95 box with the userid Bozo, but with a different password (or no password.) The shared folder will not be accessible (incorrect password).

Log onto another Win95 box with the userid Chuckles and the password clown - the shared folder will not be accessible (incorrect userid).

If you've logged in on an unsupported name, but still want to use the share, you can use the NET USE command to specify a username and password:

NET USE S: \\Win2KBox\Foo clown /USER:Bozo

The extra arguments override the default password and userid used to log into the workstation with the specific ones needed to access the share. The API calls mentione and password override values, and would not force you to run a command line executable to make the connection.

You can create as many users as necessary on the Win2K system; just remember that the Win95 user must have the same userid and password used on the Win95 machine as one defined on the Win2K machine to be authenticated, and that the user must be granted access rights to the share on the Win2K machine - it's probably easiest to create a local group, make the desired users members of the local group, and then grant rights to the group as a whole.