win2003 server sharing

[marc maze]

New Win2003server, 1 win2k workstation called "ws1"
with "user" as primary logon with no password...

server set up as member of workgoup, not domain
controller...hard drive 2nd partition has new share
called "public" with "everyone" permissions set to all
selections...

1. when browsing from win2k wkstation in
neighborhood..can see server...when attempting to open
server message says access denied

2. set up "user" name as a user on the server with
password "user", set up as administrator, power user, and
user. when attempting access from the ws...prompted for
password...will not accept password just enabled at server.

3. changed password for user to "password" thinking the
global security for password length was the problem...same
results...

4. shared the primary partition with default access
rights for "everyone" as the 2nd partition was setup....no
luck...

5. assigned permission to both partitions to power users
and administrators..asa well as the specific
user "user"...same problem....

am i making the situation too complicated???? what am i
missing...

this is a simple workgoup...used for data sharing and for
1 application sharing...all installed and stored on second
partition "pubclic"

thanks...

marc maze
(e-mail address removed)

 

[Dennis van der Meer]

Is the partition, that contains the share, NTFS?
If so then you'll need to also check the file permissions.
Also the share permissions are as of Windows 2003 read-only
by default. If you want people writing to the share then you'll
have to change the permissions.

Since you have a workgroup and no domain the users+passwords are
stored locally on every machine. When presented with a username and
password dialog you'll have to enter the info like: WORKGROUP\Username
and then the password for that user.
To be able to let everyone access the share you can enable the guest
account to allow access to the share.

 

[Michael_L]

I havent setup 2003 but I expect it is similiar to NT4 and
Win 2k when it comes to setting up a "workgroup" network.
On these two OSes it worked best if you setup an account
for each user on the server. The user name and password
on the server should match the logon they use on their
local work station. When setup like this you should not
be asked for a account name and password when accessing an
open share.

I like to map a drive letter to the share to reduce the
number of mouse clicks required to access the server share.

Hope this helps. Good luck.
Michael

 

[learner]

Pardon me, so you just happened to walked into a network "maze"


I may not have the solution, but please let me ask some questions that may
help. Yes, the questions can often be overlooked without causing problems,
but just in case.

When you are prompted for password, is it prompting for that of ws1\user or
that of the 2003 server'?

what is the password policy on your ws1? Lengthwise and complexity.

If your ws1 has "enforce complex password: policy on , I don't think
"password" will cut it but "psWRd78(/" may. That happens to be non word, to
have at least 2 char of each category, consequently should,qualify for
common complexity criterion

Just in case user means something special in the network, even though I
don't think so, how about use user1 or something else instead.

As far as I know the security and permission of W2003 for shares and
resources is much the same as Win XP. the ID of connecting user does not
have to be admin, nor power users but the connecting user must have the
required effective access from the combination of the resource and the
share.

Lastly, if connection still not achieved with all remedies to the above
questions, how about explicit map with explicit ID and password. in
Explorer, click tools, map network drive,...


I think you can make the drive mapping "reconnect at logon"

Good luck
..