Sign in
 
HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums
Windows Server TechCenter >
> 
> 
How To - Windows Server - Identify TCP Connections and Their Direction

Unanswered How To - Windows Server - Identify TCP Connections and Their Direction

  • Sunday, October 28, 2012 4:58 PM
     
     
    Sign In to Vote
    0

    We are in the process of moving servers from one data center to another.  We have setup VM clones in the new location.  I am looking for a easy (or shall I say least painful) way of identifying the dependency on other servers/apps.  I thought to run netstat, but I need to know the direction of the initiated connection because we need to open firewall to the new data center.

    Right now, I am relying on a combination of netstat (ip/port) output and nslookup (DNS/WINS hostname) output, then parsing with PERL scripting to make the server mapping.  But the direction is very important.

    Any ideas how to tackle this?

    Regards,

    Matt

     

All Replies

  • Tuesday, November 13, 2012 10:36 AM
     
     
    Sign In to Vote
    0
    so you can sniff with network  monitor (microsoft free tool) or ask to network team or security group to sniff 
     
  • Sunday, November 18, 2012 8:26 PM
     
     
    Sign In to Vote
    0

    First of all, note that VM clones may not be a best option for all solutions like AD as an example.

    Identifying dependencies is not an easy task. That is why it will be better to contact your solution vendor technical support for assistance.

    Sniffing is also an option but will be a time consuming one and not an easy task.

    To sniff traffic, you can use Wireshark for this purpose: http://www.wireshark.org/

    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.