NOT CONNECTED - Can't believe its a bigger problem

M

Mark Geiser

OK here goes;

I have had this problem for some time and here is a description.

I can get entourage X working fine on any machine no problems at all.
However Entourage 2004 is a different story.

1. On a newly built machine the Entourage 2004 works OK (ie no
previous working installation of Entourage X to an exchange server).

2. Entourage 2004 will say "Not connected" next to the user name if I
upgrade from Entourage X, I can actually have x working but if I quit
x and start 2004 I still get the 'not connected' flag. If I remove the
password from the 2004 setup then it never asks for the password, so I
know that 2004 for some reason never requests a connection (Offiline
working is not enabled).

Then get this, this afternoon I took a new machine which I had working
(it was a new install) and I installed an airport card. I now get the
'not connected' flag. As soon as i switch back to ethernet all works
fine again. I therefore take another laptop on airport that I also
have upgraded but not working and tried that on ethernet but that does
not work either (my thinking here was that it was something to do with
our airport network) but as that has a working version of x installed
no matter what I do I cannot get it working.

I'm therefore totally stumped, all the machines are laptops with
airport, so thought that was the link, but then remembered a G5 on
ethernet that does not work either.

Bottom line is that for whatever reason Entourage 2004 does not or is
not able to request connection to the exchange server.

Has anybody got any ideas, it must be something to do with our setup
otherwise the whole entourage 2004 community would have the same
problems surely.

Mark Geiser
 
M

Martin

We have the same problem here on a station with OSX
10.2.8. It was working fine with Entourage X, but since
the upgrade, it doesn't seem to make any connection to
the server. I keep getting the Not Connected in my
folder view, to the right of the username. I only see
Public Folders under it, and if I click on it, it's
saying that it's retrieving data from server. We let it
process for the whole night, whithout any progress. I've
also found on the net (just do a search on google for
Entourage Not connected) and it seem that a lot of
peoples are experiencing the same problem. However, this
occur only when we do an upgrade from Entourage X to
Entourage 2004. A few "solutions" are posted, but none
of them seem to work (Start Entourage with ALT key to
rebuilt the DB, uninstall the previous version from the
CD tool, etc). Any other idea? Hope somebody at MS will
read this thread and we'll see a fix soon.
 
F

Fel

I am having the same problem with new installs of
Entourage 2004. 2 out of 6 machines display the "not
connected" message after a few minutes, although it does
retrieve the complete mailbox from the server. I have
tried reinstalling...no success.
 
M

Mark Geiser

This is still an issue, please microsoft can you investigate. Clearly
Entourage 2004 has some sort of connection issue that version X does
not.
 
R

Richard Kmieciak

Is OWA working? If you can verify OWA is working, Entourage should work as
well. Your Entourage server entry should look similar to the URL working for
OWA in your browser.

For example, if you have

http://owa.company.com/exchange/you/inbox/... in your browser,

Use owa.company.com/exchange in Entourage

If your OWA URL starts with "https:" make sure that SSL is enabled on the
advanced tab of your Exchange account.

If this doesn't help, please send screenshots of the working OWA URL and
your each tab in your Entourage Exchange account. Please use
entourage_testATfastmailDOTfm

Thanks,
Richard
 
M

Mark Geiser

Richard..

Thanks for the info. Yes OWA is working fine. The weird things is that
version x works fine, and so does 2004 if its a new install on a clean
machine. But if it has a working version of X then it will fail. Also
on a laptop that had it working on ethernet it will fail to work on
airport, and will only work again if I plug in the ethernet again.

For server name I use the IP address which works fine for all of X and
the working versions of 2004. The issue here is on a previos working
version and also if the machine has been configured on a particular
network port, seems to not work on another, but then this I have only
happen on one machine.

I have to say this whole sorry episode of a lack of a decent MAPI
client has seriously changed my mind against using macs in the
enterprise, we have about 100 + plus and I will be ordering PC laptops
from now on I think. I have used macs for about 10 years and I find it
increasingly harder to justify to myself the continued use of macs.

Mark
 
Top