SEG Receive but no Send

[syarbrou]

Not sure if anyone has seen this problem, however we have Exchange on premise and SEG in the DMZ.  Without the seg we can send and receive email by pointing to the webmail URL.  We can also pull up the GAL.  With SEG, we can receive mail, but never send, and the GAL is flaky.  Doesn't come up in Boxer, think it comes up in Outlook Mobile but we are arguing this fact.  Keeps coming up with XML and WBXML unable to decode messages in the logs which I believe are ActiveSync messages.  Been working with AW for months and they can't seem to figure it out.  i'm all logged out with things and looking for help elsewhere.  Any thoughts?

Thanks.

Steve

[BethC]

Are you using CBA with the SEG?

[LukeDC]

What kind of infrastructure is in between the SEG? F5? NetScaler? Firewalls? I'd think something in there is messing with your traffic.

[syarbrou]

OK two stupid responses and thanks for your input.

Beth, what's a CBA?  Is that a Cert Authority?

Luke, you are probably right, but not sure what to tell our F5 guys.  is there something specific if they say nothing is being blocked on port 443 that they could look into?

[LukeDC]

Not stupid at all. Better to ask than guess 😃 CBA - Cert based Authentication.

The F5 usually needs the right persistence settings for the SEG:  https://support.air-watch.com/solutions/sol-16941?qid=MGQ4M2Q1OWMxNjA3NDMxZmE4ZDk1MWM1MTIxZTZmMTM6MT...

[ArianZuta]

Luke Sharkey Is CBA from Client to SEG to Exchange possible? What would be required to have CBA authentication enabled if SEG v2 is used. There is a document showing how to setup KCD for SEG v2 (Client to SEG using CBA and from SEG to Exchange using Kerberos).

[ThomasCheng]

Arian, that's my set up as well and I'm planning to go SEG v2 soon as I know CBA with Kerberos is also supported under v2.

[LukeDC]

I've never had the luxury of using CBA and I'm looking to drop the SEG altogether soon. So I'm not going to V2 if I can help it.

[NTerence]

To add to this thread (although our issue is not exactly the same as the original poster's), we had major issues upgrading from SEG classic to V2.
Immediately after upgrading, we've noticed issues sending email with attachments (or perhaps just large emails) that get worse with time (1-2 hours). The fix was to bounce the server/services. AW support has not been very helpful in diagnosing the issue.  Receiving has not been an issues at all.

We gave up after struggling with it for 4 days.

We rolled back to classic and it's been stable since.

[chengtmskcc]

N T., did you upgrade back from classic to v2 yet?

[NTerence]

No, staying on classic and it's very stable.

[chengtmskcc]

But you will eventually migrate to V2 before support ends for classic, no?