IIRC, you can't even do that from windows on an NT 4.0 domain with win9x
clients.
It has something to do with the way Winnt boxen are true members of a
domain - that is to say, that you have to get on the pdc and make a
machine account for every Winnt client on the domain.
Win9x boxen are transient members of the domain. The user is really a
member of the domain, and you won't see the win9x box on the domain
manager on the PDC unless a user is logged into the domain.
Winnt clients always appear on the domain manager, whether someone is
logged into them or not, and that's why you can see who's logged into
them - the domain owns them, not the user account.
I haven't worked with NT for a few years, but there is some command line
equivalent to the nmblookup on the cmd line in NT. It might be a switch
to the net * command. But we weren't able to look into win9x boxes to see
who was logged into them. I'm guessing ME is the same way.
Did you try asking a samba list? They probably have more insight as to
what's really going on. I always assumed the capability wasn't built into
the domain client code on win9x.
HTH
--mandi
On Thu, 7 Jun 2001, Mads Rasmussen wrote:
>
> I found the only tool to know who is logged on to a given machine on our win
> net is the nmblookup command.
>
> Run with the -A options it gives the user on the machine (however in a
> somewhat messy form)
>
> $nmblookup -A mars.universe
> Looking up status of 192.168.1.xxx
> received 6 names
> MARS <00> - B <ACTIVE>
> UNIVERSE <00> - <GROUP> B <ACTIVE>
> MARS <03> - B <ACTIVE>
> MARS <20> - B <ACTIVE>
> UNIVERSE <1e> - <GROUP> B <ACTIVE>
> MARTIAN <03> - B <ACTIVE>
>
> This show that the user martian is logged on to the machine mars.
>
> However this only work for machines with winnt, even though our PDC is
> running nt as well. If I make a query on a win 9x/Me machine, the nmblookup
> tool shows nothing.
>
> Anyone know how to improve on this?
>
> Regards,
>
> Mads
>
