D
Dale
I am in the process of setting up my first Outlook 2003
user on a traveling laptop. (Win XP Pro, all patches to
date) I have set up a zillion of these things in OL 2002
(XP), OL 2000, etc. but this is a new experience, and
proving to be a problem.
Prior to this, my traveling (laptop) OL clients had two
seperate profiles. One for "in the office" using an
Exchange 5.5 (SP4) server, (on a LAN) and a second,
seperate 'dial in" profile that was POP3 for on the road.
The reason for this was the terrible slowness of the phone
link using a common (LAN/dial up) shared Exchange profile.
We sacrificed the data being stored on the server to up
the speed of the connection. (storing data in a local .pst
instead of on the server) in this POP3 profile. This meant
two profiles that knew nothing of each other, and thus two
copies of every email. Ridiculous and dangerous, but fast.
When we moved to Office 2003, I vowed to try using one
profile again to both get Exchange 5.5 SP4 server email on
a LAN, and also use the same profile to dial into for all
of my users. (Cached Exchange mode and the like)
The Exchange 5.5 (LAN) portion of the profile sets up and
works well, per usual. It is the dial in portion that does
not work. There are many settings and config options
involved of course, but simply put, the dial in portion
errors out every time. To its credit, Outlook 2003 does
understand that because the LAN connection is not
available that it must dial, and dutifully pops up and
asks to do so. My server answers the dial in per normal,
and then hangs up with the message on the client; (in the
Send /receive dialog box)
" Task "Microsoft Exchange Server" reported error
(0x8004011D): "The server is not available. Contact your
admin if this condition persists."
Being familiar with Outlook and Exchange Server, I have
checked MANY things before posting here, all to no avail.
I am presently fearing an Outlook 2003 / Exchange Server
5.5 compatibility problem, which is my worst fear. Has
anyone experienced this?
Thanks for reading!
user on a traveling laptop. (Win XP Pro, all patches to
date) I have set up a zillion of these things in OL 2002
(XP), OL 2000, etc. but this is a new experience, and
proving to be a problem.
Prior to this, my traveling (laptop) OL clients had two
seperate profiles. One for "in the office" using an
Exchange 5.5 (SP4) server, (on a LAN) and a second,
seperate 'dial in" profile that was POP3 for on the road.
The reason for this was the terrible slowness of the phone
link using a common (LAN/dial up) shared Exchange profile.
We sacrificed the data being stored on the server to up
the speed of the connection. (storing data in a local .pst
instead of on the server) in this POP3 profile. This meant
two profiles that knew nothing of each other, and thus two
copies of every email. Ridiculous and dangerous, but fast.
When we moved to Office 2003, I vowed to try using one
profile again to both get Exchange 5.5 SP4 server email on
a LAN, and also use the same profile to dial into for all
of my users. (Cached Exchange mode and the like)
The Exchange 5.5 (LAN) portion of the profile sets up and
works well, per usual. It is the dial in portion that does
not work. There are many settings and config options
involved of course, but simply put, the dial in portion
errors out every time. To its credit, Outlook 2003 does
understand that because the LAN connection is not
available that it must dial, and dutifully pops up and
asks to do so. My server answers the dial in per normal,
and then hangs up with the message on the client; (in the
Send /receive dialog box)
" Task "Microsoft Exchange Server" reported error
(0x8004011D): "The server is not available. Contact your
admin if this condition persists."
Being familiar with Outlook and Exchange Server, I have
checked MANY things before posting here, all to no avail.
I am presently fearing an Outlook 2003 / Exchange Server
5.5 compatibility problem, which is my worst fear. Has
anyone experienced this?
Thanks for reading!