DNS and remote Exchange via RPC

  • Thread starter Thread starter Zenak
  • Start date Start date
Z

Zenak

First off I have a domain, mydomain.com. Our AD domain is
mydomain.local. Our website is hosted by a thrd party at
www.mydomain.com. We host our own VPN and Outlook Web Access at
server.domain.com . This works perfectly.

I have been trying to do some more advanced publishing though,
and I just can't get it to work, and I am pretty sure it is a
DNS issue. I have our Exchange server published using RPC at
exchange.domain.com, and an external client connects fine.
Problem is once it connects it resolves to the LOCAL name,
server.mydomain.local, and never connects again. This happens
with laptops that are part of the domain, and my home PC which
has never been in a domain.

So my question is this: Do I need to change my windows domain
from mydomain.local to mydomain.com?

I also seem to be having the same problem with my h.323
gatekeeper, internal clients work perfectly, but external ones
are giving me problems, and it doesn't seem to be firewall
related.

The server in question is an SBS 2000 box, running ISA and
Exchange.
Any advice?
 
In Zenak <[email protected]> made a post then I commented below
:: First off I have a domain, mydomain.com. Our AD domain is
:: mydomain.local. Our website is hosted by a thrd party at
:: www.mydomain.com. We host our own VPN and Outlook Web Access at
:: server.domain.com . This works perfectly.
::
:: I have been trying to do some more advanced publishing though,
:: and I just can't get it to work, and I am pretty sure it is a
:: DNS issue. I have our Exchange server published using RPC at
:: exchange.domain.com, and an external client connects fine.
:: Problem is once it connects it resolves to the LOCAL name,
:: server.mydomain.local, and never connects again. This happens
:: with laptops that are part of the domain, and my home PC which
:: has never been in a domain.
::
:: So my question is this: Do I need to change my windows domain
:: from mydomain.local to mydomain.com?
::
:: I also seem to be having the same problem with my h.323
:: gatekeeper, internal clients work perfectly, but external ones
:: are giving me problems, and it doesn't seem to be firewall
:: related.
::
:: The server in question is an SBS 2000 box, running ISA and
:: Exchange.
:: Any advice?

Changing your internal domain to .com is one resolution.

Another is to create a entry in your hosts file for domain.local to the
internal IP.

Or you can create a mydomain.com zone on your internal DNS server, and
create the appropriate A record it needs to connect to, to resolve to the
internal IP of the Exchange box. This may be your better bet. Give it a try
and let us know how it works.


--
Regards,
Ace

G O E A G L E S !!!
Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

This posting is provided "AS-IS" with no warranties or guarantees
and confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services

Security Is Like An Onion, It Has Layers
HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.
 
Yeah, I agree with Ace. Go with the last solution of an internal DNS zone
that will supply the mydomain.com entry for the Exchange server. This will
intercept and allow the correct resolution for internal clients.

This is a very common solution to this problem.
 
Back
Top