Re: Domain\Username Outlook Client



In news:672578AD-3835-4842-ADF0-05CB4796AE4A@xxxxxxxxxxxxx,
Moydog <Moydog@xxxxxxxxxxxxxxxxxxxxxxxxx> typed:
> Yes, they do logon to the same domain on these machines, however, we
> want them to be prompted to choose an e-mail profile and logon to
> e-mail for security reasons.

Then they should probably each have their own domain account and log in
using it.

> Many of these workstations are
> "multi-user" workstations, where generally, one user or generic user
> tends to logon for the day or shift,

Do they have to do this for some reason, or do they just "tend to" do this?

> and others use the Outlook mail
> client with their own profiles on the machine. These machines reside
> in areas such as nursing stations, emergency room desk, exam rooms in
> a hospital. We have tried to use the OWA, but users tend to hate it,
> as it lacks good functionality in addressing, and public folder
> usage.

Yes, but try www.messageware.net for some OWA addins that make addressing,
etc., more like Outlook.

> I'm thinking along the lines that it may be a pass-through
> authentication type issue between XP and server 2003, as we don't
> have this issue on W2K machine-Server 2k3, or XP to server 2000. Some
> sort of setting we missed on the exch 2003 server???

Can't say - this is a client-side issue. I wouldn't pursue it if it were me;
I'd either have them use their own logins or use OWA. An admin nightmare
otherwise.
>
> Thanx!
>
>
> "Lanwench [MVP - Exchange]" wrote:
>
>>
>>
>> In news:95C5F4CD-7A1A-40F2-A9EA-D9CBDBB47CF7@xxxxxxxxxxxxx,
>> Moydog <Moydog@xxxxxxxxxxxxxxxxxxxxxxxxx> typed:
>>> We have recently moved to Exchange Server 2003, it is not a domain
>>> controller, and any e-mail boxes that reside on it forces the user
>>> to type in their domain\username in Outlook 2003. Does not have the
>>> domain field anymore in the Outlook 2003 client. Very much like the
>>> many-many articles I have read about how OWA does this, and how you
>>> must type domain\username. This is happening on the regular Outlook
>>> 2003 client. Any clues to what I missed? Scenario - Exchange server
>>> 2003, Outlook 2003 client, XP Pro sp2.
>>>
>>> Please assist if you can!
>>> Thanx! Todd
>>
>> Do the users log into the domain on these workstations? They really
>> shouldn't be prompted at all to provide credentials, if so.


.

Relevant Pages

  • unknown user name / dropping authentication
    ... The only way to reconnect to the server is logoff/logon or reboot. ... Profiles) something called User Unknown as a profile on all the machines, ... Logon Failure: ... Caller User Name: - ...
    (microsoft.public.windows.server.sbs)
  • Re: Slow AD logon from remote offices .......
    ... So if you get long logon times once, then it runs a lot faster the next ... You may want to capture network traffic ... rudimentary checks would be to ping the Ca server and see what the ... I would verify that both the US side machines and the UK ...
    (microsoft.public.windows.server.active_directory)
  • Re: sharing Outlook Express on network with 98 + XP
    ... Outlook Express is not designed to do that... ... If you simply want to share a single email account setup each machine to leave mail on the server. ... account between two XP Pro machines. ...
    (microsoft.public.windowsxp.network_web)
  • Re: NT machines with Outlook 2000
    ... My DNS is correct; that was the first thing I checked. ... If your machines are trying to ... Server doesn't ... >> This only affects my NT machines with Outlook 2000 since upgrading from ...
    (microsoft.public.exchange.connectivity)
  • RE: NT machines with Outlook 2000
    ... resolve their DNS remotely first this can cause delay's and unpredictable ... Server doesn't seem ... > This only affects my NT machines with Outlook 2000 since upgrading from NT ...
    (microsoft.public.exchange.connectivity)
Loading