Re: Have to reset the passwords every day!!!

Tech-Archive recommends: Fix windows errors by optimizing your registry


"Pegasus (MVP)" <I.can@xxxxxxx> wrote in message
news:uk83utm6FHA.2524@xxxxxxxxxxxxxxxxxxxxxxx> ========================
>
> I'm still confused, largely because you write things such as
> "... until I reset the password on the host machine for that
> individual client machine." How do you reset a password
> for a client machine? I thought you reset passwords for
> a user account, not for a client machine?

Of course you are right. I have to reset the passwords on
the server for each individual client.
>
> I am also puzzled by your mode of operation. You write:
> ==========
> - I turn on the host machine first.
> - Then I turn on each client [PC?].
> - At each client machine, I have to access that folder
> [How exactly do you do this?]
> - It asks for the individual machine password.
> [What account name do you specify? The same,
> regardless of the client machine?]

No, each machine has it's own name.
and a separate password. Actually, I'm confused because
some client machines seem to check the server and connect
automatically. Others require the entry of the appropriate
password.

> ==========
>
> I suspect that you have a clumsy typer who consistently
> mistypes the password, thus causing the account on the
> host machine to be suspended.

I don't think so. They normally enter the password once
and that is supposed to stay connected all day.

>
> A far superior way goes like this:
>
> 1. Create a number of accounts on the host PC: One for
> every staff member in the business.
> 2. Syncronise the passwords for these host accounts with
> the passwords on the client PCs.

Step 1 and 2 is what we have done. I don't understand step
3. Sorry for being so dumb.


> 3. Create the following batch file on each client PC:
>
> c:\documents and settings\start menu\programs\startup\netlogon.bat
> @echo off
> call \\HostPC\netlogon\netlogon.bat
> (Replace "HostPC" with the real name of the host PC)
>
> 4. Start a command prompt on the host machine and type
> these commands:
> md c:\netlogon
> net share netlogon=c:\netlogon
> copy con c:\netlogon\netlogon.bat
> @echo off
> net use S: \\HostPC\NameOfShare
> (Press function key F6 here)
> (Replace "HostPC" and "NameOfShare" with the actual
> names that apply in your case)
>
> 5. Check your NTFS permissions on the host:
> - Everyone must have read-access to the c:\netlogon folder.
> - Everyone must have full access to the shared folder.

Everyone does have full access to the shared folder. That is the
way the software works.

>
> 6. Check your permissions for the netlogon share:
> Everyone must have "Full access" to it.

I guess they do. How do I check this? Every user (client
computer) is an administrator on the server.

>
> Doing this would create a tightly controlled environment
> that is completely transparent. It will not rely on some
> remembered share connections that nobody really knows
> what they are and how they came into existence.
>
>


.

Relevant Pages

  • Re: Have to reset the passwords every day!!!
    ... Is the account used to share that folder a member of the Administrators ... > the host machine for that individual client machine. ...
    (microsoft.public.win2000.networking)
  • Re: Have to reset the passwords every day!!!
    ... >> - Does the account on the share's host machine get locked ... the host machine for that individual client machine. ... host folder is mapped as a shared folder. ...
    (microsoft.public.win2000.networking)
  • Re: Have to reset the passwords every day!!!
    ... >> individual client machine." ... How do you reset a password ... >> - I turn on the host machine first. ... profile can have a reference to a network logon batch file ...
    (microsoft.public.win2000.networking)
  • Client login on TS triggers msiexec.exe problem
    ... login in with remote desktop. ... This might be a completely normally behaivour, but the pattern I have makes ... the same host machine will trigger the same set ... it's the client machine that triggers it. ...
    (microsoft.public.windows.terminal_services)
  • cant access file on client machine
    ... the client machine can see/access folders shared on the ... and can access internet through the host machine. ... permission to use this network resource. ... i didn't set any restriction when i setup the network on ...
    (microsoft.public.windowsxp.network_web)