Re: How do I setup a MAPI alias for Exchange?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Lanwench [MVP - Exchange] (lanwench_at_heybuddy.donotsendme.unsolicitedmail.atyahoo.com)
Date: 01/14/05


Date: Fri, 14 Jan 2005 09:23:11 -0500

Jerson wrote:
> Thanks for the reply Lanwench.
>
> "Lanwench [MVP - Exchange]" wrote:
>
>> Jerson wrote:
>>> Hi,
>>>
>>> I have installed exchange SBS for a company. The domain that exists
>>> is domain.local but the company has a registered domain.com.au.
>>> I have setup a DNS zone for the domain.com.au on their SBS server
>>> with host and MX records etc.
>>
>> You do not need to do that. Their MX records, etc., are held on the
>> *public* nameservers - you shouldn't be hosting your public DNS in
>> house unless you have set it up with two separate, dedicated DNS
>> servers (not your SBS box), and if you aren't trying to do this,
>> there is no need to do what you've done in your AD DNS...
>
> Your right.
> But that is not how i setup the DNS.
> The DNS is only for internal resolution of the name
> mail.domain.com.au. As you may know, if an internal user tries to
> connect to mail.domain.com.au and the ip resolves to an external IP
> then any possible future POP3/SMTP clients working from inside the
> private LAN will not be able to connect. Sure i could hardcode the IP
> for these clients but then they could not connect from outside the
> LAN.
>
>>> When i setup the Outlook clients the Microsoft Exchange server in
>>> the MAPI profile will always resolve to servername.domain.local.
>>> How do i get the Exchange server to respond to alias
>>> mail.domain.com.au in the MAPI profile?
>>
>> Is this for RPC over HTTP purposes for external/laptop users?
>> If not, there's nothing to worry about - the internal Exchange
>> server name is fine for all clients.
>
> Yep. It is for RPC over HTTPS and i just checked it again and it is
> working. When i first checked it i think i had an invalid config.

See if this helps: http://www.msexchange.org/tutorials/outlookrpchttp.html

Note that it would have taken less time for us to get to this point if you'd
put "RPC over HTTP" in the subject line and just stated that you need to
make sure the Exchange server name works both internally and externally - it
wasn't very clear what you were trying to do.

>
> Thanks again for the help.
>
>>>
>>> Thanks
>>>
>>> Jason



Relevant Pages

  • RE: VPN Clients Not Registering in AD DNS
    ... via VPN, the DNS records of the VPN clients are unable to be registered. ... Windows 2003 server? ... please let me know whether the clients get the IP ...
    (microsoft.public.windows.server.sbs)
  • Re: Permissions across 2 Forrest
    ... Primary DNS server on 1.x and the 18.x network along with DHCP and WINS. ... For instance ForrestA DNS is now a secondary for Forrest B and vise versa. ... WINS clients must use the same "WINS Database"* ...
    (microsoft.public.windows.server.active_directory)
  • Re: Still strange not fully working DNS server
    ... On none of the computers (both DC and clients) no firewall software is ... For the rest nothing happens in the DNS forward lookup zone. ... Is the new server Global catalog? ... The config you mentioned was not configured so I have configured ...
    (microsoft.public.windows.server.dns)
  • Re: Client installation frustration.
    ... not, apparently, any DNS lookup issues on my network. ... connection's addresses in DNS" and "Use this connection's DNS suffix in DNS ... is a file and print server that we have at one of our secondary sites. ... Is there any way to cancel all current requests to install clients? ...
    (microsoft.public.sms.admin)
  • Re: problem with xp clients and windows 2003
    ... We now have the cross cable running from the room's switch ... >> policy but logs into the server. ... >> aware that this is a DNS issue but I have TRIPLE checked the DNS ... >> If I do NSlookup from the problematic clients, ...
    (microsoft.public.windows.server.networking)