Re: Rename Windows Domain with Exch23K deployed.

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: Dan Townsend [MSFT] (dtown_at_online.microsoft.com)
Date: 02/25/04 

Date: Wed, 25 Feb 2004 06:00:31 -0600

"The exchange server then instructs the client that it is in fact called
eden.blobble.com, at which point the laptop cannot continue doing anything,
and the configuration stops since there is no working DNS for
eden.blobble.com"

What happened to your internal DNS? When you VPN the client should look at
the internal DNS which should still show the internal domain name of
bobble.com - so this should work fine...

"To get the RPC over HTTP working, we followed the Microsoft documentation,
patched the Domain controller, installed the relevant patches on the Outlook
client and got it working, as long as we use eden.blobble.com as the DNS
name to connect to the RPC proxy running on the exchange server."

Which setting is this in Outlook? If its the Exchange server have you tried
just EDEN? If so what happens in the web logs? Also if you ping EDEN using
rpcping does it error? It shouldn't.

Test https://mail.widget.com/rpc (with IE) and see if you get the 403.2

"Setting up RPC over HTTP is not at that level of ease yet, and it does not
seem to want to work at all when you have different external and internal
DNS domains."

Supposed to become better with Exchange 2003 SP1 - I can't wait. Hopefully
a nice tool that isn't command line.

"I am going to re-establish the testing platform for this again, and have
another bash since Dan and you seem to think I am barking up the wrong tree
and that it should just work."

It might seem like that at times - but I'm really trying to help. I haven't
actually done it but I can usually get it fixed if its ever supposed to
work. 

-- 
Hope that helps,
Dan Townsend
This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send email to this address, post a reply to this newsgroup.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Alex Griffin" <nntpuser@hotmail.com> wrote in message
news:o40n30hkchqq1jshnnt7741mge3l93e9lv@4ax.com...
> On Tue, 24 Feb 2004 10:31:43 -0600, "Dan Townsend [MSFT]"
> <dtown@online.microsoft.com> wrote:
>
> >"Because Exchange seems to insist on using its internal name, we are
> >somewhat rudderless."
> >
> >Can you clarify what you mean by that?  We use the internal domain naming
> >for DNS and by default for the SMTP domain (this can be changed very
> >easily).  I don't see how that really causes an issue.  Please eloborate
so
> >I can help.
>
> Some assumptions:
>
> The server has a netbios name of EDEN, and it considers its DNS name
> to be eden.blobble.com. So blobble.com is the name of the current AD
> DNS domain (a domain which we have lost control of in the real world,
> due to a fall out between directors). Our company has decided to
> rebrand to widget.com, a domain which we have complete control of. For
> external DNS purposes, the MX records of widget.com points to
> mail.widget.com, which in actuality connects through to
> eden.blobble.com. That exchange server quite happilly accepts and
> sends out mail as widget.com.
>
> What do I mean by its "internal name". If I take a laptop home, and
> establish a VPN, and I setup the laptop with Outlook 2003, and I tell
> it to talk to mail.widget.com and that my username is blah, it goes
> off and talks to the Exchange server. The exchange server then
> instructs the client that it is in fact called eden.blobble.com, at
> which point the laptop cannot continue doing anything, and the
> configuration stops since there is no working DNS for
> eden.blobble.com. That's what I mean by the exchange server insisting
> on using its "internal name". This can of course be fixed with hosts
> file entries........
>
>
>
> >"Hence we thought renaming the domain would allow us to "fix" this
> >situation, so we would once again match our external DNS to our internal
> >DNS."
> >
> >What is the actual problem your facing?  The client on the internet
doesn't
> >need to know anything about the internal stuff.  It only needs to know
the
> >RPC Proxy (ip and name) and the Exchange server (name - not ip).  This is
> >why we add the netbios and FQDN to the RPC Proxy reg key on the server.
> >Only the server at that point has to be able to resolve those names.
>
> To get the RPC over HTTP working, we followed the Microsoft
> documentation, patched the Domain controller, installed the relevant
> patches on the Outlook client and got it working, as long as we use
> eden.blobble.com as the DNS name to connect to the RPC proxy running
> on the exchange server.
>
> We setup SSL certificates with eden.blobble.com and mail.widget.com in
> IIS on the proxy server, if we use the mail.widget.com, it just does
> not want to play, it never gets past authenticating the user it seems.
> If we use eden.blobble.com (backed up with hacked hosts files to frig
> the fact that blobble.com is no longer under our control and pointing
> somehwere else), it connects through quite happilly.
>
> -- 
> Alex Griffin
>
>

Relevant Pages

  • RE: Internet Speed
    ... IP and DNS as dynamically". ... you saying the server IP address should not be the primary DNS under Internet ... it is recommend to configure all SBS client computers' IP and DNS as ...
    (microsoft.public.windows.server.sbs)
  • Re: Cant browse Network on VPN - seems to be a rule issue?
    ... Client to make sure it is getting all the details correct (ignore the Default ... connection to use the ISA DNS entries which are all the valid 'external' ... Microsoft Internet Security & Acceleration Server: ...
    (microsoft.public.isa.vpn)
  • Re: Slow network browsing (folder content)
    ... IP that has DNS Service installed on. ... Are all of your client machines only using 192.168.0.1 for DNS? ... able to browse internet. ... > of headaches and problems to let another device offer Internet connectivity ...
    (microsoft.public.windows.server.dns)
  • Re: Problem(s) resolving names with natd/ipfw.
    ... Then set all the clients' primary DNS to ... that of the internal IP of your gateway. ... > The problem is that the Windows XP client CANNOT ... > access the Internet with alphabetic names (should be ...
    (freebsd-questions)
  • Re: Exchange 4 Calendar only, Mail is externally, problem sending
    ... my case the Exchange server does NOT accept mail directly from the internet. ... The client has Outlook with both external pop3 and internal ... the user populates the mail type as "EX" instead of SMTP. ...
    (microsoft.public.exchange.admin)