Entourage "exchange account (Not connected)"

[Asger H J]

Hi
After I set up an exchange account in Entourage 2004 SP2 I get (not
connected) behind the account's name
Locally it is working fine, but over the internet through NAT'ed router i
get the problem. OWA working fine! I also get promted that the certificate
is unknown (but this is not the problem), so there IS a connection of some
kind???



Pliiiizzzz help


Asger

 

[William Smith]

Hi
After I set up an exchange account in Entourage 2004 SP2 I get (not
connected) behind the account's name
Locally it is working fine, but over the internet through NAT'ed router i
get the problem. OWA working fine! I also get promted that the certificate
is unknown (but this is not the problem), so there IS a connection of some
kind???

Hi Asger!

You may need to open your Account in Entourage and select the option
"This DAV service requires a secure connection (SSL)".

Hope this helps! bill

 

[scott boettcher]

I doubt it will work without some sort of VPN connection to your office.

SB

 

[Corentin Cras-Méneur]

I doubt it will work without some sort of VPN connection to your office.

Not necessarely. I can access my account from home. Most of the time,
connections from "the outside" go through https though,

Corentin

 

[Gary Small]

Trying to join in on this thread....
My company recently switched to Exchange Sever 2003. OWA works fine. I
initially log in to "http://mail.domain.com". Then I key in my Exchange
Email address, and am re-directed to: https://mail2.domain.com. I then log
in using "NT" credentials (nam\userid) then password. Finally I am in, and
it's a beautiful thing. At work, my company-provided Windows box runs an
initial Log in script, and using Outlook 2003, obviously synchronize and
work all day in Outlook. We have numerous Exchange servers (mine is
NHQSEXC23). I'm actually including some legitimate server names in hopes
that one of my co-workers will recognize these names, and jump in.

My company (a major airline) considers itself to be a Microsoft partner, and
is VERY unsupportive of Mac users. Using Entourage 2004 (SP2) I simply can
NOT connect to Exchange either at work (with my iMac which is on the LAN),
or from home via internet. I have been at this for over a year. In the
Exchange server field of the Entourage set up, I have tried NHQSEXC23 (the
internal name), http://mail.domain.com/exchange and
https://mail2.domain.com. The last of these actually returns the "user id or
password are incorrect", so it seems to be connecting somewhat, but failing
to authenticate. I should add that my company also uses proxy servers, but I
am able to get to MOST web sites from the internal LAN. I can NOT access my
personal POP mail (not the Exchange stuff) using Apple Mail or Entourage, so
it appears that the proxy server has some ports blocked (I guess). I have
asked our IT support people (EDS) if LDAP is active, but have NOT been given
an answer.

I'm just dead in the water and very frustrated, so would be grateful if
anyone has ideas.

Merci en avance pour votre aide.

Gary

(quelque fois etudiant de Francais et les ordinateurs)

 

[royl]

Hallo Gary,

Entourage 2004 was running well since over a year on my G4 power book
under MAC OS Panther now with MacOSX10.3.9. After I installed the
latest Microsoft Service pack in early november 2005 for office 2004
and the patch 11.2.1 which mostly affects entourage I cannot connect
anymore to our microsoft exchange server. I get the message

unable to establish a secure connection nlbmsx.ka.fzk.de because the
correct root certificate is not installed.

After I reinstalled the root certificate issued by my company I still
cannot connect to our exchange server. I am as frustrated as you are in
particular because the update destroyed my ability to use entourage. I
had to go back to OWA which works but is not so convenient. Do you have
any idea what could be the problem?

Yours Peter

 

[scott boettcher]

Try using: "NHQSEXC23.domainname.yourcompany.com/exchange" No quotes.

Scott

 

[Corentin Cras-Méneur]

Try using: "NHQSEXC23.domainname.yourcompany.com/exchange" No quotes.

Scott

