Re: win2003 File Server in a Workgroup -- User Access

Hi,

Create a new user and change all the steps from the previous posts:

1. Click Start/Run, type gpedit.msc

2. Open Computer Configuration\Windows Settings\Security Settings\Local
Policies\Security Options

3. Change the following key:" Network Access: Sharing and Security model for
local accounts" to "Classic"

4. Computer Configuration/Windows Settings/Security Settings/Local Policies.
Under User Rights Assignments check the following keys:

-Access this computer from network (Your new account or everyone group
should be in)

-Deny access to this computer from network (remove Everyone group)

Under the security options take a look at this key:

-Accounts: Limit local account use of blank passwords to console logon only
(disabled)-only if local administrators do not have passwords

-Network access: Do not allow anonymous enumerations of SAM accounts
(enabled)

-Network access: Do not allow anonymous enumerations of SAM accounts and
shares (disabled)

-Network access: Allow anonymous SID/Name translation (disabled)

-Network access: Let everyone permission apply to the anonymous user
(disabled)

After this change all the users will have to enter username and password
(one you created), if you want the user to authenticate as themselves,
create accounts for all users on Win 2003 machine.

Regards,

Anton Pegan

"NuBee" <NuBee@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:F60D4636-806B-4B94-AA5D-6A5D6820408C@xxxxxxxxxxxxxxxx

Thank you ... that worked just fine. There was no autentication required
when a user clicks on the network folder/drive (I mapped to the shared
folder
so it looks like a network drive to the user).

However, I want to restrict access to each shared folder/drive. I want
to
require authentication. What do I do to set this up???
--
NuBee


"Anton Pegan" wrote:

Hi,

Run gpedit.msc again and take a look at the following keys:

Computer Configuration/Windows Settings/Security Settings/Local Policies.
Under User Rights Assignments check the following keys:

-Access this computer from network (Guest should be in)

-Deny access to this computer from network (remove Guest and Everyone
group)

Under the security options take a look at this key:

-Accounts: Limit local account use of blank passwords to console logon
only
(disabled)-only if local administrators do not have passwords

-Network access: Do not allow anonymous enumerations of SAM accounts
(enabled)

-Network access: Do not allow anonymous enumerations of SAM accounts and
shares (disabled)

-Network access: Allow anonymous SID/Name translation (disabled)

-Network access: Let everyone permission apply to the anonymous user
(disabled)

Also check the permissions that you set on your shared folders (give
everyone read permissions).

Regards,

Anton Pegan

"NuBee" <NuBee@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:1F8827D5-E4E1-417C-BF31-E137E1DE85E9@xxxxxxxxxxxxxxxx
I did just as you said and the situation has changed to --> I:\ is
not
accessible. Access is denied. What do I do now????
--
NuBee


"Anton Pegan" wrote:

Hi,

If it is not necessary for the users to enter a valid username and
password,
you can try using the guest account. To do that, follow these steps:

1. Click Start/Run, type gpedit.msc

2. Open Computer Configuration\Windows Settings\Security
Settings\Local
Policies\Security Options

3. Change the following key:" Network Access: Sharing and Security
model
for
local accounts" to "Guest Only"

4. Open Local users and groups and enable the Guest account

5. Restart the computer

If the steps above do not help, please post the full error text or its
number.

Regards,

Anton Pegan

"NuBee" <NuBee@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:998AB314-0F2F-4844-B958-95FCA6FE56B6@xxxxxxxxxxxxxxxx
I have a small office setup with 4 winXP workstations connected
(wireless)
to
a Win2003 File server SP1, all in a workgroup. I have created
several
shared
folders on the Win2003 file server. When I access these shared
folders
from
a winXP machine, double-click the folder, it asks for username and
password,
as long as I log-on as an administrator or power user, I can access
the
shared folders on the win2003 file server from the winXP machines.

On the win2003 server, using Computer Management mmc, I created a
new
user
named jjones, in the Local Users and Groups -- Users folder. When I
use a
winXP machine and try to access the the shared folders on the
win2003
file
server, it won't let me have access -- says user not known or
password
is
wrong.

What might I be overlooking and how might I fix it?

Thanks for any help ...
--
NuBee








.

Relevant Pages

  • Re: encyption?
    ... protect some folders. ... This is only possible when separate user accounts are used, as far as native XP tools are concerned. ... Add passwords to the accounts and only give him the passwords to the *limited* accounts you want him to have. ... Changing the password from outside the account, such as from a boot/reset CD will permanently remove decrypt access to encrypted files and folders. ...
    (microsoft.public.windowsxp.general)
  • Re: Password for spcific folder
    ... It is done using grants to accounts, ... passwords on the folders. ... and at the NTFS level. ...
    (microsoft.public.win2000.security)
  • Re: encyption?
    ... protect some folders. ... This is only possible when separate user accounts are used, ... Add passwords to the accounts and only give him the passwords to the ... encrypted files can probably be deleted by careless users. ...
    (microsoft.public.windowsxp.general)
  • Re: password expiration policy for admin and system accounts ?
    ... policy that Admins manually reset these important account passwords every ... You can still have the passwords set to never expire, ... > Privileged accounts should be the most, not the least, well guarded. ...
    (microsoft.public.security)
  • Re: password expiration policy for admin and system accounts ?
    ... policy that Admins manually reset these important account passwords every ... You can still have the passwords set to never expire, ... > Privileged accounts should be the most, not the least, well guarded. ...
    (microsoft.public.win2000.security)