RE: Commands for closing tcp session on a window box

From: Thomas F. Szabo (tszabo_at_diamondtech.net)
Date: 04/28/04

  • Next message: khayes_at_eastbay.com: "Re: Returned Mails" 
    Date: Tue, 27 Apr 2004 23:58:50 -0400
To: "Tiongster" <tiongster84@yahoo.com.sg>, <security-basics@securityfocus.com>

    In windows xp, you can run NETSTAT -ano to get a list of active TCP/UDP
    and their associated PID. Then you can use kill/taskkill/pskill to
    terminate the process behind the session. You probably want to take a
    look at FPORT to make it a little easier to hunt down what applications
    are using which ports. That way you can stop it from starting up in the
    first place.

    Tom Szabo

    -----Original Message-----
    From: Tiongster [mailto:tiongster84@yahoo.com.sg]
    Sent: Tuesday, April 27, 2004 3:12 AM
    To: security-basics@securityfocus.com
    Subject: RE: Commands for closing tcp session on a window box

    Sorry, the question I'm asking is quite vague without giving more
    details.
    Let's say, on command prompt I entered NETSTAT -A -N and it showed a
    list of TCP and UDP active connections. A session was established i.e.

    TCP 123.183.193.219:1038 64.12.24.151:5190 ESTABLISHED

    Question, is it possible to terminate this Session on the command prompt

    And what command is use to achieve it or what solutions do you suggest?
    Thank you!

    ---------------------------------------------------------------------------
    Ethical Hacking at the InfoSec Institute. Mention this ad and get $545 off
    any course! All of our class sizes are guaranteed to be 10 students or less
    to facilitate one-on-one interaction with one of our expert instructors.
    Attend a course taught by an expert instructor with years of in-the-field
    pen testing experience in our state of the art hacking lab. Master the skills
    of an Ethical Hacker to better assess the security of your organization.
    Visit us at:
    http://www.infosecinstitute.com/courses/ethical_hacking_training.html
    ----------------------------------------------------------------------------

  • Next message: khayes_at_eastbay.com: "Re: Returned Mails"

    Relevant Pages

    • Re: Finding PID to kill the current user logged into UNix
      ... you want to forcibly terminate all terminal sessions owned by ... The ps command is particularly incompatible across OSes. ... This command outputs the process id and the session id for each ... But actually it does not harm if you kill the entire session, ...
      (comp.unix.shell)
    • Re: What is the function/purpose of the Terminal ServicesSysprocs registry entry?
      ... registry key has exactly the same function as the ... When you specify intial program for your session, ... session exits when your initial app and all the processes that ... program would terminate when all the processes except the ones ...
      (microsoft.public.windows.terminal_services)
    • Re: What is the function/purpose of the Terminal ServicesSysprocs registry entry?
      ... When you specify intial program for your session, your session exits when your initial app and all the processes that are running in your session exit. ... All these processes are listed under Terminal Server\Sysprocs registry key. ... Your session started with intial program would terminate when all the processes except the ones listed here are terminated. ...
      (microsoft.public.windows.terminal_services)
    • Re: different policiy
      ... Here are four ways to terminate a disconnected session. ... In Terminal Server Connection Configuration, you can set a global option ...
      (microsoft.public.win2000.termserv.clients)
    • Re: Windows 2000 TS, restricting users to 1 session
      ... I've not tested the SysProcs registry key solution on ... MCSE, CCEA, Microsoft MVP - Terminal Server ... If you have identified the process which keeps the session ... terminate the session when the user closes the environment ...
      (microsoft.public.windows.terminal_services)