«

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.

In article <423b20ea$>, Rob <> wrote:
eople 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!

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" <> wrote in message
news:d1f9ee$69o$...
> In article <423b20ea$>, Rob <> wrote:
> eople 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!