Determining which machines I've logged on to

[Herb Martin]

Hello,
We're running a Windows 2000 Active Directory environment. I was just
wondering if there's a resource kit utility that will allow me to see which
machines I've currently 'locked' instead of 'logged off'. The reason I'm
asking is because I need to change my domain password & I'm afraid of
locking out my account if I'm still logged in somewhere. Sorry if my
question is a little confusing. Any suggestions are appreciated.

Not really -- even if you audited Account Logons it would
be non-trivial to check all of the security logs.

The NetBIOS registration (of your name) won't work since
that is unique and only works for the first machine (you logged
into.)

 

[Veets]

Hello,
We're running a Windows 2000 Active Directory environment. I was just
wondering if there's a resource kit utility that will allow me to see which
machines I've currently 'locked' instead of 'logged off'. The reason I'm
asking is because I need to change my domain password & I'm afraid of
locking out my account if I'm still logged in somewhere. Sorry if my
question is a little confusing. Any suggestions are appreciated.
Best regards,
Veets

 

[Veets]

Hey Herb, thanks for the reply. Actually, I did find the following ->
http://www.optimumx.com/download/#NetUsers
It's the 'netusers' tool. It's kind of what I'm looking for.
Veets

 

[Herb Martin]

Hey Herb, thanks for the reply. Actually, I did find the following ->
http://www.optimumx.com/download/#NetUsers
It's the 'netusers' tool. It's kind of what I'm looking for.
Veets

What does it do?

If if uses the NetBIOS registration with WINS server to give you
the current users then it will miss the multiple logons...

 

[ptwilliams]

Hi Herb,

Can you use the fact that multiple logons cause a conflict with the <03>
bit?

(I've never really looked into NetBIOS as I started administering servers
with win2000 and have only recently -since changing job in March- started
working with NT <blush>)

--

Paul Williams

http://www.msresource.net
http://forums.msresource.net

Hey Herb, thanks for the reply. Actually, I did find the following ->
http://www.optimumx.com/download/#NetUsers
It's the 'netusers' tool. It's kind of what I'm looking for.
Veets

What does it do?

If if uses the NetBIOS registration with WINS server to give you
the current users then it will miss the multiple logons...

 

[Herb Martin]

Hi Herb,

Can you use the fact that multiple logons cause a conflict with the <03>
bit?

(I've never really looked into NetBIOS as I started administering servers
with win2000 and have only recently -since changing job in March- started
working with NT <blush>)

Sorry for the delay -- I have been away a lot.

No, not unless you monitored them with a custom
process or network filter (write an entire new program)
-- and run it on every WINS or broadcast domain -- since
the NetBIOS name registration can happen on either a
broadcast basis or at each WINS server.

(FYI for the merely curious: I have written NetBIOS API
code starting with DOS 3.x., but nothing recently.)

 

[ptwilliams]

Figured it wouldn't have been that straight forward else you'd have
mentioned it.

What language would you have written the early networking stuff in?? : )

--

Paul Williams

http://www.msresource.net
http://forums.msresource.net

Hi Herb,

Can you use the fact that multiple logons cause a conflict with the <03>
bit?

(I've never really looked into NetBIOS as I started administering servers
with win2000 and have only recently -since changing job in March- started
working with NT <blush>)

Sorry for the delay -- I have been away a lot.

No, not unless you monitored them with a custom
process or network filter (write an entire new program)
-- and run it on every WINS or broadcast domain -- since
the NetBIOS name registration can happen on either a
broadcast basis or at each WINS server.

(FYI for the merely curious: I have written NetBIOS API
code starting with DOS 3.x., but nothing recently.)

 

[Herb Martin]

Figured it wouldn't have been that straight forward else you'd have
mentioned it.

What language would you have written the early networking stuff in?? : )

Well, we wrote much of it in Assembler but Turbo Pascal
was also popular -- then later in C. I believe I still have
my "C Programmer's Guide to Netbios" around here somewhere.

And I just found it listed on Amazon (used) for 98 cents <grin>

By the time we got that book we had been doing it for a while
but it seemed so cool to actually have a book on the subject.

You may not remember when a visit to the bookstore would
turn up maybe 10 books in the computer "section".

(Two or three of the ten would be in ForTran.)

 

[ptwilliams]

Turbo Pascal was my first introduction to programming in College. Now don't
get me wrong - I'm no programmer, I just did what had to be done in College
and Uni. (Pascal, C, Java and C++) but one thing I liked about Turbo Pascal,
which I've been looking for in VBScript with no such luck, was the gotoxy()
function. Great for column-type output. Where has the functionality gone??
<g>

As for NetBIOS programming I admire you older programmers - you really had
to write code. Nothing nice and easy like try {} catch, etc. now ;-)

As for assembler...well, that just astounds me.

Can you read binary??? <g>


--

Paul Williams

http://www.msresource.net
http://forums.msresource.net

