Re: Roaming profile in problem
danieltan_at_time.net.my
Date: 02/24/05
- Next message: ptwilliams: "Re: Roaming profile in problem"
- Previous message: ptwilliams: "Re: fix domain name in AD"
- In reply to: ptwilliams: "Re: Roaming profile in problem"
- Next in thread: ptwilliams: "Re: Roaming profile in problem"
- Reply: ptwilliams: "Re: Roaming profile in problem"
- Messages sorted by: [ date ] [ thread ]
Date: 24 Feb 2005 00:12:07 -0800
Paul, i try nltest in windows2000 server but it doesnt have this
command. Where can i try it ?
Rgds
Daniel
ptwilliams wrote:
> Ah...nice. I'll have a play with that tomorrow. I'm thinking about
> learning Perl. I just downloaded and installed ActivePerl...
>
>
> I often use /whowill, but I'd forgotten about /finduser.
>
> nltest is a real handy tool alright!!!
>
>
> --
>
> Paul Williams
>
> http://www.msresource.net/
> http://forums.msresource.net/
>
> "Herb Martin" <news@LearnQuick.com> wrote in message
> news:OvlnAYVGFHA.4088@TK2MSFTNGP09.phx.gbl...
> "ptwilliams" <ptw2001@hotmail.com> wrote in message
> news:eiITfHSGFHA.3840@tk2msftngp13.phx.gbl...
> > > I wonder if there is a built-in and direct way to tell if the
machine
> and
> > > user are authenticated....
> >
> > That would be nice!
>
> Maybe these are close enough:
>
> nltest /whowill:Domain.Com UserName
>
> nltest /finduser:UserName
>
> > Can you whip something up in Perl?!? ;-)
>
> Well, sure, though it wouldn't be direct but
> just another hack <grin>
>
> #Perl begins
>
> $debug = 1; #set to 0 for less output
> @services = `net start`;
> foreach (@services) {
> next unless /^\s+Net Logon\s*$/;
> $dc = 1;
> print if $debug;
> last;
> }
>
> print "DC\n" if $dc && $debug;
> print "not DC\n" if $dc && $debug;
> if (defined($ENV{LOGONSERVER})) {
> $logonServer = $ENV{LOGONSERVER};
> $logonServer =~ s/.*\\+(.*)/$1/;
> print "LogonServer: $logonServer\n" if $debug;
> }
> if (defined($ENV{COMPUTERNAME})) {
> $computer = $ENV{COMPUTERNAME};
> print "Computer: $computer\n" if $debug;
> }
>
> if ($dc || ($computer != $logonServer)) {
> print "logged onto domain.\n";
> exit 0;
> } else { #User is
> print "NOT logged onto domain.\n";
> exit 1;
> }
>
> # Perl ends
>
> --
> Herb Martin
>
>
> >
> >
> > --
> >
> > Paul Williams
> >
> > http://www.msresource.net
> > http://forums.msresource.net
> >
> >
> > "Herb Martin" <news@LearnQuick.com> wrote in message
> > news:%23hHvvf4FFHA.2180@TK2MSFTNGP12.phx.gbl...
> > "ptwilliams" <ptw2001@hotmail.com> wrote in message
> > news:eZS4PC4FFHA.3888@TK2MSFTNGP12.phx.gbl...
> > > The logonserver is the local machine if a DC cannot be found,
e.g. the
> > > computer name.
> > >
> >
> > I was also leaving some wriggle room for
> > things like DC available, authenticates, then
> > DC does down (credentials might even expire.)
> >
> > I wonder if there is a built-in and direct way to
> > tell if the machine and user are authenticated....
> >
> > (Looking at the environment works for me, but
> > seems a bit indirect or non-specific.)
> >
> > --
> > Herb Martin
> >
> >
> > >
> > > --
> > >
> > > Paul Williams
> > >
> > > http://www.msresource.net/
> > > http://forums.msresource.net/
> > >
> > > "Herb Martin" <news@LearnQuick.com> wrote in message
> > > news:unSbSA3FFHA.1392@tk2msftngp13.phx.gbl...
> > > <danieltan@time.net.my> wrote in message
> > > news:1108908702.154362.35980@g14g2000cwa.googlegroups.com...
> > > > Herb, firstly if i can set L to a DC and get result then my
computer
> is
> > > > authenticated ?
> > >
> > > I think this is true -- were the the user not logged on
> > > it would seem wrong to show a logon server.
> > >
> > > NLTest is more definitive but difficult to use (contrary
> > > command line switches.)
> > >
> > > I was sort of hoping that someone would post a KB article
> > > describing such tests. (Experience makes it pretty obvious
> > > to me but that is NOT a good answer for someone trying to
> > > learn.)
> > >
> > > > also if USE and ping can be used then it is
> > > > authenticated also ?
> > >
> > > In no way does ping tell you this.
> > >
> > > Ping FAILURE would make it unlikely that authentication
> > > worked but even that is not reliable unless you are very
> > > certain why ping failed.
> > >
> > > For instance, any firewall including the XP-Win2003 built-in
> > > firewall might block ping or IP might be broken a computer
> > > still authenticate in some domains with another protocol but
> > > this is less common today with IP required and few people
> > > using other protocols.
> > >
> > > > What are the components required to have in order
> > > > to have roaming profile works ?
> > >
> > > Authentication
> > > Server with share, proper permissions on share and NTFS
> > > Usually share and NTFS need to be Full Control for the
> > > group or user to who will save a profile.
> > > Network operation so that client can reach the share (timely
> > > manner so that it doesn't timeout)
> > >
> > > --
> > > Herb Martin
> > >
> > >
> > > >
> > > > Regards
> > > > Daniel
> > > >
> > >
> > >
> > >
> >
> >
> >
- Next message: ptwilliams: "Re: Roaming profile in problem"
- Previous message: ptwilliams: "Re: fix domain name in AD"
- In reply to: ptwilliams: "Re: Roaming profile in problem"
- Next in thread: ptwilliams: "Re: Roaming profile in problem"
- Reply: ptwilliams: "Re: Roaming profile in problem"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
