Re: How to investigate

From: Steven L Umbach (n9rou_at_nospam-comcast.net)
Date: 05/27/05 

Date: Fri, 27 May 2005 12:42:20 -0500

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

Relevant Pages

  • 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)
  • Re: Cannot connect to workstation within lan
    ... >> command from a Command Prompt: ... > The network is a peer-to-peer network. ... > connections, even though a lan connection has been created to allow the ... - What is the subnet address of your pseudo-server? ...
    (microsoft.public.win2000.general)
  • RE: clients lose connection to server for only a few seconds
    ... Recommend checking the physical network connections. ... The workstations have three applications open that the ... data is stored on the server but the applications are on the local machine. ...
    (microsoft.public.windows.server.sbs)
  • Mapped Drives Losing Connections
    ... - Control Panel -> Network Connections. ... Your 2000 Server has NetBIOS enabled by default, ... >Server version, and we have 5 workstations, each running WinXP Pro. ...
    (microsoft.public.windowsxp.network_web)
  • Re: Problem getting a new XP computer to join an NT 4.0/Win 98 domain
    ... > and all of the computers on this network do log onto a domain, ... > can access any shares enabled on the file server and/or any ... get back to basics and start working from a Command ... > being a domain controller and just change all the workstations ...
    (microsoft.public.windowsxp.network_web)