N
Nathan
Can anybody tell me if Entourage will support accessing Exchange over the
Internet via http the same as you can in Outlook?
Internet via http the same as you can in Outlook?
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
B
Barry Wainwright [MVP]
Can anybody tell me if Entourage will support accessing Exchange over the
Internet via http the same as you can in Outlook?
Yes, it does.
In the exchange settigns dialog, just enter the URL of your exchange
server's OWA address (complete with 'http(s)://')
O
obsrving
Actually, there is a very large possibility that it might not work. If
you are using exchange 2003 in its default and suggested security mode
you are out of luck. Entourage does not support cookieauth.dll, only
the older forms authentication. Since most companies don't actually
care about their mac users requests, that would mean no chance of
having your IT group setup the security to support them.
http://support.microsoft.com/kb/909268
you are using exchange 2003 in its default and suggested security mode
you are out of luck. Entourage does not support cookieauth.dll, only
the older forms authentication. Since most companies don't actually
care about their mac users requests, that would mean no chance of
having your IT group setup the security to support them.
http://support.microsoft.com/kb/909268
W
William Smith
obsrving said:Actually, there is a very large possibility that it might not work. If
you are using exchange 2003 in its default and suggested security mode
you are out of luck. Entourage does not support cookieauth.dll, only
the older forms authentication. Since most companies don't actually
care about their mac users requests, that would mean no chance of
having your IT group setup the security to support them.
http://support.microsoft.com/kb/909268
Very interesting. I hadn't heard of this before. But I have to wonder
how many companies are running ISA servers between internal servers and
internal clients. I would think that pointing to an Exchange server (not
necessarily the company's external OWA server) would bypass this problem.
bill
T
Thomas H. Hart III
I use Entourage to access my Exchange Server over http.
<http://webville.net> is my Exchange Server host and the instructions for
set up are on that site. They have both Windows and Mac set up instructions.
Tom Hart
<http://webville.net> is my Exchange Server host and the instructions for
set up are on that site. They have both Windows and Mac set up instructions.
Tom Hart
O
obsrving
Bill: yep, that definitely solves the issue, but unfortunately only if
you are on the network since most companies don't open up direct access
to exchange from the outside. At least I seriously hope no one out
there even thinks about putting exchange directly on the web, just not
a smart decision. Anyone using a front end server with just basic
config will end up with the ISA issue.
I am just suprised that such an obvious issue was missed by the MacBU
and that they haven't come up with a simple solution to a cookie
request issue. MS even has a link to a method in visual basic to make
it work.
you are on the network since most companies don't open up direct access
to exchange from the outside. At least I seriously hope no one out
there even thinks about putting exchange directly on the web, just not
a smart decision. Anyone using a front end server with just basic
config will end up with the ISA issue.
I am just suprised that such an obvious issue was missed by the MacBU
and that they haven't come up with a simple solution to a cookie
request issue. MS even has a link to a method in visual basic to make
it work.
W
William Smith
obsrving said:Bill: yep, that definitely solves the issue, but unfortunately only if
you are on the network since most companies don't open up direct access
to exchange from the outside. At least I seriously hope no one out
there even thinks about putting exchange directly on the web, just not
a smart decision. Anyone using a front end server with just basic
config will end up with the ISA issue.
I am just suprised that such an obvious issue was missed by the MacBU
and that they haven't come up with a simple solution to a cookie
request issue. MS even has a link to a method in visual basic to make
it work.
Absolutely, you'd never want to open up Exchange to the world. But
that's why you use OWA. Run OWA on a separate server pointing to your
Exchange server and it gives you access to your Exchange account from
outside the company firewall without compromising security. And you'd
still never go through an ISA server this way either.
I'm going to guess that your mobile users are trying to use just one
server address (the OWA address) so that they're able to use Entourage
inside and outside your company firewall. Unfortunately, this setup
doesn't always work as you've seen. I'd love to see some feature in
Entourage that allows for a primary (internal) and a secondary (OWA)
address for the same account so that this issue could be resolved.
bill
O
obsrving
I think you are actually missing the point of what I am saying. If you
install exchange 2003 on your internal network, then install a front
end server as per the stock instructions, you will be *always* be using
ISA (windows firewall). This is more common than most people realize
as small to medium sized companies very rarely mix exchange and
macintosh so they either don't see the issue, or this issue (along with
others) pushes them to other solutions. Large companies generally
(though not always) customise their install and make sure that their
front end servers don't use ISA.
In my opinion, this issue hampers a large portion of the up and coming
market, and most people don't have the technical expertise to diagnose
the cause, much less the solution. In all cases with the large
companies, if they are using the default install and it works for them,
they will not be changing their setup just because a few people out
there ask them to.
(the fact that the error message is a plain message with no detail and
no good logging as to why the error pops up does not help.)
The answer is to figure out a way to have entourage support the cookie
version of login, then there should be no more issues for any common
configurations of the OWA server.
install exchange 2003 on your internal network, then install a front
end server as per the stock instructions, you will be *always* be using
ISA (windows firewall). This is more common than most people realize
as small to medium sized companies very rarely mix exchange and
macintosh so they either don't see the issue, or this issue (along with
others) pushes them to other solutions. Large companies generally
(though not always) customise their install and make sure that their
front end servers don't use ISA.
In my opinion, this issue hampers a large portion of the up and coming
market, and most people don't have the technical expertise to diagnose
the cause, much less the solution. In all cases with the large
companies, if they are using the default install and it works for them,
they will not be changing their setup just because a few people out
there ask them to.
(the fact that the error message is a plain message with no detail and
no good logging as to why the error pops up does not help.)
The answer is to figure out a way to have entourage support the cookie
version of login, then there should be no more issues for any common
configurations of the OWA server.
W
William Smith
obsrving said:I think you are actually missing the point of what I am saying. If you
install exchange 2003 on your internal network, then install a front
end server as per the stock instructions, you will be *always* be using
ISA (windows firewall). This is more common than most people realize
as small to medium sized companies very rarely mix exchange and
macintosh so they either don't see the issue, or this issue (along with
others) pushes them to other solutions. Large companies generally
(though not always) customise their install and make sure that their
front end servers don't use ISA.
In my opinion, this issue hampers a large portion of the up and coming
market, and most people don't have the technical expertise to diagnose
the cause, much less the solution. In all cases with the large
companies, if they are using the default install and it works for them,
they will not be changing their setup just because a few people out
there ask them to.
(the fact that the error message is a plain message with no detail and
no good logging as to why the error pops up does not help.)
The answer is to figure out a way to have entourage support the cookie
version of login, then there should be no more issues for any common
configurations of the OWA server.
Thanks for your clarification and that explanation. I'm not familiar
with the practice of setting up a front-end server for internal use but
then again I'm no network architect.
bill
O
obsrving
Definitely no reason to use OWA internally... In my comment I only mean
that the exchange server would be internal. The front end would be
external, or at least in a DMZ with an external port allowance, and a
conduit on the inside to an exchange system.
In that situation, the default config of the front end would include
ISA, even though there might be a firewall infront and behind it before
the exchange server. Microsoft's default install will include
ISA/Windows Firewall and require cookie authentication rather than
forms for Exchange 2003, rendering Entourage 2004 useless for
OWA/Webdav support. Exchange 2000 Front End systems did not have this
configured which is why it works for some and not others.
I don't know if the default for cookie auth requires windows2003 on the
front end or not, but I doubt it.
that the exchange server would be internal. The front end would be
external, or at least in a DMZ with an external port allowance, and a
conduit on the inside to an exchange system.
In that situation, the default config of the front end would include
ISA, even though there might be a firewall infront and behind it before
the exchange server. Microsoft's default install will include
ISA/Windows Firewall and require cookie authentication rather than
forms for Exchange 2003, rendering Entourage 2004 useless for
OWA/Webdav support. Exchange 2000 Front End systems did not have this
configured which is why it works for some and not others.
I don't know if the default for cookie auth requires windows2003 on the
front end or not, but I doubt it.