Re: Auto Logon to network

If the account names and passwords match across the workgroup you should not
see a prompt for a name and password when you connect to a network
resource - it should just happen. If you see the prompt that means that
either (1) The account does not exist on the "server"; or (2) The account
exists but has a different password on the "server" than the "guest"; or (3)
That the share rights on the "server" are not correctly configured.

--
Richard G. Harper [MVP Shell/User] rgharper@xxxxxxxxx
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


"Hosehead" <richbu@xxxxxxxxxxx> wrote in message
news:go3dc1drovvk8scm7qq11h9i0tonl4nivu@xxxxxxxxxx
>I thought that I have done the latter. I have each workstation with a
> unique ID and password to logon to XP and matching user accounts
> on the one Win 2000 server. I have three folders setup as share with
> one user able to access all folders and other users only able to
> access one folder that matches their ID.
>
> I remember that on workstations that were Win98 that you can go to
> networking and change the logon from "Client for MS Networks" to
> "Windows to Windows Family" logon and this would work to eliminate the
> second screen to logon to network. Is their a way to setup a script
> on the workstation that will auto-logon to the network using the ID
> and Password or the Windows logon. If possible a generic script that
> will use the ID and password from the user that is currently logged
> on.
> Detail instructions will be greatly appreciated.
>
> On Fri, 1 Jul 2005 19:39:19 -0400, "Richard G. Harper"
> <rgharper@xxxxxxxxx> wrote:
>
>>You have two choices - either you can establish a domain configuration
>>where
>>all accounts are stored on the domain controllers, or you will have to go
>>to
>>each server and establish accounts whose names and passwords match the
>>names
>>and passwords used to log onto the computers that are accessing the shared
>>resources.
>


.

Relevant Pages

  • Re: Windows 2000 users accounts get locked out
    ... You say that those machines are on your network or not?? ... The caller machine is the name of the machine that ... the user was attempting to logon from at the time of the lockout. ... Still my accounts get locked out. ...
    (microsoft.public.win2000.security)
  • Re: Maximum password Age, Domain Security Policy
    ... with the user command to search for and force accounts with certain password ... ages to change their password at next logon. ... > network drive mappings, while they are working. ... The password expires dialog-box warning is working ...
    (microsoft.public.win2000.group_policy)
  • Re: Password access for folders over network
    ... the network logon always uses the currently logged on user ... but you *can* get it to prompt for the password. ... username, ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Question: Sharing resources between Forests
    ... recource) and have your users logon with their given domain A credentials. ... Create a trust between our respective networks. ... Create local accounts on the server for the users needing access. ... on network A that users on network B need access to. ...
    (microsoft.public.windows.server.active_directory)
  • Re: OWA 2003 is only accessable during workingdays
    ... Is it the same when you log in from a client on the network? ... thinking of AD Users and Computers, Properties, Accounts, Logon Hours. ...
    (microsoft.public.exchange.misc)