[isalist] Re: Supporting RPC Outlook Clients

  • From: "John T \(Lists\)" <johnlist@xxxxxxxxxxxxxxxxxxx>
  • To: <isalist@xxxxxxxxxxxxx>
  • Date: Fri, 14 Apr 2006 09:06:26 -0700

Just to be clear, you are not using split DNS. You are indeed using 2
different domain names, one being problematic and ill-used, and the other
being an actual registered domain name.

 

John T

eServices For You

 

"Seek, and ye shall find!"

 

-----Original Message-----
From: isalist-bounce@xxxxxxxxxxxxx [mailto:isalist-bounce@xxxxxxxxxxxxx] On
Behalf Of Rob Moore
Sent: Friday, April 14, 2006 5:55 AM
To: isalist@xxxxxxxxxxxxx
Subject: [isalist] Supporting RPC Outlook Clients

 

Using: ISA 2004 Standard, Server 2003, Outlook 2003. 

I've finally gotten around to implementing RPC over HTTP for my Outlook
clients. We have a split DNS, with our internal DNS names ending in
".local".

I've gotten an external client to connect, but only if I add the Exchange
server's external IP address and internal name to the Hosts file on the
external PC (as described in Tom's article
<http://www.isaserver.org/articles/2004securerpc.html>
http://www.isaserver.org/articles/2004securerpc.html). When I configure the
client, I put in "mail.afsc.org"--the public name of our Exchange server--as
the server name. When it resolves, it resolves to "delta.afsc.local"--the
internal name of our Exchange server. This resolution works, even without
the addition to the Hosts file. However, without the addition to the Hosts
file, the client can't actually connect to "delta.afsc.local".

So, these are my questions: 
1. Is there a way around using the Hosts file? 
2. If not, can someone tell me how to script the necessary info into the
Hosts file? (I'm not much of a scripter, and I'd like to avoid giving my
fairly non-technical users instructions for editing it themselves.) 

        Alternatively, I suppose I could create the necessary Hosts file and
give that to them. But there are a couple of problems with that: first, our
non-techie users would likely put it in the wrong place; second, I've found
that our anti-spyware program also uses the Hosts file, and I don't want to
mess that up.

        I can't use AD to make the changes to the Hosts file because many of
the computers that need the change are personal computers that are not
members of our domain.

Thanks, 
Rob 

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 
Rob Moore 
Network Manager 
215-241-7870 
Help Desk: 800-500-AFSC 

Other related posts: