Exchange Server - Internet access to Exchange server for Outlook

Asked By ToddAndMargo
29-Jan-10 03:00 PM
Hi All,

I just picked up responsibility for a sbs 2003 server running
Exchange.

Now on one issue, I am completely puzzled.  On a number of
laptops, the customer has Outlook installed and working
with the exchange server.  They all work perfectly inside
the local network.

Here is what is puzzling.  One of the laptops Outlook works
outside the network (over the Internet).  And it
is not Terminal Services.  When this laptop is
inside the LAN, Outlook just pops right into Outlook.
When this laptop is outside the LAN (from the Internet),
He gets a username and password prompt to log in.  Then
he is attached to the Exchange server as if he was on the
LAN.

The rest of the laptops will not connect over the Internet.
The customer wants me to configure them all for
Internet access to Exchange.

I have looked at the Outlook configure pages and they
are all identical.  For the server, they all reference the
internal LAN (acme.local) domain name, not the Internet
domain name.

What in the world?  My brain hurts!

Many thanks,
-T
Outlook
(1)
VPN
(1)
Acme.local
(1)
Thetip
(1)
Pops
(1)
RPC
(1)
Sbs
(1)
  Mark Arnold [MVP] replied to ToddAndMargo
29-Jan-10 03:09 PM
Sounds like one of the laptops is configured for "RPC over HTTPS"
Google up on that, check out the laptop that will work and then
implement that across the board if you need.
  ToddAndMargo replied to Mark Arnold [MVP]
29-Jan-10 03:33 PM
Thank you!
  Phil Angus replied to ToddAndMargo
01-Feb-10 06:21 AM
Are you sure this is a live connection, and not just using cache mode? Does
he receive an email OK and is able to send a new one (and it is received). I
always thought you had to use OWA if outside, unless you are making a VPN
connection.
  ToddAndMargo replied to Phil Angus
01-Feb-10 02:03 PM
Hi Phil,

No VPN or Terminal Services.  He receives everything live.

-T
  ToddAndMargo replied to ToddAndMargo
02-Feb-10 11:37 AM
That was it.  The "Outlook Anywhere" should have been the
tip off.  I totally missed it.  Thank you again.  -T
Create New Account
help
of the office Exchange Server Hi, Our users can send / receive mail in office using Outlook / Outlook express. After going out / home, they can't send the mail, just can receive. Someone told me that Exchange 2007 not allow users using Outlook / Outlook Express to send mail while users is not internal user. Is it correct? We have well, there is no problem, just happen in exchange 2007. Thank You Exchange Admin Discussions Outlook 2007 (1) Outlook (1) Office (1) SMTP (1) Cordialement (1) Outlook2003 (1) Autoconfigure (1) Configue (1) Hello, Are you using MAPI connection to exchange (Microsoft Office Outlook only, not express) or pop / smtp or imap4 / smtp ? If you are using the SMTP configuration ? - - Cordialement, Mathieu CHATEAU http: / / lordoftheping.blogspot.com Hi, We want to use IMAP with Outlook / Outlook Express, at least one application with use IMAP. Let me explain more detail to
Outlook doesn't work on VPN Exchange Server I have a few users using new Dell Latitude laptops running XP SP2 and Outlook 2003 that when they are on VPN Outlook cannot connect to the Exchange server. They can access all other company resources i.e sharepoint, remote desktops, etc. The users with IBM laptops sitting in the same room on VPN can access Outlook / Exchange just fine. The only difference between the configs on the laptops are the Intel s and the Broadcom NICS in the Dell's. We are using a Nortel Contivity VPN concentrator. Is anyone else experiencing this? Any workarounds? thanks Exchange Clients Discussions Outlook 2003 (1
Outlook 2003 through VPN connection Exchange Server A user of my company has some problems using Outlook 2003 through VPN connection. She connects through VPN, opens Outlook 2003 and starts working with Outlook without any evident issue. After some time, Outlook prompts for user credentials (User name / Password). The user name field is already filled with
to deploy Exchange 2007 in our environment. Our AD infrastructure is as follows: Single forest (acme.local) Multiple child domains (child1.acme.local, child2.acme.local, child3.acme.local, child4.acme.local, child5.acme.local, child6.acme.local) Each child domain resides in a