Re: It must be simple, but...



Mocacius,

It looks as though you are mixing a peer-to-peer setup with a domain setup.
Why did you create domain accounts on the server and local accounts on the
workstations?

Remove the local workstation accounts and just use the domain accounts you
created on the server when you log into the workstations. That will create
profiles on the workstations that contain the domain user information. You
do not need local user accounts at all on the workstations.

What is happening is that you have set up peer-to-peer permissions in a
domain. In order for your plan to work (explanation only!!! Do NOT do
this!!), you would have to create a LUSR01 local account on the Client2
computer with the same password used on Client1, and a LUSR02 local account
on the Client1 computer, with the same password as the Client1 user. See how
screwy that gets? All you need to do is dump the local accounts, log into
each workstation as the domain account you created, and get authentication
from the server.

If you MUST share your client drives (bad move from a security standpoint),
then add the DOMAIN account of each user to the two workstations' share
permissions.

Gregg Hill




"Mocacius" <mocacius@xxxxxxx> wrote in message
news:%236IUrBA1FHA.3892@xxxxxxxxxxxxxxxxxxxxxxx
> Just (finally <g>) moved the LAN to a new SBS2003 Server. At this point,
> it's the only server, with 2 clients, both XP Pro.
>
> I am trying to make things work the way they user to work on NT4 (well
> similar), but I think I must be missing something very basic. To preface,
> on the recommendation from some in this NG, I purchased and looked through
> the "Windws Small Business Server 2003", by Russel, Crawford, Gerend, but
> I can't find the answers (may be because I don't know what I'm looking for
> <smile>).
>
> Here is is in a nutshell..
>
> - SBS2003 has 2 user records created on it, U_SR01 and U_SR02, both admin
> privileges
> - Client #1, has a "local" user defined as LUSR01, Drive C is shared for
> U_SR01 and U_SR02
> - Client #2, has a "local" user defined as LUSR02, Drive C is shared for
> U_SR01 and U_SR02
>
> Reboot all 3 systems
> - Log on Client#1 as a local use, LUSR01
> - Log on Client#2 as a local use, LUSR02
>
> From Client #1, through network neighborhood, I can see the SBS2003
> server, and I can access its resources after I get prompted for and log on
> as U_SR01.
>
> From Client #2, through network neighborhood, I can see the SBS2003
> server, and I can access its resources after I get prompted for and log on
> as U_SR02.
>
> From either client, I can see the other client, but when I try to access
> the HD, I get an error message that I may not be authorized to access it.
>
> I am probably missing something very simple, but you know, can't see the
> forrest for the trees... :-(
>
> Any hints, anyone?
>
> *M*
>
>
>
>


.



Relevant Pages

  • Re: How to set up DCOM properly to allow server and client connect remotely
    ... their accounts if said accounts have the same username ... I need to know how to set up DCOM properly so the OPC server and client ... local user ...
    (microsoft.public.win32.programmer.ole)
  • Re: Multiple Individual permissions.
    ... The server acts as a file, ... > user accounts on each machine. ... > All I want is for Client D to boot to windows automatically using D's ... > Client D = Admin rights on all machines ...
    (microsoft.public.windowsxp.network_web)
  • Re: E-mail filtering recommendations needed.
    ... company's server and send outgoing e-mail through the same server. ... You could put up a local mail server which will poll the ISPs ... Then the user pop accounts would be removed from ... SS numbers and protected client information? ...
    (comp.unix.sco.misc)
  • Re: SMS site server HDD allocation
    ... Keep in mind that the SMS server is a database server. ... >>The Client Installation Wizard is used to remotely install, or push, the ... >>Connection accounts to allow the clients to connect and write to the ...
    (microsoft.public.sms.admin)
  • Re: It must be simple, but...
    ... I assume you have added both workstations to the new domain. ... using the DOMAIN user accounts ONLY. ... >I understand why I shouldn't share the client drives, etc., and in general ... > the server shared drive), again, using the same credentials. ...
    (microsoft.public.windows.server.sbs)

Loading