RE: Need help with Exchange 2000 behind ISA configuration

  • From: "Mike Carlson" <domitianx@xxxxxxxxxxxxx>
  • To: "'[ISAserver.org Discussion List]'" <isalist@xxxxxxxxxxxxx>
  • Date: Tue, 22 Jan 2002 10:38:05 -0600

When you configure Outlook you have options for POP3, IMAP4, Exchange,
etc. These determine the protocols. I would not use RPC since it is
fairly slow and cumbersome over the internet connections. I would use
OWA myself too or IMAP.

If you use OWA, I would use SSL which uses port 443, not 80.

With IMAP you have the advantage of storing the email on the server by
default, but still use Outlook which is similar to using an Exchange
account. If you select IMAP though, it uses your local copy of Contacts,
not what is stored on the server. You would somehow have to synch the
contacts between the server and the users local machine.

With OWA, you use the contacts on the server.

********************
Mike Carlson
http://www.domitianx.com
domitianx@xxxxxxxxxxxxx

Master Of The Spoon People
Keeper Of None
******************** 

> -----Original Message-----
> From: Lippman, Michael [mailto:Michael.Lippman@xxxxxxxxxxxxxxxx] 
> Sent: Tuesday, January 22, 2002 10:20 AM
> To: [ISAserver.org Discussion List]
> Subject: [isalist] RE: Need help with Exchange 2000 behind 
> ISA configuration
> 
> 
> http://www.ISAserver.org
> 
> 
> I think by protocol he meant how your end users were going to 
> access Exchange.  If this is external access my preference 
> would be to use Outlook Web Access on Port 80 with a SSL 
> certificate.  You don't have to have the SSL but it does 
> encrypt your passwords.  Using an RPC connection to the 
> exchange server can be risky and also result in poor 
> performance.  The RPC connection is basically using Outlook 
> to connect directly to Exchange.  By default when you run the 
> mail wizard if you don't modify any of the settings the RPC 
> connection is setup.
> 
> MRL
> 
> -----Original Message-----
> From: Bob Cheeseman [mailto:bob@xxxxxxxxxxx]
> Sent: Tuesday, January 22, 2002 10:25 AM
> To: [ISAserver.org Discussion List]
> Subject: [isalist] RE: Need help with Exchange 2000 behind 
> ISA configuration
> 
> 
> http://www.ISAserver.org
> 
> 
> Connection at server end is DSL, connection at client end is 
> T1. Not sure what you mean by what protocol on the client. 
> There does not seem to be anywhere in Outlook 2000 to 
> configure this when connecting to exchange.
> 
> 
> Thanx
> 
> Bob
> 
> -----Original Message-----
> From: Mike Carlson [mailto:domitianx@xxxxxxxxxxxxx]
> Sent: Tuesday, January 22, 2002 9:26 AM
> To: [ISAserver.org Discussion List]
> Subject: [isalist] RE: Need help with Exchange 2000 behind
> ISA
> configuration
> 
> 
> http://www.ISAserver.org
> 
> 
> What protocol are you using from the external client to the 
> Exchange box behind ISA? IMAP, POP3, RPC, etc.?
> 
> What kind of connection are you using? DSL, T1, etc.?
> 
> ********************
> Mike Carlson
> http://www.domitianx.com
> domitianx@xxxxxxxxxxxxx
> 
> Master Of The Spoon People
> Keeper Of None
> ********************
> 
> > -----Original Message-----
> > From: Bob Cheeseman [mailto:bob@xxxxxxxxxxx]
> > Sent: Tuesday, January 22, 2002 8:22 AM
> > To: [ISAserver.org Discussion List]
> > Subject: [isalist] Need help with Exchange 2000 behind ISA 
> > configuration
> >
> >
> > http://www.ISAserver.org
> >
> >
> > Prior to diving in head first, we did some testing. We
> built
> > an ISA server, installed Exchange 2000 on the same machine and 
> > configured exchange to handle mail for
> companyname.NET.
> > Currently all employees use email from an ISP at the
> domain
> > companyname.COM. Seemed to work very well.
> >
> > Then we jumped in.
> >
> > We Setup the whole company behind ISA on SBS2000 which is
> a
> > pdc for the domain companyname.COM, with exchange 2000 on
> a
> > separate machine as member server. ISA server has two
> NIC's,
> > 1 with a public IP (ie: 206.47.85.xxx), 1 with an internal 
> private IP. 
> > (ie: 192.168.16.xxx).
> >
> > I made DNS HOST and MX entries on the ISP's servers for
> the
> > exchange server at the IP Address of the ISA server. I ran 
> the secure 
> > mail publishing wizard. I setup an outside
> client
> > (outlook 2000) to connect to an exchange server. put in
> the
> > FQDN of the exchange server and it responded asking me for 
> username, 
> > domain, and password.
> >
> > When I click send and receive, I see dialing, waiting for 
> connection, 
> > a quick flash of another dialogue box I can't read, and no 
> errors. But 
> > no mail either. no send, no
> receive.
> > I know there are two mail messages in the administrator 
> mailbox. If I 
> > Terminal into either the exchange server or
> the
> > ISA server (thus on the internal network) I can send and 
> receive mail 
> > internally.
> >
> > Now to my real question;
> >
> > How do I setup the exchange box behind ISA to handle mail
> > for the companyname.NET domain. I need to do this to do proper 
> > testing. I can't use companyname.COM until it is working 
> perfectly, as 
> > the employees use the email as part
> of
> > their daily work.
> >
> > I'm stuck.
> >
> > Thanx & regards
> >
> > Bob Cheeseman
> >
> >
> >
> >
> >
> >
> > ------------------------------------------------------
> > You are currently subscribed to this ISAserver.org
> Discussion
> > List as: domitianx@xxxxxxxxxxxxx To unsubscribe send a
> blank
> > email to $subst('Email.Unsub')
> >
> 
> 
> ------------------------------------------------------
> You are currently subscribed to this ISAserver.org
> Discussion List as: bob@xxxxxxxxxxx
> To unsubscribe send a blank email to 
> $subst('Email.Unsub')
> 
> 
> ------------------------------------------------------
> You are currently subscribed to this ISAserver.org Discussion 
> List as: Michael.Lippman@xxxxxxxxxxxxxxxx To unsubscribe send 
> a blank email to $subst('Email.Unsub')
> 
> ------------------------------------------------------
> You are currently subscribed to this ISAserver.org Discussion 
> List as: domitianx@xxxxxxxxxxxxx To unsubscribe send a blank 
> email to $subst('Email.Unsub')
> 



Other related posts: