Re: Outlook 2003 on Tablet outside the domain
- From: "Ben Winzenz [Exchange MVP]" <ben_winzenz@nospamdotmessageonedotcom>
- Date: Tue, 27 Jun 2006 08:28:02 -0500
Heh - I'd rather you include too much information than too little!
I do like the OpenVPN solution. While it does take a little more technical
prowess on the client side (though if you as an admin can deploy the GUI
portion, it makes things a ton easier), I really like that it works as a VPN
over SSL instead of PPTP or L2TP. That feature alone makes it much more
flexible, and means that it will likely work even in places where L2TP and
PPTP might be blocked. Feel free to contact me off-list if you want more
information about it.
--
Ben Winzenz
Exchange MVP
MessageOne
Read my blog!
http://winzenz.blogspot.com
http://feeds.feedburner.com/winzenz (RSS Feed)
"Cary Shultz" <cwshultz@xxxxxxxx> wrote in message
news:OsqUGMRmGHA.508@xxxxxxxxxxxxxxxxxxxxxxx
Ben,
Schoene Gruesse aus Roanoke.
You gave me the answer. Send/Receive in Outlook. Must have missed this -
don't know how.....
I guess that I include too much information. As I stated in the original
post, we are going to get rid of the third-party hosting company. We will
change the MX record (which currently points to the third-party hosting
company). I will set up OWA for external use ( so that when he is not in
the office he will be able to check his e-mail via OWA). That is all he
really needs to do. OWA will be fine for him. You are right: Outlook
2003 is a much richer client than OWA. But all he really needs to do is
to read his e-mails and to reply to the e-mails. OWA on Exchange Server
2003 is sufficient for this. Most of the time that he is not in his
office he will be at the hospital (right across the street).
However, you bring up a really good solution with the VPN. I suggested
that to him but he was not interested. He is extremely cost-conscious.
Nothing wrong with that. However, I will look into OpenVPN. Thanks for
the tip. That might just be the way we end up going. This way Outlook
would be the client that he could always use - no matter where he is.
And, you are right about having two Outlook profiles. That would not be
an optimal solution.
Oh, and to clarify the "won't be an issue" statement. When the doctor is
not in his office he would simply not open Outlook for e-mail, he would
always use OWA. Thus, the pooling error ("Outlook could not find the
Exchange Server") would not happen. In that sense, it would not be an
issue anymore.
Thanks,
--
Cary W. Shultz
Roanoke, VA 24012
"Ben Winzenz [Exchange MVP]" <ben_winzenz@nospamdotmessageonedotcom> wrote
in message news:%23Nx2U$MmGHA.4864@xxxxxxxxxxxxxxxxxxxxxxx
I'm not sure I understand how it will no longer be an issue unless your
user won't need to check their hosted mail while out of the office. It
wouldn't make sense to remove the Exchange settings from Outlook, as
Outlook is a much richer client than OWA.
As far as your question about the Exchange polling interval, it's in the
Send/Receive Settings in Outlook. Regardless of what you do, though,
it's not a fix for the problem. It's just covering it up.
As I see it, there are really a few things you could do.
1) set up a VPN. If cost is an issue, check into using something like
OpenVPN (It's Free!). I've actually used this before, and it's a fairly
good solution. With your current infrastructure, this would be the
recommended solution.
2) rpc/https. As Mark indicated, and it appears you may know, this
requires Windows 2003 in addition to Exchange 2003.
3) Configure 2 Outlook profiles. This would be a sub-optimal solution,
as it wouldn't allow you to store hosted messages in their Exchange
mailbox, but if there is no other option available,
--
Ben Winzenz
Exchange MVP
MessageOne
Read my blog!
http://winzenz.blogspot.com
http://feeds.feedburner.com/winzenz (RSS Feed)
"Cary Shultz" <cwshultz@xxxxxxxx> wrote in message
news:eXR9%23EMmGHA.4064@xxxxxxxxxxxxxxxxxxxxxxx
Mark,
Thank you for the reply. Sorry for the lack of needed info.
I have not set up OWA yet (read: configure Firewall and change MX
Record). They still have the third-party hosting their e-mail and the MX
record still points to that third-party hosing company.
My question concerns Outlook 2003. I must be missing a check box or
something that controls how often Outlook pools for e-mail messages. I
assume this to be the case because when he is no longer in his office
(read: at the hospital) and he turns his tablet on Outlook errors out -
stating that it can not find the Exchange Server. All I am asking about
is where do I change the time frame where Outlook 2003 pools for e-mail
messages. These errors are becoming a nuisance to the good doctor.
Ultimately we will be setting up OWA (making use of https://) and this
will no longer be an issue.
Thank you,
--
Cary W. Shultz
Roanoke, VA 24012
"Mark Arnold [MVP]" <mark@xxxxxxxx> wrote in message
news:m2ot92p1r5lgsjtacndnrh169pt67facdi@xxxxxxxxxx
On Sun, 25 Jun 2006 09:47:09 -0400, "Cary Shultz" <cwshultz@xxxxxxxx>
wrote:
Good morning, All!
I have a simple question. Here are the domain environment details:
Windows 2000 Server SP4 on which Exchange Server 2003 SP2 is installed
(I
inherited this environment!).
Windows 2000 Pro SP4/Windows XP Pro SP2 on which Outlook 2003 SP2 is
installed. User in question has a Tablet PC running Windows XP Pro SP2
that
he will take quite often outside the network.
This environment has a third party company hosting their e-mail (yes, I
know....why do they have both this and Exchange?) as well as their
internal
Exchange Server (the company that we bought set this up in just about
every
location....I do not know what their thought process was...). So, when
I
configure their Outlook 2003 client I first create the Exchange
'profile'
(mail goes to their Exchange mailbox) and then their third-party hosing
company 'profile' (which is, naturally, a POP set up and goes to their
Exchange mailbox).
The problem that this user is having is that when he is outside the
office
his Outlook client is attempting to connect to the Exchange Server and
fails. It does this quite often. How do I prevent this from
happening?
Now, in the near future we are going to be setting up OWA (obviously
already
set up internally, I mean that we are going to do what is necessary for
it
to be available outside the office) and getting rid of the third-party
hosting company. But, until that point how do I prevent the Outlook
2003
client from looking for the Exchange Server? This is very frustrating
to
him.
Since it is Exchange Server 2003 RPC over HTTPS might have been an
option -
however, it is running on Windows 2000 (so, unfortunately, it is not).
Thanks,
You make no mention of a VPN or a dial-in connection so unless you
need to clarify the question, the reason it doesn't work outside the
network is that the firewall is (rightly) closed to the traffic that
allows Outlook to work.
So, unless you go to Exchange 2003 on Windows Server 2003 or go to
Outlook Web access you're a little stuck. Setting up OWA is a 5 minute
job really though. If you need help on making it happen you can have a
think about what you have and then post a question on anything you're
unsure of.
.
- Follow-Ups:
- Re: Outlook 2003 on Tablet outside the domain
- From: Cary Shultz
- Re: Outlook 2003 on Tablet outside the domain
- References:
- Outlook 2003 on Tablet outside the domain
- From: Cary Shultz
- Re: Outlook 2003 on Tablet outside the domain
- From: Mark Arnold [MVP]
- Re: Outlook 2003 on Tablet outside the domain
- From: Cary Shultz
- Re: Outlook 2003 on Tablet outside the domain
- From: Ben Winzenz [Exchange MVP]
- Re: Outlook 2003 on Tablet outside the domain
- From: Cary Shultz
- Outlook 2003 on Tablet outside the domain
- Prev by Date: Re: SMTP Referrals - Is there such a thing?
- Next by Date: Re: SMTP queue problem.
- Previous by thread: Re: Outlook 2003 on Tablet outside the domain
- Next by thread: Re: Outlook 2003 on Tablet outside the domain
- Index(es):
Relevant Pages
|