Accessing the GAL using Internet E-Mail Service
Brint Hite
In my organization, we have about ten users outside our LAN who dial into
the network via a 3Com RAS 1500. I have set up the Outlook 2000 clients to
access their mailboxes on our Exchange 5.5 SP3 server using the Internet
E-Mail Service instead of the Exchange Server service for performance
reasons. Everything works fine but I have one problem: those remote users
need to access the Global Address List so they can easily send messages to
others in our organization without having to type the actual e-mail address
of each recipient of their message. Is there any way to do this?
Thanks,
Brint Hite
Kirill S. Palagin
Take a look at
www.slipstick.com
Brint Hite wrote:
--
If you feel that anything in my post needs correction - feel free to do so (in
group).
And please, keep all discussions in NG, so that everybody can participate.
Kirill
bud_miller
Have you considered setting up OWA - it may be a better solution . . .
"Brint Hite" <bh...@gordoncounty.org> wrote in message
news:OYNaQrxIAHA.196@cppssbbsa04...
Brint Hite
I haven't had much luck using OWA. In fact, I have tried to set up a login
on our website for users to access their mailboxes from outside the offices.
However, when attempting to access ./exchange, the user is presented with a
login box that doesn't accept any username or password. It's something I
haven't played with that much.
"bud_miller" <bud_m...@yahoo.com> wrote in message
news:u$CeRryI...@cppssbbsa02.microsoft.com...
Kirill S. Palagin
Any help from
http://support.microsoft.com/support/exchange/content/whitepapers/owa_tshoot.asp
Brint Hite wrote:
--
Ray Schlosbon
OWA rocks man. Especially in Exchange 2000!!!
"Brint Hite" <bh...@gordoncounty.org> wrote in message
news:ehIRn$yIAHA.277@cppssbbsa04...
msnews.microsoft.com
msnews.microsoft.com
their Exchange *ALIAS*, then you have use an extended login string. Here's
the info I have put on my Intranet about this:
+++++++++++++++++++++++++
You will likely need to use the explicit login format of
<NTDOMAIN>\<yourNTlogin>\<your_exchange_alias>. Yes, that is a convoluted
mess - you can thank Microsoft for making this all so easy. :) Here's how it
breaks down:
The first part, the <NTDOMAIN> is the name of the NT domain. The San
Francisco office is presently the "LVI_MV" domain. The second part,
<yourNTlogin> is your account in the NT domain you'll be accessing (for
example, the LVI_MV domain in San Francisco office). You were assigned this
login when you joined LVI. The third part is the most obscure. Your "alias"
is the shortcut name your e-mail account was assigned to make it easier for
our staff to address e-mail messages to you. For example, I have the alias
'Bear.' Paul S. Kegelmeyer has the alias 'keg.'
EXAMPLE: For John Smith, who has the NT domain account login of jsmith and
the alias "john" in the LVI_MV domain, his Outlook Express login would be
lvi_mv\jsmith\john
HINT: To confirm your alias, have a coworker look up your Exchange Directory
(LDAP or Outlook Address Book) entry on the Exchange Server. Have them go to
Tools --> Address Book, open your entry and look in the "alias" filed of the
"Name" section of your record.
++++++++++++++++++++++
Hope that helps
"Brint Hite" <bh...@gordoncounty.org> wrote in message
news:ehIRn$yIAHA.277@cppssbbsa04...
> I haven't had much luck using OWA. In fact, I have tried to set up a
login
> on our website for users to access their mailboxes from outside the
offices.
> However, when attempting to access ./exchange, the user is presented with
a
> login box that doesn't accept any username or password. It's something I
> haven't played with that much.
>
> "bud_miller" <bud_m...@yahoo.com> wrote in message
> news:u$CeRryI...@cppssbbsa02.microsoft.com...
> > Have you considered setting up OWA - it may be a better solution . . .
> >
> >