Hello all,
I have recently put a second Exchange 2000 server in place in our organization. Everything works good but my question is regarding OWA. I have noticed that if I go to OWA on my original exchange box but my mailbox is on the new machine, OWA redirects me to the new machine's URL. That is fine when accessing OWA from inside the LAN but since I do not allow Internet traffic to go to the new box users on the new machine can not use OWA. I know that a front-end server for this will act as a proxy for the OWA traffic and get the data from the back end server that the mailbox resides on for the user transparently.
My question is if there is a way to make a back-end server also do that for a mailbox on another server. My scenario is that I do not yet have the budget approval for another piece of hardware and software licensing to put up a front-end server, although I know that is the preferred and supported method. If anybody has am idea how to get around that, please let me know. Thanks in advance!
I have recently put a second Exchange 2000 server in place in our organization. Everything works good but my question is regarding OWA. I have noticed that if I go to OWA on my original exchange box but my mailbox is on the new machine, OWA redirects me to the new machine's URL. That is fine when accessing OWA from inside the LAN but since I do not allow Internet traffic to go to the new box users on the new machine can not use OWA. I know that a front-end server for this will act as a proxy for the OWA traffic and get the data from the back end server that the mailbox resides on for the user transparently.
My question is if there is a way to make a back-end server also do that for a mailbox on another server. My scenario is that I do not yet have the budget approval for another piece of hardware and software licensing to put up a front-end server, although I know that is the preferred and supported method. If anybody has am idea how to get around that, please let me know. Thanks in advance!