Figured it wouldn't have been that straight forward else you'd have
mentioned it.

What language would you have written the early networking stuff in?? : )

Well, we wrote much of it in Assembler but Turbo Pascal
was also popular -- then later in C. I believe I still have
my "C Programmer's Guide to Netbios" around here somewhere.

And I just found it listed on Amazon (used) for 98 cents <grin>

By the time we got that book we had been doing it for a while
but it seemed so cool to actually have a book on the subject.

You may not remember when a visit to the bookstore would
turn up maybe 10 books in the computer "section".

(Two or three of the ten would be in ForTran.)

 

[Herb Martin]

Turbo Pascal was my first introduction to programming in College. Now don't
get me wrong - I'm no programmer, I just did what had to be done in College
and Uni. (Pascal, C, Java and C++) but one thing I liked about Turbo Pascal,
which I've been looking for in VBScript with no such luck, was the gotoxy()
function. Great for column-type output. Where has the functionality gone??
<g>

Turbo Pascal was basically what C became, with plenty of
additions to make it work easily on a DOS machine.

To this day, the finest book on "How to THINK like a programmer"
is "Software Tools in Pascal" and I still try to re-read it at least
once per year. (It's difficult to convince newbies why they want
to read a book on an obsolete language but the key is the TOOL
MENTALITY.)

As for NetBIOS programming I admire you older programmers - you really had
to write code. Nothing nice and easy like try {} catch, etc. now ;-)

Most people don't really understand the need for error
handling anyway -- but it's not really that hard, just incredibly
tedious to write you own.

Remember, everything you write in a high level language is
ultimately translated by the compiler into assembler, or
ultimately into machine language which is just assembler
without the mnemonic codes.

But today, I can get so much more done in Perl most of the
time, and of all the languages that I really know (about 30
for production code) Lisp is still the most fun if you can get
it for your platform. (Quality Lisp compiler that is.)

VB is great for Windows graphical programs.

As for assembler...well, that just astounds me.

It's not really hard if you just THINK good programming.

I actually learned to program on a CALCULATOR (HP and TI)
which is actually good training for both assembler and symbolic
programming. (Ok, I went to 2 classes in ForTran during college
before I dropped the course as worthless.)

Can you read binary??? <g>

Of course, but that's not hard and a few minutes (about an hour)
with me and you could do so too. <really>

 

[ptwilliams]

Ha ha ha. I don't know about an hour!!!

I meddled with Lisp and clips in my advanced AI module, but didn't get very
far as there wasn't much coverage in the lectures and I wasn't going to go
out and buy a book as there was lots of other things to do -including heavy
drinking sessions, football, cricket, etc. ;-)

Yes, Turbo Pascal was our introduction, and it was a good way of introducing
us to structured programming.

I quite like the whole OOP thing though (just prefer prototyping again and
again as opposed to structured design like the waterfall ;-)


--

Paul Williams

http://www.msresource.net
http://forums.msresource.net

Turbo Pascal was my first introduction to programming in College. Now don't
get me wrong - I'm no programmer, I just did what had to be done in College
and Uni. (Pascal, C, Java and C++) but one thing I liked about Turbo Pascal,
which I've been looking for in VBScript with no such luck, was the gotoxy()
function. Great for column-type output. Where has the functionality gone??
<g>

Turbo Pascal was basically what C became, with plenty of
additions to make it work easily on a DOS machine.

To this day, the finest book on "How to THINK like a programmer"
is "Software Tools in Pascal" and I still try to re-read it at least
once per year. (It's difficult to convince newbies why they want
to read a book on an obsolete language but the key is the TOOL
MENTALITY.)

As for NetBIOS programming I admire you older programmers - you really had
to write code. Nothing nice and easy like try {} catch, etc. now ;-)

Most people don't really understand the need for error
handling anyway -- but it's not really that hard, just incredibly
tedious to write you own.

Remember, everything you write in a high level language is
ultimately translated by the compiler into assembler, or
ultimately into machine language which is just assembler
without the mnemonic codes.

But today, I can get so much more done in Perl most of the
time, and of all the languages that I really know (about 30
for production code) Lisp is still the most fun if you can get
it for your platform. (Quality Lisp compiler that is.)

VB is great for Windows graphical programs.

As for assembler...well, that just astounds me.

It's not really hard if you just THINK good programming.

I actually learned to program on a CALCULATOR (HP and TI)
which is actually good training for both assembler and symbolic
programming. (Ok, I went to 2 classes in ForTran during college
before I dropped the course as worthless.)

Can you read binary??? <g>

Of course, but that's not hard and a few minutes (about an hour)
with me and you could do so too. <really>

 

[Herb Martin]

Ha ha ha. I don't know about an hour!!!

I do -- since I do it all the time and with many people not
nearly as smart as you are.

Teaching people to see THROUGH the IP addresses directly
to the binary is part of my standard Windows Server training.

