Entourage 2004 going through proxy server

D

d.adviento

Is there a way to bypass the proxy server so that entourage can
retrieved e-mails directly from Exchange server 2003? At the moment,
even if you include the exchange server to be bypass in
OS X, it does not seem to work. Is there a workaround to this or
this is how it really work?

Thanks,
Dennison
 
D

Den

No one seem to have responded. I guess the answer is NO. Microsoft, can
you confirm this?
 
W

William Smith

Is there a way to bypass the proxy server so that entourage can
retrieved e-mails directly from Exchange server 2003? At the moment,
even if you include the exchange server to be bypass in
OS X, it does not seem to work. Is there a workaround to this or
this is how it really work?
Click to expand...

Hi Dennison!

I saw your response to your message that you haven't had a response and
looked up the original post.

I'm a little confused. Are you required to go through your company's
proxy server to access your Exchange server, all while on your company's
network? This wouldn't be an Entourage limitation but a really odd
network setup causing your problem. However, Entourage has no built in
means for configuring a proxy server. It will use whatever setup your
Mac uses in System Preferences... --> Network --> <network connection>
--> Proxies.

If you're looking to connect to your Exchange server via Entourage from
outside your company's network, this is possible so long as your company
provides webmail services (aka Outlook Web Access or OWA). You wouldn't
enter the name of your Exchange server but rather you would use your
webmail address (something like http://webmail.company.com). You'll also
most likely have to select the option to use SSL as well. LDAP lookups
may not work unless this has been shared to the Internet, which is
unlikely.

Hope this helps! bill
 
D

Den

William,
Thanks for your reponse.
All I want is for Entourage to communicate directly to our Exchange for
internal clients.
At the moment, when I run reports for our Internet Usage on ISA server,
our Exchange server will come up on the top list of websites or address
being accessed. If Entourage mainly uses WebDAV, does it mean it has to
hit our ISA server first. I should be just able to put the Exchange IP
address on System Prefs--Network to be bypassed. But when I do that, it
won't connect to the Exchange server. I should also be able to achieve
faster access to our Exchange if Entourage communicate directly.
Please note that I am talking internal computers here. We have OWA but
that's not my question.
 
W

William Smith

Den said:
William,
Thanks for your reponse.
All I want is for Entourage to communicate directly to our Exchange for
internal clients.
At the moment, when I run reports for our Internet Usage on ISA server,
our Exchange server will come up on the top list of websites or address
being accessed. If Entourage mainly uses WebDAV, does it mean it has to
hit our ISA server first. I should be just able to put the Exchange IP
address on System Prefs--Network to be bypassed. But when I do that, it
won't connect to the Exchange server. I should also be able to achieve
faster access to our Exchange if Entourage communicate directly.
Please note that I am talking internal computers here. We have OWA but
that's not my question.
Click to expand...


Hi Den!

I think I understand what you mean. Your Entourage clients are going
through your ISA server to get to Exchange and this shouldn't be
happening so long as your Exchange server is accessible via WebDAV
internally. Are you able to access webmail (OWA) internally? If not,
then this needs to be enabled on an internal NIC.

Or I suspect your Exchange server may have an IP for internal use and
one for external (OWA) use. Have you made sure your Entourage clients
are using the internal address?

bill
 
D

Den

Bill,

Thanks again. Yes, we can access our OWA internally. Although the
current setup is another ISA server our site is used to direct traffic
to our Exchange Server when staff use OWA. Imagine having 2 exchange, 1
on each site plus a ISA servers on each site. The ISA server on site A
was used to resolve the OWA addresses and fetches the web data to the
appropriate Exchange server.

Example:

Web Address External IP
Internal IP

https://Aowa.com/exchange 210.3.4.5 10.10.0.54
https://Bowa.com/exchange 210.3..4.6 10.1.1.24

Both are on configured on ISA server A.


On my Entourage setup, I use the internal IP address but ISA server
reports that 10.1.1.24:443 was on top on address accessed.

Does this mean that our OWA hosted on the other site causes Entourage
to pass through our ISA server?

Thanks,
Dennison
 
W

William Smith

Den said:
Bill,

Thanks again. Yes, we can access our OWA internally. Although the
current setup is another ISA server our site is used to direct traffic
to our Exchange Server when staff use OWA. Imagine having 2 exchange, 1
on each site plus a ISA servers on each site. The ISA server on site A
was used to resolve the OWA addresses and fetches the web data to the
appropriate Exchange server.

Example:

Web Address External IP
Internal IP

https://Aowa.com/exchange 210.3.4.5 10.10.0.54
https://Bowa.com/exchange 210.3..4.6 10.1.1.24

Both are on configured on ISA server A.


On my Entourage setup, I use the internal IP address but ISA server
reports that 10.1.1.24:443 was on top on address accessed.

Does this mean that our OWA hosted on the other site causes Entourage
to pass through our ISA server?
Click to expand...

Hi Dennison!

This setup is beyond my skill to know the potential setup problems. You
might try posting what's happening and your setup to one of MS ISA
groups such as microsoft.public.isa or
microsoft.public.isa.configuration.

From what you're describing, this sounds like your network is configured
to have clients access the ISA server whether they go through it or not
to get to the Exchange server. I would suspect then that most types of
network traffic may be hitting those servers unnecessarily.

bill
 
Top