Entourage error 23016 with Exchange Server 2003

[Linder]

After over a year of running flawlessly, my office Entourage email has
suddenly packed up. It cannot send or receive any messages from my
corporate email account, and always gives me error message -23016.

I consulted the Entourage Errors page mentioned in this group, but none
of the fixes are applicable. I called our IT department and no changes
were made to our server app (Microsoft Exchange Server 2003) recently,
so I am assuming that isn't the problem.

Any idea where to begin trouble-shooting? Is it possible I have a
corrupted account identity? I am using Entourage X for Mac, version
10.1.6 on an iMac G4 (the model that looks like a table lamp) running
OS X version 10.3.8.

TIA,

Linder

 

[Corentin Cras-Méneur]

Hi,

After over a year of running flawlessly, my office Entourage email has
suddenly packed up. It cannot send or receive any messages from my
corporate email account, and always gives me error message -23016.

I consulted the Entourage Errors page mentioned in this group, but none
of the fixes are applicable. I called our IT department and no changes
were made to our server app (Microsoft Exchange Server 2003) recently,
so I am assuming that isn't the problem.

Any idea where to begin trouble-shooting? Is it possible I have a
corrupted account identity? I am using Entourage X for Mac, version
10.1.6 on an iMac G4 (the model that looks like a table lamp) running
OS X version 10.3.8.

You can try a couple of things:
First you can disable calendar and address book synching to see if the
warning goes away (that would allow you to restrict the search somehow).

Then you can use a port sniffing application (like tcpflow, tcpdump,
etc) to monitor traffic and try and find out where Entrouage chokes.
Personnally I do that from Interarchy.
In Entourage X, mail traffic goes through IMAP and calndar and address
book sync through WebMail (port 80 or 443 - depending on whether or not
you use https).

Corentin

 

[Linder]

Thanks very much for the suggestions. Although disabling the
synchronization has fixed the problem before with the Mac next door
(the designer in the next cube), it didn't solve my problem.

Although I tried to run a port sniffing app to detect the choke, it
seems that our IT folk have done something to block employees from this
sort of thing, as I'm not getting the type of results that the
instructions describe. However I am not an expert on this sort of
thing; I'm a liberal arts major - my failure to find anything via
sniffer may very well be my lack of expertise.

Since I can't sniff properly, I can't think of anything else I can do
except to re-install. Any other suggestions?

 

[Corentin Cras-Méneur]

Although I tried to run a port sniffing app to detect the choke, it
seems that our IT folk have done something to block employees from this
sort of thing, as I'm not getting the type of results that the
instructions describe. However I am not an expert on this sort of
thing; I'm a liberal arts major - my failure to find anything via
sniffer may very well be my lack of expertise.

Since I can't sniff properly, I can't think of anything else I can do
except to re-install. Any other suggestions?

Nahhhh, if you have admin privileges on the Mac, you can prot-sniff. The
software only analyzes the traffic on the Mac. There is nothing they
could do (or should do for that matter since I don't see what the
problem would be) to prevent it.
That's quite different from "packet-sniffing" on the network (looking at
what other computers send over the network), which is assimilated to
spying. All you are doing here is looking at incoming and outgoing
traffic on your own computer.



You'l find info on port sniffing here:
http://www.entourage.mvps.org/troubleshoot/sniff.html

You'll find info on how to use tcpflow (free) here:
http://www.entourage.mvps.org/troubleshoot/tcpflow.html

If you have Interarchy, give it a try for port-sniffing. It's far easier
than any command-line application.


Corentin

 

[Linder]

Man, this is weird. Came to work this morning, turned on Entourage to
read an email from last week - and it's working again. Called IT and
they all swore that they didn't change any settings.

This is after I spent a couple of hours over the weekend reading up on
port sniffing...

 

[Corentin Cras-Méneur]

Man, this is weird. Came to work this morning, turned on Entourage to
read an email from last week - and it's working again. Called IT and
they all swore that they didn't change any settings.

This is after I spent a couple of hours over the weekend reading up on
port sniffing...

For some reason that makes NO sense to me whatsoever, other people have
also reported that after performing some port sniffing, their access to
their Exchange server started working again for no apparent reason... I
don't get it, but I'm glad ou got the access back

Corentin