It takes about 1 1/2 hours to teach subnetting (and then 5 minutes
to teach supernetting and route summarization) the way I do it.

I meddled with Lisp and clips in my advanced AI module, but didn't get very
far as there wasn't much coverage in the lectures and I wasn't going to go
out and buy a book as there was lots of other things to do -including heavy
drinking sessions, football, cricket, etc. ;-)

Yes, Turbo Pascal was our introduction, and it was a good way of introducing
us to structured programming.

I quite like the whole OOP thing though (just prefer prototyping again and
again as opposed to structured design like the waterfall ;-)

Most of the OOP stuff is badly taught since it is dependent on
good structured design as a BASIS. Many/most programmers never
really understood good structured design (since most teachers
don't have a clue) and therefore write bad code in OOP the same
way.

Good programmers were thinking OOP long before the tools supported
it -- the idea behing an object oriented language is to get the compiler
to do the tedious bookkeeping -- instead of making the programmer do
it.

 

[Kevin D. Quitt]

A REAL programmer can write FORTRAN in any language. Every programming
style and modality has both advantages and disadvantages. I've written OO
programs in assembly and a multi-tasking OS in BASIC. I also have an
example of a (harmless) virus written in plain, vanilla DOS batch
language.

For a humorous example of a disadvantage of OOP, see
<http://www.tinyurl.com/4569e>

 

[ptwilliams]

Well, I'd sure like to visit one of *your* courses!

You do training in the UK? Specifically, the South Wales area??? <grin>


--

Paul Williams

http://www.msresource.net
http://forums.msresource.net

Ha ha ha. I don't know about an hour!!!

I do -- since I do it all the time and with many people not
nearly as smart as you are.

Teaching people to see THROUGH the IP addresses directly
to the binary is part of my standard Windows Server training.

It takes about 1 1/2 hours to teach subnetting (and then 5 minutes
to teach supernetting and route summarization) the way I do it.

I meddled with Lisp and clips in my advanced AI module, but didn't get very
far as there wasn't much coverage in the lectures and I wasn't going to go
out and buy a book as there was lots of other things to do -including heavy
drinking sessions, football, cricket, etc. ;-)

Yes, Turbo Pascal was our introduction, and it was a good way of introducing
us to structured programming.

I quite like the whole OOP thing though (just prefer prototyping again and
again as opposed to structured design like the waterfall ;-)

Most of the OOP stuff is badly taught since it is dependent on
good structured design as a BASIS. Many/most programmers never
really understood good structured design (since most teachers
don't have a clue) and therefore write bad code in OOP the same
way.

Good programmers were thinking OOP long before the tools supported
it -- the idea behing an object oriented language is to get the compiler
to do the tedious bookkeeping -- instead of making the programmer do
it.

 

[Herb Martin]

A REAL programmer can write FORTRAN in any language.

Absolutely. And conversely, a REALLY GOOD programming
can write really good code in any language.

Even OOP in assembler. (But it's a lot of work.)

Every programming
style and modality has both advantages and disadvantages. I've written OO
programs in assembly and a multi-tasking OS in BASIC.

That's fairly hard (BASIC multi-tasking) on most systems.

I also have an
example of a (harmless) virus written in plain, vanilla DOS batch
language.

Some of the most prevalent virus were Word macros written
in that odd form of Basic.


One trick is to think in the language that most closely matches
the problem -- and then code the solution in the language that
is most suitable given the context (OS, etc.)

Another is to adapt the language by writing a business specific
language and then coding in that meta-language.

The latter is the sitiuationg usually missed by those criticising
C or Assembler as being too "low level".

Such languages operate at many levels of abstraction if the
programmer has the skills.

For a humorous example of a disadvantage of OOP, see
<http://www.tinyurl.com/4569e>

 

[Herb Martin]

Well, I'd sure like to visit one of *your* courses!

You do training in the UK? Specifically, the South Wales area??? <grin>

I would love to have you in class, but no we aren't putting
Wales on the schedule at the moment.

Prior to 9/11 we had international students in class almost
every time -- we thought of Canadians as being local then. <grin>

For some (explanable but) odd reason we were very popular
with the Danes -- we would have one or two about every other
month.

 

[ptwilliams]

That's not surprising! The Danes can't wait to get out of Denmark!!! <grin>

Hell, it was up for sale on E-bay a couple of months ago ;-)


--

Paul Williams

http://www.msresource.net
http://forums.msresource.net

Well, I'd sure like to visit one of *your* courses!

You do training in the UK? Specifically, the South Wales area??? <grin>

I would love to have you in class, but no we aren't putting
Wales on the schedule at the moment.

Prior to 9/11 we had international students in class almost
every time -- we thought of Canadians as being local then. <grin>

For some (explanable but) odd reason we were very popular
with the Danes -- we would have one or two about every other
month.