saA Flag

Discussion in 'Cisco' started by Rob, Mar 18, 2005.

  1. Rob

    Rob Guest

    Hi,
    people at one of our remote site having problem access to exchange server
    here. they have 506e, 6.3. when I checked their PIX, there are 100s of
    connections with saA flags, usually i dont see these connection. does anyone
    know how to fix it?
    The Tunnel seems to be up.
    TCP out 192.168.34.146:135 in 192.168.0.194:3387 idle 0:00:01 Bytes 0 flags
    saA

    Thanks in advance for any help.
    Rob, Mar 18, 2005
    #1
    1. Advertising

  2. In article <423b20ea$>, Rob <> wrote:
    :people at one of our remote site having problem access to exchange server
    :here. they have 506e, 6.3. when I checked their PIX, there are 100s of
    :connections with saA flags, usually i dont see these connection. does anyone
    :know how to fix it?

    Hmmm, that would be "waiting for an outside SYN", "waiting for an
    outside ACK", and "waiting for an inside ACK".

    :The Tunnel seems to be up.
    :TCP out 192.168.34.146:135 in 192.168.0.194:3387 idle 0:00:01 Bytes 0 flags
    :saA

    What happens if you try to telnet to port 135 of that destination?
    --
    Oh, to be a Blobel!
    Walter Roberson, Mar 18, 2005
    #2
    1. Advertising

  3. Rob

    Rob Guest

    I blocked port 135 for outbound (iside interfarce), that fixed the problem,
    but after that people couldnt open their Outlook (Authentication problem) I
    had to re-open that port. Is there any way to eliminate this problem?
    Thanks-Rob
    "Walter Roberson" <-cnrc.gc.ca> wrote in message
    news:d1f9ee$69o$...
    > In article <423b20ea$>, Rob <> wrote:
    > :people at one of our remote site having problem access to exchange server
    > :here. they have 506e, 6.3. when I checked their PIX, there are 100s of
    > :connections with saA flags, usually i dont see these connection. does

    anyone
    > :know how to fix it?
    >
    > Hmmm, that would be "waiting for an outside SYN", "waiting for an
    > outside ACK", and "waiting for an inside ACK".
    >
    > :The Tunnel seems to be up.
    > :TCP out 192.168.34.146:135 in 192.168.0.194:3387 idle 0:00:01 Bytes 0

    flags
    > :saA
    >
    > What happens if you try to telnet to port 135 of that destination?
    > --
    > Oh, to be a Blobel!
    Rob, Mar 21, 2005
    #3
    1. Advertising

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

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. Dmitry Melekhov

    smokeping, SAA, jitter

    Dmitry Melekhov, Nov 25, 2003, in forum: Cisco
    Replies:
    2
    Views:
    1,930
    Dmitry Melekhov
    Dec 5, 2003
  2. Dmitry Melekhov

    SAA, jitter, strange values

    Dmitry Melekhov, Dec 12, 2003, in forum: Cisco
    Replies:
    0
    Views:
    473
    Dmitry Melekhov
    Dec 12, 2003
  3. jhuys

    monitoring SAA stats from IPM

    jhuys, Aug 8, 2004, in forum: Cisco
    Replies:
    0
    Views:
    399
    jhuys
    Aug 8, 2004
  4. ny

    SAA and MRTG

    ny, Jan 24, 2005, in forum: Cisco
    Replies:
    1
    Views:
    1,375
    Daniel Prinsloo - www.CherryFive.com
    Jan 26, 2005
  5. Bernard van de Koppel

    clear int dialer 0triggered by saa

    Bernard van de Koppel, Feb 6, 2005, in forum: Cisco
    Replies:
    0
    Views:
    383
    Bernard van de Koppel
    Feb 6, 2005
Loading...

Share This Page