Re: How to investigate

From: Bijan Kianifard (BijanKianifard_at_discussions.microsoft.com)
Date: 05/28/05

  • Next message: Bruce Chambers: "Re: Netcraft Toolbar" 
    Date: Sat, 28 May 2005 05:59:01 -0700

    Thank you Steven

    "Steven L Umbach" wrote:

    > There are a couple ways. The command net use when run on a computer will
    > show network shares that it is connected to. The command net session will
    > show what shares other user are connected to on the computer where the
    > command is run. You can also use Computer Management and then select connect
    > to another computer to see sessions on the target computer via shared
    > folders/sessions. It would also be a good idea to enable auditing of logon
    > events on the domain computers and then you can check the security log for
    > what users have connected to that computer at what times.
    >
    > http://www.microsoft.com/technet/security/prodtech/windows2000/secmod144.mspx
    >
    > You can also use the command netstat -an to see network connections
    > established on a computer. To run this command on a remote computer that you
    > are an administrator on you can use the free tool psexec from SysInternals
    > as shown in the link below. --- Steve
    >
    > http://www.sysinternals.com/ntw2k/freeware/psexec.shtml
    >
    > You can also use the user rights access this computer from the network and
    > deny access this computer from the network to manage what users can access a
    > network share. For Remote Desktop connections you can manage the user rights
    > for allow/deny logon through Terminal Services. Ipsec can also be used to
    > control access to a computer for all or specific protocols/ports/IP
    > ddress. --- Steve
    >
    >
    > "Bijan Kianifard" <BijanKianifard@discussions.microsoft.com> wrote in
    > message news:A42DCE38-95B4-4229-A0B4-110CE23C069D@microsoft.com...
    > > Hi,
    > >
    > > I'm the administrator of a domain. I want to investigate the connections
    > > between workstations from my workstation. In other words I want connect to
    > > workstation X and check if it is connected to other workstations or not
    > > (by
    > > means of sharing remote desktop...). How can I do it? Do I have to install
    > > a
    > > service for this purpose or is there any third party software to cary out
    > > this job?
    > >
    > > Thanks in advance,
    > > Bijan
    >
    >
    >

  • Next message: Bruce Chambers: "Re: Netcraft Toolbar"

    Relevant Pages

    • Re: How many differences, categories?
      ... >> relocate the pattern by a process similar to the one we used to ... Network logic is counterintuitive. ... In theory the limit to the number of connections per node ... As Kauffman varied this connectivity parameter in his generic networks, ...
      (sci.cognitive)
    • Re: win XP Pro SP2 with latest RDP. Workgroup vs. domain
      ... I do not need to setup RDP port forwarding in the Belkin router. ... the firewall did have in the exceptions screen "Remote Desktop" ... think that the "Allow remote connections RDP" and/or having the firewall RDP ... for network connections. ...
      (microsoft.public.windowsxp.work_remotely)
    • Re: [Fwd: Re: Mainframe not a good architecture for interactive was Re: What is the future of COBOL
      ... programmers do not understand the inner working of CICS and that CICS ... does not keep track of ALL terminals in a mainframe network. ... >> to a Web Server, this means that for an equal number of clients, a Web ... >>server is keeping track of 5 times the connections. ...
      (comp.lang.cobol)
    • Re: Problem for physicalist evolutionists
      ... does not a neural network make. ... potential to have an FPP, and the FPP will be some part of that ... along any of those network connections to "assemble" the picture. ...
      (talk.origins)
    • Re: network failure..
      ... >I remember using a command line command that "refreshed the routing table". ... because your network connections don't have IP ... Please post any reply as a follow-up message in the news group ...
      (microsoft.public.windowsxp.general)