As far as I can tell from the similar setup we have here, using the the
backend server in the address doesn't necessarely help (especially when
the net admin move the accounts around without warning anyone :-> ).
Really, the easiest way to go has always been for us here to connect in
the web browser, let the server redirect us to wherever it wants and
once we're in our account on the proper OWA server: copy the URL and use
it as is in Entourage.
Here we are on a backend server as well but the server does not accept
http (WebDAV) requests. Everything is chanelled through a dedicated OWA
server.
We conect to server.domain.com and get redirected to
owaserver.domain.com and never ever manage to connect through
backend.domain.com.

Corentin

 

[Gary Small]

Thanks. The URL, when I'm actually looking at my "Inbox" in OWA is :
https://mail2.domain.com/CookieAuth.dll?GetLogonWrapper?url=/exchange/&r
eason=0

So I tried pasting this into the Exchange Server field, but nothing happens.
Now I am doing this at home and NOT on the LAN. I read somewhere that this
should work WITHOUT VPN. I have not tried this yet at the office (which is
on the LAN).

Next I tried Mr. Boettcher's suggestion, but I think I might need to be on
the LAN for that to work. It does not from home (without VPN).


Any other ideas?

gary

 

[Gary Small]

No idea at all, since I have never been able to connect even before the SPs.
If I could get to the point that you were, I would uninstall Entourage, then
re-install without the SPs. My company is just very difficult to work with,
and gives me no Mac support.

Hallo Gary,

Entourage 2004 was running well since over a year on my G4 power book
under MAC OS Panther now with MacOSX10.3.9. After I installed the
latest Microsoft Service pack in early november 2005 for office 2004
and the patch 11.2.1 which mostly affects entourage I cannot connect
anymore to our microsoft exchange server. I get the message

unable to establish a secure connection nlbmsx.ka.fzk.de because the
correct root certificate is not installed.

After I reinstalled the root certificate issued by my company I still
cannot connect to our exchange server. I am as frustrated as you are in
particular because the update destroyed my ability to use entourage. I
had to go back to OWA which works but is not so convenient. Do you have
any idea what could be the problem?

Yours Peter

I'm just dead in the water and very frustrated, so would be grateful if

 

[Corentin Cras-Méneur]

Thanks. The URL, when I'm actually looking at my "Inbox" in OWA is :
https://mail2.domain.com/CookieAuth.dll?GetLogonWrapper?url=/exchange/&r
eason=0

Ouch ouch.... do you happen to know what type of server you have ?? What
version of Exchange ?? That really doesn't look like the standard
addresses we usually get....


Corentin

 

[Gary Small]

