Server 2003 Enterprise File Server and Workgroup access to shares...

Posted on 2009-04-13
Last Modified: 2013-11-29
Well let me try to begin with...

I've come in to help a friend with their business network.  The previous admin left their place in a mess....  Essentially, they have a server which I had to clean and reinstall Windows Server 2003 Enterprise on.  They want to use this server as strictly a file server and repository for documents.

This is a very small office.  Currently 5 users with NO intent of growing beyond 10 people.  The group doesn't want Active Directory installed because they do not want to hire a dedicated admin.  They are using a WORKGROUP model.  (Yes, I've tried to talk them into using AD but they are not interested). 2003 Enterprise was a major un-needed upgrade but the last admin convinced them to get it.

Anyway, I re-installed the OS on this server, set it up as a file server and shared 3 folders out as requested.  All the house PC's are using Win XP Pro.  The house PC's can see the server - we'll call it:  NAME-FS  listed in network places and under Workgroup but cannot access it.  When they try they get an error saying that they don't have permission to log on to this device.

I went into the local security settings on the Server (which can see everybody in the workgroup by the way), and tried to add the accounts for the 2 house machines into the local security group list but received an error for that.

I can see the house PC's from the server, and can log into their machines with their local login permissions.  Keep in mind I'm dealing with local logins and no AD.  I'm trying to figure out why or what permissions I'm missing to prevent the house PC's from accessing the NAME-FS file server.  What am I missing?  I just need some ideas to get me rolling...
Question by:krazykc22
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
  • 4

Author Comment

ID: 24134072
Solved the initial problem with being able to access shared folders.  All machines can see the folders now.  It was an issue with file and folder sharing not being selected on the server and windows firewall not allowing access through a TCP port to the server.  SOLVED....

NEW ISSSUE....  The clients want 3 shared folders on the D: drive of this new file server... I have those set up and people can see them.  The only problem is now that they want a seperate password on each shared folder.  They don't want to deal with permissions to do this, just a password access.  This is a workgroup internal to the organization where passwords on machines are NOT changed and not shared from person to person.   They want me to set up a different password to access each of the three shared folders on the D: drive.  I see no way to do this...any ideas...?

Accepted Solution

RobDating earned 500 total points
ID: 24135303
You should be able to create 3 new users on the server (that do not exist on any of the client PC's) so for example:

Folder 1, create "user one" with a password
Folder 2, create "user two" with a password
Folder 3, create "user three" with a password

now on the sharing permissions for instance on folder 1 only allow "user 1" access. so when Bob who signs into his PC as Bob try's to access Folder 1 he has to enter "user one" as his user name along with the password to "user one's" account.

Author Comment

ID: 24135732
I think I understand.  So in essence, each person, when trying to access the share will have to enter the given password.  If the shares are already created and the workgroup computers have open access to them right now, how can I button down that open access to set this up correctly?  Do I have to delete the shares and start over?
Simple, centralized multimedia control

Watch and learn to see how ATEN provided an easy and effective way for three jointly-owned pubs to control the 60 televisions located across their three venues utilizing the ATEN Control System, Modular Matrix Switch and HDBaseT extenders.


Expert Comment

ID: 24135811
Right click on the folders in question go to Sharing and Security, Security tab.
Click Advanced and uncheck Allow inheritable permissions.....etc and check Replace permissions on all child ....etc
Remove all rights for all users other than the accounts (if any) you have just created (i.e. user one etc). and the Server Administrator account.

Test from all workstations that will be accessing the share to simulate realistic usage.

Expert Comment

ID: 24135883
Sorry I forgot to ask how many people are accessing each share?

Author Comment

ID: 24137902
Currently there are only 3 people that could be accessing each share.  This could change but, if I'm understanding what you've said correctly, it won't matter how many they have so long as the password and account login for the share itself is known on the local server....

Well it might matter if there was a possibility of a lot of people accessing a share but there isn't in this case.  It won't get any higher than 5 or 6 people...ever...

What I'm thinking of doing is creating user acounts whose names match the name of the share and using the different passwords methods that way.  I think that may work.  I will have to try it..  Was there anything else you wanted me to know RobDating?

Expert Comment

ID: 24141061
Nope I think you should be good.

Good luck

Author Closing Comment

ID: 31569716
Thank you for your patience on waiting for your points.  Well earned and deserved.  I have gotten so used to centralized mgmt of servers that I had forgotten some of the finer points of working with WORKGROUPS.  
Thank you for this solution.  YOU ROCK!

Expert Comment

ID: 24306266
Not a problem I'm not a points junkie! just glad I could make someones life easier!

Featured Post

Don't Cry: How Liquid Web is Ensuring Security

WannaCry is just the start. Read how Liquid Web is protecting itself and its customers against new threats.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

The Windows functions GetTickCount and timeGetTime retrieve the number of milliseconds since the system was started. However, the value is stored in a DWORD, which means that it wraps around to zero every 49.7 days. This article shows how to solve t…
Determining the an SCCM package name from the Package ID
This Micro Tutorial will give you a basic overview of Windows DVD Burner through its features and interface. This will be demonstrated using Windows 7 operating system.
The Task Scheduler is a powerful tool that is built into Windows. It allows you to schedule tasks (actions) on a recurring basis, such as hourly, daily, weekly, monthly, at log on, at startup, on idle, etc. This video Micro Tutorial is a brief intro…

691 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question