My issue stems from the fact that the people who did the initial implementation of the AD in our organization did not upsize the NT domain to a owned dns name, ie: the fqdn of our domain actually belongs to someone else. This has not presented a big deal till now, becuase i just use a different namespace on the internet and for mail and everything works ok. my internal (example) notowned.org my extneral (example) owend.org In our ex2003 deployment of webmail, we used two Front-End servers and every thing works correctly example: https://webmail.owned.org The issue that I am having is around connecting legacy users to the 2007 web access servers. When I point a client at the new ex2007 Client access server: https://owa.owned.org/exchange, the client is redirected back to their home mail server, https://server1.unowned.org; which internally works, externally it doesn't, since i don't own the domain, i can't do anything from a DNS perspective to translate the name. My question is: is there any setting, in either version of exchange, that will let me set the server value for the owa server for ex2003 users, so that in the redirect from the 2007 CAS, it will redirect to to the legacy front-end server and not the home mail server? Thanx, -Steve

solved my own problem: deployed ISA 2006, use the address re-write functionality on an access rule to re-write the host header value to the front-end server