Re: Outlook -> Exchange 2007 communication issue



On Wed, 9 Jul 2008 10:37:01 -0700 (PDT), HankC <clarkc@xxxxxxxxxxxx>
wrote:

Only Outlook clients with cache mode enabled may talk to our 2007
exchange server.

With cached mode *enabled*, the Outlook 2007 client attempts to
communicate on TCP port 27599 to the mail server and does not receive
a SYN, ACK response. This happens only once. We then see a TCP
request from source port 1275 to destination port 5137. We get a SYN,
ACK back. There is further TCP communication over source and
destination port 5137. The new Outlook profile functions normally.

With cached mode *disabled*, the Outlook 2007 client attempts to
communicate on TCP port 27599 to the mail server and does not receive
a SYN, ACK response. The client continues to send the request
multiple times and never receives a SYN, ACK response. We see no TCP
port 5137 traffic at any time to the mail server. The new Outlook
profile is unusable no matter what settings we attempt to change due
to a communication issue between the client and the Exchange 2007
cluster.

The mail server is behind our Trusted Zone firewall, and a register
value on the server locks these services to ports 5135, 5136, and 5137
respectively


I've never been a fan of putting a firewall between mapi clients and
the Exchange Server. There doesnt seem much to be gained and it causes
issues as you have seen.

Sorry, I dont have an answer for you on this, but it may be worth
contacting Microsoft support if no one here responds.



Thanks,
HankC
.



Relevant Pages

  • Re: Win2K3 Client / Win2K3 & 2K SQL Server DBNETLIB Problem!
    ... > I am also wondering if it has something to do with TCP port allocation. ... Once the client gets to port 5000 it seems to stop and then ... Normally I'd expect a different error from the SQL Server ...
    (microsoft.public.sqlserver.odbc)
  • Re: Win2K3 Client / Win2K3 & 2K SQL Server DBNETLIB Problem!
    ... > I am also wondering if it has something to do with TCP port allocation. ... Once the client gets to port 5000 it seems to stop and then ... Normally I'd expect a different error from the SQL Server ...
    (microsoft.public.sqlserver.connect)
  • Re: Win2K3 Client / Win2K3 & 2K SQL Server DBNETLIB Problem!
    ... > I am also wondering if it has something to do with TCP port allocation. ... Once the client gets to port 5000 it seems to stop and then ... Normally I'd expect a different error from the SQL Server ...
    (microsoft.public.sqlserver.server)
  • Re: Win2K3 Client / Win2K3 & 2K SQL Server DBNETLIB Problem!
    ... > I am also wondering if it has something to do with TCP port allocation. ... Once the client gets to port 5000 it seems to stop and then ... Normally I'd expect a different error from the SQL Server ...
    (microsoft.public.sqlserver.clients)
  • Re: Timeout error when using FTP from Windows DOS prompt
    ... You stated that the windows command line FTP client uses active mode to ... TCP RAINIER:microsoft-ds RAINIER.subnet.mycompany.com:0 LISTENING ... > address and a port. ... > limited range of unreserved ephemeral ports. ...
    (microsoft.public.inetserver.iis.ftp)