Outlook 2003 not authenticating to Exchange 2003 server which is not part of the local domain.

 I am not sure if I have set this up correctly but I have the Exchange server setup in its own domain, own DNS server outside my firewall. My internal networks have its own Domain/ forest two Global catalogs, DNS, DHCP.

My thought was to keep the exchange server completely separate and if by chance it gets hacked into there is no chance of compromising our internal network shares. It was double work to key in all the users into the email/exchange domain but I thought for security it was worth it.  In outlook, you specify the exchange server name (mail.mydomain.com) and then when you click on check name it would prompt for a username and a password (mydomain.com\username)  This works fine for everyone at the corporate office and any remote location that is not a member of the domain mydomain.local

 

The internal domain is called mydomain.local (192.168.1.x network) and the Exchange domain is mydomain.com (24.x.x.x)

 

Food for more thought…

The internal domain client all talk back to the PDC for DNS (192.168.1.86) which forwards all outbound DNS to ISP. As I said though for all the computers at the corporate office this is working fine it is just the remote branches whose computers are members of the corporate domain (mydomain.local). They can ping the exchange server, they can telnet to port 25 on the exchange server, just can not resolve the name during the initial setup.

 

I have applied the hotfix to the 2 GC servers and the 1 Exchange server and have no such luck. Reference Microsoft KB 898060
I am stumped, any ideas?

tgeddingsAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Netman66Commented:
You'll have to resort to using HOSTS for this.

Have you thought about OWA rather than Outlook when offsite?  You can also look at RPC over HTTP.

0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
tgeddingsAuthor Commented:
Turns out according to Microsoft that this is an unsupported configuration. I didn't realize this at the time but hey I am an idiot. What changes to the host file will need to be made, since they are able to ping and telnet(port 25 only) to the exchange server?

Microsoft recommending moving the exchange server to be within the local domain and put it behind the firewall with the rest of our network. That seems like alot of work? What is everyone else thoughts?
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.