Re: windows domain questionFrom: Laura A. Robinson (email@example.com)
- Previous message: Deus, Attonbitus: "Re: OWA and URLScan"
- In reply to: Bejon Parsinia: "RE: windows domain question"
- Next in thread: Moorhouse, Walt P: "RE: windows domain question"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "Laura A. Robinson" <firstname.lastname@example.org> To: <email@example.com>, "'Mike Coppins'" <firstname.lastname@example.org>, <email@example.com> Date: Fri, 19 Apr 2002 15:01:19 -0400
But that is not the same as what remains or doesn't *when the laptop is
removed from the domain*. Entirely different situations.
As far as cached credentials, those can be easily controlled via group
policy. Also, it is not as easy as you indicate to "capture and recover"
passwords when somebody connects to a domain resource using cached
credentials. NTLM authentication is, indeed, used, but it's not quite as
simple as running a packet sniffer and voila!, credentials are magically
----- Original Message -----
From: "Bejon Parsinia" <firstname.lastname@example.org>
To: "'Mike Coppins'" <email@example.com>; <firstname.lastname@example.org>
Sent: Friday, April 19, 2002 12:53 AM
Subject: RE: windows domain question
> Speaking from experience, depending on the policies in place on the
> the laptop very well could retain sensitive information about the domain.
> My example is as follows, I take my laptop home with me every night. It
> running Win2k Pro. I can leave my login information exactly the same as
> when I have it plugged into my domain at the office when I login to the
> laptop at home without any sort of VPN or public access to my network.
> What does this mean? The laptop contains cached information (username,
> password, domain name) that does not necessarily expire. I am just
> in to use my laptop at home without connecting to any resources other than
> my internet connection at the house. Dangerous, you bet. You can run
> utilities to capture and recover those passwords very easily. No need to
> disconnect it from the domain whatsoever.
> Hope this helps,
> -----Original Message-----
> From: Mike Coppins [mailto:email@example.com]
> Sent: Thursday, April 18, 2002 9:46 AM
> To: firstname.lastname@example.org
> Subject: windows domain question
> If you connect a machine to a Windows domain, so things like SIDs change,
> machine IDs synchronised, etc, and then disconnected, what happens
> Does the node that gets disconnected generate a new machine SID or does
> information get left behind on the node?
> Putting the question into a scenario might help :) If a laptop (NT4 or
> Win2k) is connected to a domain, then is removed from the domain (as in,
> admin goes into network properties and tells the machine that it is part
> a bog standard workgroup again, is the laptop going to retain any
> information that it belonged to a domain before, and possibly security
> sensitive information about the domain?
> Mike Coppins
> Currently looking for work: http://www.legolas.com/mikes/cv.html