I just bought a new Win 2003 server, and have it set up in the workgroup. (No Domain) In order for our design program to have acess to it's database, I have mapped drives from the XP Pro workstations to a shared folder on the server. The problem is that even though I've set the sharing and security to allow users and authenticated users to be able to fully control the files, I still must log in to the server from the workstation. I don't think that allows automatic file sharing. Is there a way to allow the program full access to the mapped drive without the log in screen? And how should the sharing and security really be set up on this shared folder?

Why not create a domain and use active directory? I highly recommend NOT doing what you currently have setup. Creating a domain and adding the machines is an extremely easy process. What permissions are you setting? There are 2, file and share. I suppose you could just add the EVERYONE group to have full control on both shares, and it shouldn't ask for any credentials. Holy Wow.

I'm not setting up a domain and active directory as it would add a level of complexity that I don't need on a small network- on the advice of several system admins I know.

Why would you not recommend doing what I am doing, and why would you set up active directory instead?

Because any IT guy would suggest a Domain if you have the capabilities. What does your database run over? SQL? Access? Most databases wont care whether its a workgroup or domain, unless they are custom and specific to something. Your problem lies in authentication. When you type in Start>run>\\servername to show shares, it automatically tries to log in with the user that you are logged in with locally. You will have to mach usernames / passwords. Active Directly would allow you to add these users in, and for them to get onto the domain, they would log in with that user. That would give them rights to the server, ect. Yes it will be more WORK promoting your Server to a DC but, more worth it in the long run. Unless of course you are running like 2 PC's with this server, which at that point I would not even see why you would need a server. Thanks for any input.

I AM the IT guy (of sorts). It's ok if you don't consider me to be much of one. It's only one of the hats I wear here. :-) And we have less than 15 PCs on the network. Which is why it's not really worth it to set up active directory. Our design program uses an Access database. It installs itself and it's database on the "server" and the keyserver process also runs on that machine. Then the other workstations have the program installed locally via a netsetup program run across a mapped drive to the server. Once it's installed on the local machine it gets permission from the keyserver, and accesses the database on the server, but runs locally. So, since it's the read write speed of the server that counts here, and XP flakes out after 10 users - that's why I have a real server. At least that's the theory. We'll see if it actually speeds up the process once I get this problem solved. And like I said, several of my sys admin friends say I don't really need a domain/active directory for this small network. I believe 'em since one of them runs all the systems for a large government organization in whole southeastern US. He should know what he's talking about. I really don't have that much of a security problem since I have a really limited group of users, so I'm not really worried about that. If anyone causes problems I just walk around the corner and slap 'em up side the head. :-) I know I'm not using the server as it was really designed, but all I really need to know is how to set up the server permissions so that each user doesn't have to provide a username and password every time they try to use the design program. The program itself already has that built in. I don't need them to have to do it twice...

In no way, shape, or form, was I intentionally suggestiong that you were not much of a IT guy. I was only expressing my opinion on the matter, and still provided you with a solution. The Username and Passwordsr between local PC and the Server must match. If you log into (example) local PC account: u=account1 p=password Then the account must be added the the server, with the same creds. Then if everyone is utilizing your share, share it to everyone. That should enable the share to everyone and you wont have to worry about login to that share. If you have specific users for the share, then you will have to specify permissions. The authentication will come from the server since its sharing the files and folders, if it cant recognize the account you log in with, then to grant access to the share it will prompt you for a logon. If this works for you, which it should, I feel pretty bad for the Southeastern US, and am glad I work in the Midwest :) Thanks for any input.