Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 153
  • Last Modified:

How to connect remote W2K users of Outlook 2003 to Exchange 2003?

We have an Exchange 2003 environment.  Most of our remote users use Outlook 2003 on Windows XP SP2 and connect via RPC/HTTPS.  We have started to encounter users that are running Windows 2000 and need all the functionality of Outlook.  Seeing as the W2K clients don't support RPC/HTTPS that have been out of luck.  I have now been charged with the task of making it work.  I am looking for any information that woudl assist in the following environment.

Our Exchange is set up as a front-end/backend configuration.  The front end server have public IPs that are protected by a firewall.  The second NIC in the FE server conencted to the backend servers which all have private addresses.  Obviously the BE network, where the AD controllers live also are on private IPs and are not reachable from the public side of the FE server.

What is the best approach to achieve Outlook access to this configuration from W2K machines that are remote?
0
BladesAway
Asked:
BladesAway
  • 2
2 Solutions
 
SembeeCommented:
If you want the full feature set of Exchange available to those users then there is only one option.
VPN.

You don't have any other options except upgrade those machines to Windows XP so that you can use RPC over HTTPS.

Simon.
0
 
BladesAwayAuthor Commented:
Yes, I'm aware of W2K not supporting the RPC/HTTPS and that VPN is the only other option other than upgrading.    In our type of environment what would be the recommended approach  for VPN?  I need to make it as transparent as possible.  Would ISA be the approach?  Is there something better/easier to use than ISA?  With ISA I assume the VPN client is built-in or at least easily available for W2K?

Thanks
0
 
SembeeCommented:
I don't use ISA for anything other than application publishing.
I have run large sites using Cisco kit for VPN access. It very much depends on where the users are. If they are in another office then you could look at a site to site VPN. If they are roaming then something will have to be installed on the machine. The user will then have to connect to the VPN first, before starting Outlook.

Simon.

--
If your question has been answered, pleased remember to accept the answer and close the question.
0

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now