How does exchange talk to outlook

[tshad]

How does exchange talk to outlook?

Is it a push/pull relationship? Does outlook make a request to exchange at
various intervals? Or does it run as some type of service waiting for a
request on a port from exchange?

Thanks,

Tom.

 

[neo [mvp outlook]]

traditional communications take place over what is called remote procedure
calls (or RPC for short). more or less when outlook starts, it makes an RPC
call to port 135 on the exchange server. port 135 tells the client what
ports the information stores (private [mailbox] & public folders) are on.
outlook then in turn makes RPC calls to those two new ports and closes port
135. from there outlook does one last thing... it registers itself to
receive notification events from the server. these notification events
travel by UDP. port is never the same.

did this help or make things worse?

 

[tshad]

traditional communications take place over what is called remote procedure
calls (or RPC for short). more or less when outlook starts, it makes an
RPC call to port 135 on the exchange server. port 135 tells the client
what ports the information stores (private [mailbox] & public folders) are
on. outlook then in turn makes RPC calls to those two new ports and closes
port 135. from there outlook does one last thing... it registers itself
to receive notification events from the server. these notification events
travel by UDP. port is never the same.

did this help or make things worse?

It helps. I was just curious to know how it works. I was used to Eudora,
which you set a timer to check every x minutes to query the pop server to
see if anything was available.

If the port is different, how does outlook get the notification?

Tom.

 

[neo [mvp outlook]]

When outlook registers with the Exchange server to receive UDP
notifications, it tells the server what port it will be listening to.

traditional communications take place over what is called remote
procedure calls (or RPC for short). more or less when outlook starts, it
makes an RPC call to port 135 on the exchange server. port 135 tells the
client what ports the information stores (private [mailbox] & public
folders) are on. outlook then in turn makes RPC calls to those two new
ports and closes port 135. from there outlook does one last thing... it
registers itself to receive notification events from the server. these
notification events travel by UDP. port is never the same.

did this help or make things worse?

It helps. I was just curious to know how it works. I was used to Eudora,
which you set a timer to check every x minutes to query the pop server to
see if anything was available.

If the port is different, how does outlook get the notification?

Tom.

 

[tshad]

When outlook registers with the Exchange server to receive UDP
notifications, it tells the server what port it will be listening to.

Is that even when the Outlook is closed?

I just got a notification on my screen that I had a message and Outlook
wasn't open at that time.

Tom

traditional communications take place over what is called remote
procedure calls (or RPC for short). more or less when outlook starts,
it makes an RPC call to port 135 on the exchange server. port 135 tells
the client what ports the information stores (private [mailbox] & public
folders) are on. outlook then in turn makes RPC calls to those two new
ports and closes port 135. from there outlook does one last thing... it
registers itself to receive notification events from the server. these
notification events travel by UDP. port is never the same.

did this help or make things worse?

It helps. I was just curious to know how it works. I was used to
Eudora, which you set a timer to check every x minutes to query the pop
server to see if anything was available.

If the port is different, how does outlook get the notification?

Tom.

How does exchange talk to outlook?

Is it a push/pull relationship? Does outlook make a request to
exchange at various intervals? Or does it run as some type of service
waiting for a request on a port from exchange?

Thanks,

Tom.

 

[neo [mvp outlook]]

Check your processes list in task manager. Bet you will find Outlook and/or
the MAPI spooler still running. (Outlook 2003 doesn't have a MAPI spooler
by the way. So its just good ol' Outlook.)

When outlook registers with the Exchange server to receive UDP
notifications, it tells the server what port it will be listening to.

Is that even when the Outlook is closed?

I just got a notification on my screen that I had a message and Outlook
wasn't open at that time.

Tom

traditional communications take place over what is called remote
procedure calls (or RPC for short). more or less when outlook starts,
it makes an RPC call to port 135 on the exchange server. port 135
tells the client what ports the information stores (private [mailbox] &
public folders) are on. outlook then in turn makes RPC calls to those
two new ports and closes port 135. from there outlook does one last
thing... it registers itself to receive notification events from the
server. these notification events travel by UDP. port is never the
same.

did this help or make things worse?

It helps. I was just curious to know how it works. I was used to
Eudora, which you set a timer to check every x minutes to query the pop
server to see if anything was available.

If the port is different, how does outlook get the notification?

Tom.


How does exchange talk to outlook?

Is it a push/pull relationship? Does outlook make a request to
exchange at various intervals? Or does it run as some type of service
waiting for a request on a port from exchange?

Thanks,

Tom.