Re: NOT CONNECTED - Can't believe its a bigger problem
From: Richard Kmieciak (richk_at_aidan.net)
Date: 08/10/04
- Next message: BB: "Re: AppleScripts"
- Previous message: Anoop: "Re: Entourage 2004 Delegates not connected"
- Maybe in reply to: Mark Geiser: "Re: NOT CONNECTED - Can't believe its a bigger problem"
- Next in thread: SWeinberg: "Re: NOT CONNECTED - Can't believe its a bigger problem"
- Reply: SWeinberg: "Re: NOT CONNECTED - Can't believe its a bigger problem"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 10 Aug 2004 10:28:40 -0700
Hi Mark - When you connect to airport, are you switching from an internal
LAN connection to another network perhaps on the other side of a
firewall/proxy? Are you connecting to an Exchange back-end server? If so,
this might be expected behavior (well sort of...The Entourage-X-working part
casts doubt on my theory admittedly). For example, if I'm connected to my
LAN, I have access to my back-end Exchange server, but if I were to grab an
IP on the other side of our firewall/proxy via airport, I would no longer be
able to sync with Exchange. If you do have a front-end server on your
network, one potential workaround is to use its address in your entourage
account.
There might be some voodoo with Entourage X's app-level proxy settings
that's allowing it to work. If so, hopefully there's a matching change you
could make with the OS-level proxy settings that Entourage 2004 uses.
If none of this helps or applies, I'm curious what the traces of Entourage
2k4 success and failure (over airport) show. If you are want keep at this,
I'd be willing to take a look at the traces. Please send to
entourage_testATfastmaiDOTfm . FYI - you'll need to change tcpflow's network
interface when tracing airport vs. ethernet. In my case, ethernet is en0 and
airport is en1.
http://www.entourage.mvps.org/troubleshoot/tcpflow.html
On 8/10/04 8:06 AM, "Mark Geiser" <markg@dynamo.net.uk> wrote:
> 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
- Next message: BB: "Re: AppleScripts"
- Previous message: Anoop: "Re: Entourage 2004 Delegates not connected"
- Maybe in reply to: Mark Geiser: "Re: NOT CONNECTED - Can't believe its a bigger problem"
- Next in thread: SWeinberg: "Re: NOT CONNECTED - Can't believe its a bigger problem"
- Reply: SWeinberg: "Re: NOT CONNECTED - Can't believe its a bigger problem"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|