Netstat and Port 389 (mad.exe)

Discussion in 'Windows Small Business Server' started by Roger Cook, Sep 9, 2004.

  1. Roger Cook

    Roger Cook Guest

    We have approx 16 users (about 8 active at any one time) connected to an SBS
    2003 (std) server.

    I have just run a Netstat -ano command, which reveals 30 or 40 plus TCP
    connections in the CLOSE_WAIT state.
    These are of the form:
    TCP 10.0.0.232:xxxxx 10.0.0.232:389 CLOSE_WAIT 3120

    xxxxx is a different high-numbered port for each line.
    3120 is the Process ID which relates to mad.exe, whilst I gather port 389
    relates to LDAP.

    Whats is going on here. Why are there so many connections in this state

    Roger Cook
     
    Roger Cook, Sep 9, 2004
    #1
    1. Advertisements

  2. Hi Roger,

    mad.exe is one of the primary Exchange processes, and it routinely talks to
    Active Directory (which uses port 389) for various reasons.
    This is normal behavior, and isn't anything to be worried about.

    David Jones
    SBS Product Team
     
    David Jones [MSFT], Sep 9, 2004
    #2
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.