[premnik]

Hi there,

we are about to set some fw rules on our network.

I have read that when a new message arrives in a user’s mailbox, Microsoft Exchange notifies the BlackBerry Messaging Agent.
Don't you know wich tcp port uses MS Exchange to communicate with BES ? (we need to add this to fw rules).

Thanks a lot.

[scorp508]

Originally Posted by premnik

Hi there,

we are about to set some fw rules on our network.

I have read that when a new message arrives in a user’s mailbox, Microsoft Exchange notifies the BlackBerry Messaging Agent.
Don't you know wich tcp port uses MS Exchange to communicate with BES ? (we need to add this to fw rules).

Thanks a lot.

Exchange doesn't talk to BES. Exchange has no idea BES is poking it all the time like a hot poker. BES scans the user mailboxes for changes and then performs the necessary actions to get them to the handhelds.

[penguin3107]

Originally Posted by scorp508

Exchange doesn't talk to BES. Exchange has no idea BES is poking it all the time like a hot poker. BES scans the user mailboxes for changes and then performs the necessary actions to get them to the handhelds.

Sorry, but this is not true.
In Domino and Groupwise environments, BES scans the mailboxes on a schedule for changes... but this is not the case for Exchange.

Exchange uses MAPI and sends a UDP Notify packet to BES to alert it that there is a new message to be delivered.

If there is heavy network traffic, or some other reason to prevent the UDP Notify packet from reaching BES, only then will BES issue a mailbox rescan to have a look around.

[penguin3107]

Originally Posted by premnik

Hi there,

we are about to set some fw rules on our network.

I have read that when a new message arrives in a userxxx8217;s mailbox, Microsoft Exchange notifies the BlackBerry Messaging Agent.
Don't you know wich tcp port uses MS Exchange to communicate with BES ? (we need to add this to fw rules).

Thanks a lot.

Is your BES not on the same local LAN as your Exchange server?
If not, then why?

Exchange <--> BES communication is via MAPI. You'd want to allow any and all ports defined by the MAPI protocol.

[scorp508]

Originally Posted by penguin3107

Exchange uses MAPI and sends a UDP Notify packet to BES to alert it that there is a new message to be delivered.

Think about the situation of this post. If the client established the session first then this is merely part of the MAPI conversation and since the client established it there should (in most cases) be no need for FW rule adjustment.

[knottyrope]

Originally Posted by penguin3107

Sorry, but this is not true.
In Domino and Groupwise environments, BES scans the mailboxes on a schedule for changes... but this is not the case for Exchange.

Exchange uses MAPI and sends a UDP Notify packet to BES to alert it that there is a new message to be delivered.

If there is heavy network traffic, or some other reason to prevent the UDP Notify packet from reaching BES, only then will BES issue a mailbox rescan to have a look around.

You are a basket full of knowledge. Keep up the great work.

[hdawg]

Originally Posted by scorp508

Think about the situation of this post. If the client established the session first then this is merely part of the MAPI conversation and since the client established it there should (in most cases) be no need for FW rule adjustment.

You can assign static ports for MAPI communication with Exchange.

READ: Exchange Server static port mappings

[hdawg]

Originally Posted by knottyrope

You are a basket full of knowledge. Keep up the great work.

did you give him an atta boy?

really?

[NJBlackBerry]

Probably knot

[hdawg]

Originally Posted by NJBlackBerry

Probably knot

you just ... omg.

[knottyrope]

Originally Posted by hdawg

did you give him an atta boy?

really?

Yes I did.