Disabling authentication in a workgroup

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi does anyone know the answer to this, greatly appreciated

I have a standalone business LAN in a workgroup, all pc's have internal IP addresses assigned so they can communicate. In the workgroup is a machine running windows server 2003, acting as a file and print server ONLY. I would like to disable the authentication prompt that comes up everytime a user trys to access a shared folder or add a printer from this windows 2003 machine

Can this be done

Thanks in addvance
 
Create all accounts and passwords on the server to match.
How many computers? A domain model may prove easier to manage.
 
Hi Lanwench thanks for the advice to answer your question:

The windows 2003 server machine is not a server as such its just a machine doing file and print sharing that happens to have this as an os.

In total there are 6 machines workgrouped the machine running server 2003 being one of them. Very small but its a hassle for the users to enter a username and password everytime they want to access a file on this machine or add a printer.
I just want to disable this somehow
Any ideas

Thanks
 
microsoft.public.win2000.security news group, =?Utf-8?B?Q2hyaXM=?=
The windows 2003 server machine is not a server as such its just a machine doing file and print sharing that happens to have this as an os.

In total there are 6 machines workgrouped the machine running server 2003 being one of them. Very small but its a hassle for the users to enter a username and password everytime they want to access a file on this machine or add a printer.
I just want to disable this somehow
Any ideas
Click to expand...

Your question was answered by Lanwench already:

"Create all accounts and passwords on the server to match."

With only 6 computers (and I'm assuming 6 users), this is trivial to do.
On the Windows Server 2003 computer, create 6 user accounts. Make sure
that the account names and passwords match the account names and
passwords that are being used to log on to the 6 computers.
 
What's the percieved disadvantage in setting up a domain model, since you
have a server that can do it? There's no additional cost, and it's a lot
easier to manage - only one place to set security (server), only one place
to manage accounts, you can use DHCP, DNS, roaming profiles, etc., ro make
admin a breeze....I'd do it, frankly.

That said, if you don't want to, you need to make sure there are accounts
set up on the server that match exactly what the local accounts/passwords
are for each machine. If someone changes a password, you have to change it
 
Back
Top