Re: Logon local to W2k workstation using domain account
From: Steven Umbach (n9rou_at_n0spam-comcast.net)
Date: 08/12/04
- Next message: dkpc: "Re: last critical updates"
- Previous message: Ratmoler Hamstak: "Re: Logon local to W2k workstation using domain account"
- In reply to: Ratmoler Hamstak: "Re: Logon local to W2k workstation using domain account"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Thu, 12 Aug 2004 04:43:29 GMT
That is true. About the best you could do is to copy one profile over to the
other when needed. --- Steve
"Ratmoler Hamstak" <hamstak@yahoo.com> wrote in message
news:f3c5beb2.0408112037.cde53ef@posting.google.com...
> Thanks Steve, but I think I am out of luck -- at least from the
> perspective of my ideal solution. I was hoping to be able to use a
> single account so that I could also use a single profile; correct me
> if I am mistaken, but I am under the impression that a domain account
> and a local account, even with identical credentials, maintain
> distinct profiles. Your solution might be the closest to ideal that I
> have. So it goes.
>
> "Steven L Umbach" <n9rou@n0-spam-for-me-comcast.net> wrote in message
news:<l_7Sc.233128$a24.215816@attbi_s03>...
> > You can create a local computer account that has the same username/password
as a
> > domain account and access resources in the domain as a domain user as long
as the
> > domain controller is running. If the domain controller is down you can not
access the
> > resource as a domain user because the domain controller must be contacted to
> > authenticate the user since the domain resource computer has no way of
knowing if the
> > request is from a legitimate domain account. That is the nature of domain
> > authentication.
> >
> > The only way to access a resource on a domain computer without the domain
controller
> > running is to add users to local user database via lusrmgr.msc on that
domain member.
> > That will allow a user to access the resource as a local user and not as a
domain
> > member. Though confusing, you could have the same username/password in the
local user
> > sam of the domain computer offering the share. You should be able to connect
then by
> > using computername\user as the user trying to gain access when prompted for
> > credentials. Hope that helps. --- Steve
> >
> > "Ratmoler Hamstak" <hamstak@yahoo.com> wrote in message
> > news:f3c5beb2.0408092056.703a7fc4@posting.google.com...
> > > Thanks for your responses. If anyone was (is) confused, that would be
> > > me. I misunderstood the notion of using a domain account to "logon
> > > locally" (selecting "this computer" from the "log on to" menu of the
> > > logon screen), believing that this would cause the account to emulate
> > > a local account therefore bypassing domain authentication and treating
> > > the workstation essentially as a standalone computer. Let me approach
> > > the problem from the opposite direction.
> > >
> > > I have a Tritton NAS-120 network attached storage appliance. It was
> > > designed to operate readily with Windows workgroups but not domains.
> > > Accounts and groups are established on the device through an embedded
> > > http interface and do not appear to be integrable with Active
> > > Directory.
> > >
> > > My server is Win2k, serves as a DC and has Active Directory installed.
> > > When I initially set up the NAS device, I was able to connect to it
> > > and map it to a drive letter on the server in the manner specified
> > > (\\{ip address}). Incidentally, a name can be specifed for the
> > > device using its web interface, and this name appears in the Active
> > > Directory Users and Computers manager under the compouters node.)
> > > While the server was in operation, I made the same mapping on my
> > > workstation and was able to access it without any problems. The
> > > problem occurs if the server is off and I try to access the drive
> > > through the workstation using either the mapping or the URN. The
> > > error which occurs reads "no logon servers available to service the
> > > logon request". My impression is that the device is considered to be
> > > a member of the domain and is registered in Active directory, that
> > > this information stored is maintained in the instance of win2k pro on
> > > the workstation, and that it requires the dc to be operating in order
> > > to service the "logon" request.
> > >
> > > By the way, the credentials for the domain accounts I have used are
> > > cached, as I am able to "logon to the domain" even when the server is
> > > unavailable.
> > >
> > > Finally, if I use a local computer account and logon to the computer,
> > > I am able to access the drive with no problem.
> > >
> > > Ultimately, the issue is that I would like to be able to use a domain
> > > account to logon and be able to access the drive without the server
> > > being available rather than having to maintain a separate local
> > > account. For those of you who might suggest I keep the server on all
> > > the time, the reason I got the NAS device was so I wouldn't have to do
> > > that; it is a compact, low-power unit -- and I do live in SoCal.
> > >
> > > Thanks again for any comments/suggestion you might have.
> > >
> > > Tom -- aka hamstak
- Next message: dkpc: "Re: last critical updates"
- Previous message: Ratmoler Hamstak: "Re: Logon local to W2k workstation using domain account"
- In reply to: Ratmoler Hamstak: "Re: Logon local to W2k workstation using domain account"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|
