Exchange and AD port use problem

[jkellington]

I'm having a small issue with Outlook (2K + 2K3) on WinXP accessing an Exchange 2K3SP2 server in a Windows 2003 Native Forest (2 DC's, neither of them is the Exchange server). I have remote clients that connect with the exchange server via a broadband (24Mb) wireless VPN connection. The VPN has a global "timeout" value that it uses for tunnel life. If a tunnel opened on any specific port is idle for the "timeout" value, it closes until the client initiates a request on the same port, at which time it opens again. Now we have some applications that require a longer idle time, which is OK, because I isolate the port (or ports) and assign them a longer timeout value. My clients seem to have sporadic performance with the exchange server (having to hit send/recieve to get messages, etc.) My problem lies in the fact that I cannot seem to pin down how Exchange and Outlook through the Active directory and what ports are involved. In fact, Exchange seems to change the port it uses to facilitate client communication on a regular basis (read: weekly). Any AD/Exchange/Network gurus out there that can give me some insight?

Thanks for your help,
Jason

 

[markdmac]

Configure your users to use Outlook over HTTP and you will only need to worry about ports 80 and 443.

I hope you find this post helpful.

Regards,

Mark

 

[jkellington]

And my Outlook 2000 clients?

 

[markdmac]

Why do you even have them?

If you have Exchange 2003 then you have alicense for each user that has an Exchange CAL to be able to use Outlook 2003. In other words, you get free Outlook 2003 with Exchange 2003.

Upgrade your clients. You can automate the upgrade if you like. Look at my FAQ on the deployment via AD: faq96-4996

I hope you find this post helpful.

Regards,

Mark

 

[markdmac]

Why do you even have them?

If you have Exchange 2003 then you have a license for each user that has an Exchange CAL to be able to use Outlook 2003. In other words, you get free Outlook 2003 with Exchange 2003.

Upgrade your clients. You can automate the upgrade if you like. Look at my FAQ on the deployment via AD: faq96-4996

I hope you find this post helpful.

Regards,

Mark

 

[jkellington]

Sorry, way too much work in deployment and reconfiguration at this point.

 

[markdmac]

Only takes 1 hour to set up the AD deployment and then you save the work of having to install in the future.

I hope you find this post helpful.

Regards,

Mark