I guess I really don't know how to answer this. I know that it is Exchange
Server 2003. I had a support ticket with our IT support (EDS) and got word
back today, that they had "fixed" my problem by enabling the required
protocols that had (apparently) been disabled. Again, internally, we have
numerous Exchange servers. The OWA front end is just as we have discussed.My
Outlook 2003 client at work syncs up with NHQSEXC23. The new implementation
of OWA (on http://mail.mycompany.com/exchange/logon.asp) has a Microsoft
Exchange Server 2003 banner. I am continuing to play "trial and error" to
get this to work, and would definitely be willing to pay M$ a support call,
if I had any hopes that "Real time" Tech support would be able to solve
this.

I'm not clear on whether this needs to be done while on the LAN behind the
firewall, can be done at home without VPN etc. I've seen some discussions of
using a functional Outlook set up to get IP addresses, but missed the point
of that.

I do know that my company relies heavily on these ".asp" servers, so maybe
that is the answer to your question, and may or may not make this solvable.

Again, and ideas, suggestions from anyone is sincerely appreciated.

gary

 

[Corentin Cras-Méneur]

My
Outlook 2003 client at work syncs up with NHQSEXC23. The new implementation
of OWA (on http://mail.mycompany.com/exchange/logon.asp) has a Microsoft
Exchange Server 2003 banner. I am continuing to play "trial and error" to
get this to work, and would definitely be willing to pay M$ a support call,
if I had any hopes that "Real time" Tech support would be able to solve
this.

THe .asp at the end of the link makes me fear that the server is running
some kind of script that makes it incompatible.
The address I have looks like that:
http://mail.mycompany.com/exchange/me/

It looks lto me that they have implemented some measures that make the
whole thing not compatible.

Corentin

 

[Tim Lapin]

THe .asp at the end of the link makes me fear that the server is running
some kind of script that makes it incompatible.
The address I have looks like that:
http://mail.mycompany.com/exchange/me/

It looks lto me that they have implemented some measures that make the
whole thing not compatible.

Corentin

On a Mac, the ".asp" extension refers to an "Apple System Profiler" data
file. I had a person run into this one a while back, unfortunately, I
really don't remember anything more.

Try a search using either Google or "www.macosxhints.com". I know there
was an answer. Like Corentin, though, I fear that the answer might not
be good.

To get you started, here is a link to a converter program. I don't know
how much it will help but it is worth a look:
http://mac.sofotex.com/download-126034.html

 

[Corentin Cras-Méneur]

On a Mac, the ".asp" extension refers to an "Apple System Profiler" data
file. I had a person run into this one a while back, unfortunately, I
really don't remember anything more.

Yeah, but that's not the case here. It compes from the ASP.net Microsoft
technology. It's a bunch of functions like what you'd get through .cgi
scripts.
It's often used to manipulate database queries.

Try a search using either Google or "www.macosxhints.com". I know there
was an answer. Like Corentin, though, I fear that the answer might not
be good.

To get you started, here is a link to a converter program. I don't know
how much it will help but it is worth a look:
http://mac.sofotex.com/download-126034.html

That won;t do the trick.... the .asp does not refer to an acutal file,
but to a request on the server :-\ The page is dynamically generated
through the script.

Corentin

 

[Tim Lapin]

That won;t do the trick.... the .asp does not refer to an acutal file,
but to a request on the server :-\ The page is dynamically generated
through the script.

Corentin

That was what the other person saw when she/he had the problem to which
I was referring. Instead of triggering a script on the website, it
launched apple system profiler and of course failed miserably to do what
was supposed to happen.

Here is an example problem report that someone else saw in conjunction
with .asp pages:
http://www.planetpdf.com/forumarchive/95334.asp

Another:
http://www.macwindows.com/citrix.html


As I said, I truly wish I could remember what the fix was. :-(

 

[Adam Bailey]

THe .asp at the end of the link makes me fear that the server is running
some kind of script that makes it incompatible.
The address I have looks like that:
http://mail.mycompany.com/exchange/me/

FWIW, my OWA URL looks something like:
https://webmail.example.com/exchweb...https://webmail.example.com/exchange&reason=0

....and Entourage works just fine with it. I use
<https://webmail.example.com/exchange/> in Entourage.

 

[Corentin Cras-Méneur]

FWIW, my OWA URL looks something like:
https://webmail.example.com/exchweb/bin/auth/owalogon.asp?url=https://webm
ail.example.com/exchange&reason=0

...and Entourage works just fine with it. I use
<https://webmail.example.com/exchange/> in Entourage.

Very interesting indeed... That's worth testing here.
I wonder what they put in these scripts,


Corentin

 

[Kevin Ledgister]

No idea at all, since I have never been able to connect even before the SPs.
If I could get to the point that you were, I would uninstall Entourage, then
re-install without the SPs. My company is just very difficult to work with,
and gives me no Mac support.


















I'm just dead in the water and very frustrated, so would be grateful if

I share your frustration as I've been trying to get the Exchange account
settings to work for 2 years. As a stop gap, I connect via IMAP in Entourage
which works to get your email, you should also be able to setup ldap for
your Global Address List, and accepting a meeting invitation will add it to
your Entourage calendar but will not update Exchange. And I do this through
a VPN from my remote office.

That being said, one thing that helped me was to put the DNS server in
System Preferences>Network>TCP/IP so I could resolve server names better.

If you're getting a root certificate error and you have a hostname mismatch,
that's what I'm trying to work through right now and haven't found a
solution yet.

If you don't have a hostname mismatch, then there is another issue. Some
authentication methods will not work with Entourage either so that is
another point to verify.