Re: I really need help from somebody.

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: BCE (dirwolf_at_speakeasy.net)
Date: 01/25/05 

Date: Mon, 24 Jan 2005 20:33:27 -0500

You can keep this arrangement, BUT, for every workstation you have it must
have a locally built account, and then that account must also be created on
the server. You will get a bypass authentication as the workstation will
send the locally logged on credentials to the server who will have its own
account with the same username and password.
This can be done, but you dont want this hassle.
Create the domain, it is not that bad and it will give you more control. 

-- 
BRIAN EDWARDO
"Greg" <Greg@discussions.microsoft.com> wrote in message 
news:D610894C-B786-47EF-98D9-5675F1A3DEBA@microsoft.com...
> Ken, with a peer to peer network, all logon accounts are stored on each
> machine, this will cause more work to manage. You will have to go to each
> machine and create login accounts to login locally. Also, users will have 
> to
> know a acct/password for the server to access info. The only way you can 
> get
> a login prompt is if you add the machines to a domain. You might want to
> consider creating a domain, it will allow you to control everything from 
> one
> computer (the server). Just use dcpromo on the server. You dont have to 
> use
> all the AD features. That would actually be simpler than going to all the
> workstations.
>
> If that scares you, just edit the local security policy to require a login
> user name and pass on each workstation.
>
> "Ken Roberts" wrote:
>
>> I inherited support for a Windows Server 2003 that was never setup by the
>> last guy (he never came back).  The server is physically connected to the
>> work stations using a switch.  All computers can 'see' eachother, but 
>> when
>> the work stations bootup, they are never given the chance to log onto the
>> network; they were just peer-to-peer before. I would like to keep this
>> simple; no domain controller, no active directory, as simple as possible. 
>> I
>> just want to logon about 10 users, and store data on the server.  How can
>> this be done simply?

Relevant Pages

  • Re: Re-Post - "the trust relationship between this workstation and the
    ... "the trust relationship between this workstation and the primary domain ... only problem is adding a new user account on the station. ... Client computer must use STRICTLY the INTERNAL DNS server which can ... Attr: subschemaSubentry ...
    (microsoft.public.windows.server.active_directory)
  • Re: Re-Post - "the trust relationship between this workstation and
    ... account is NEW to the workstation. ... needs admin group priv at workstation level. ... only problem is adding a new user account on the station. ... This would be on the DNS server 172.20.100.2 ...
    (microsoft.public.windows.server.active_directory)
  • Re: Re-Post - "the trust relationship between this workstation and
    ... There were no logged events in either the DC or workstation. ... DC/DNS Server - DCDiag ... Attr: subschemaSubentry ... only problem is adding a new user account on the station. ...
    (microsoft.public.windows.server.active_directory)
  • Secure web authentication system w/o SSL and PKI
    ... In the beginning, a user should be able to register for an account, ... minted one-time password to their email address. ... it is assumed that only both the server and the end ... I'm making the big assumption that the user's email login has not been ...
    (comp.security.misc)
  • Re: Re-Post - "the trust relationship between this workstation and
    ... There is no secondary WINS server defined for this adapter. ... Can you also run netdom and verify that the workstation has a valid ... account and that it checks out ok? ... Attr: subschemaSubentry ...
    (microsoft.public.windows.server.active_directory)