Windows XP Machines Always Prompt for Credentials (Exchange 2013, Outlook 2010)

I am running Exchange 2013 on Server 2012 Datacenter (VM). Windows 7 clients with Outlook 2010 work fine. Windows XP clients with Outlook 2010 prompt for credentials (user name and password) each time Outlook is started, and checking the "Remember
my password" box does not prevent this from happening the next time. The "Always prompt for logon credentials" checkbox on the "Security" tab of the "More Settings" section of the Exchange account is not checked. I have found a myriad of posts
with similar issues, but they all seem to have to do with SBS/Exchange 2007, and I haven't come across something that works as a solution for me. One suggested certificate issues, and I was having certificate security warnings, but I got that resolved.
I am hopefuly that the fact that this only happens on Windows XP will be telling.

Proxy settings:
auth_param ntlm program /usr/bin/ntlm_auth --helper-protocol=squid-2.5-ntlmssp
auth_param ntlm children 50
auth_param ntlm keep_alive on
auth_param basic program /usr/lib/squid3/squid_ldap_auth -R \
-b "DC=domain,DC=local" \
-D "CN=Squid Proxy,OU=TI,OU=Domain,DC=domain,DC=local" \
-W passldap \
-f "sAMAccountName=%s" \
-h domain.local
auth_param basic children 20
auth_param basic realm Domain Internet Proxy
auth_param basic credentialsttl 8 hours
external_acl_type ADS children=50 ipv4 ttl=60 %LOGIN /usr/lib/squid3/squid_ldap_group -S -K -b "DC=domain,DC=local" -f "(&(objectclass=person)(sAMAccountName=%v)(memberof =CN=%a,OU=Domain,DC=domain,DC=local))" -D "CN=Squid Proxy,OU=TI,OU=Domain,DC=domain,DC=local" -s sub -W ldappass domain.local
tks.

Similar Messages

Exchange 2013 - Outlook 2010 - 550 5.1.0 RESOLVER.ADR.InvalidInSmtp; encapsulated INVALID address inside an SMTP address

Hello,
I have issue when sending email to some addresses. Server respond with:
Remote Server returned '550 5.1.0 RESOLVER.ADR.InvalidInSmtp; encapsulated INVALID address inside an SMTP address (IMCEAINVALID-)'
My enviroment: Exchange 2013, Outlook 2010 - no cached mode. Issue happend with two email addresses but not always.
Any suggestion, how to resolve issue?
Thx.

Hi Tomas,
Does this issue occur in OWA? How is the impact, only one user or all users?
Please try to run Outlook under safe mode to avoid add-ins and AVs.
If there is any 3rd party add-ins, please try to disable them for testing.
Thanks
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Mavis Huang
TechNet Community Support

Outlook 2013 Constantly Prompting For Credentials - Exchange 2007 - Small Business Server 2008

Hello, I am having a problem using Windows Small Business Server 2008 and Exchange 2007 with Outlook 2013. The issue is that a credentials box appears in Outlook 2013 when using there exchange account whilst connected to the domain. The box will randomly
prompt for user credentials, once the user credentials are entered it will either pop back up again and if you enter the details in again it will continue to pop up for around 4 or 5 times before accepting the credentials. It will then pop back up within 15
minutes and do the same thing, if you click "Cancel" on the box it will also go away and remain connected to exchange however a popup in the bottom right will appear asking for a password even though you can send / receive from the mailbox.
I have looked into this issue for hours and hours and still can not find a resolution, I have tried re-installing Office 2013 and re-creating the Outlook Profile as-well as as the Windows 7 Profile. I have checked through all the SSL certificates in IIS
and everything appear to be correct.
Is this a common issue? Is there anything I can do to further diagnose or fix this issue without having to try to re-install both the server and machine?

Hi James_wilson,
Any update?
Just additional, would you please let me know whether have installed all updates for Outlook 2013? If hasn’t, please install and then monitor the result.
Please also check if you enable
Always prompt for logon credentials setting in Outlook 2013.
If you enable this setting, please uncheck and check if this issue still persists. Meanwhile, please remove the old credential in
Credential Manager, then add again. Then monitor the result
By the way, please run the Exchange BPA on the SBS 2008 server and check if can find some issue.
Hope this helps.
Best regards,
Justin Gu

Getting Prompt for Credentials When Opening InfoPath 2010 Form in Sharepoint 2010

I have a domain user who runs Office 2010 x32 and uses a Sharepoint 2010 site daily. Lately a specific page on that site has been randomly giving prompts for credentials when opening existing documents and creating new ones. The process can be most easily
replicated by opening the new document template in Infopath by going to Documents -> New in the ribbon bar of the SP page. Most of the time the Windows credentials for the user are passed to Infopath/Sharepoint automatically (which is normal), but on the
fourth or fifth attempt to create a new form, the prompt appears. The user can still enter the credentials and open the blank template form, but a prompt should not appear. The user is also the administrator for that page, so I'm thinking it's not a permissions
issue.
The user is running IE 9 on Windows 7 Pro x64. I have performed the following:
Reset advanced IE settings and all user cache data
Cleared cached Sharepoint credentials in Windows credential manager
Re-applied group policy for the machine using gpupdate /force
Logged in with a clean temporary profile
Logged in to another domain account using the user's Sharepoint credentials
Cleared Infopath cache
Re-installed Office 2010 x32
The problem only occurs only on this particular machine. There are no Sharepoint or authentication-related errors or warnings in the application and system event logs. There are also no error messages on-screen when the prompt appears. I also considered
the possibility of this being a performance related issue in the case that maybe Infopath was taking too long to start, causing the credential pass-through process to time out and fall back to a prompt. I ran disk cleanup, deleted some temporary files, and
checked for excessive CPU/memory load. I didn't find any issues and doing these things did not help.
I'm convinced there is another setting somewhere in Windows that is causing this. Interestingly it always happens after four or five attempts, never the first time. Can someone point me in the right direction?

Hi Titan, this sounds like an IE security setting issue. Things to do:
1. In Internet options>Security>Local Intranet, make sure "Enable Protected Mode" is not selected.
2. Under Sites>Advanced, add https://*.sharepoint.com (and make sure "Require server verification..." is not checked).
3. Under Security>Custom Level, scroll all the way to the bottom and make sure "Automatic logon with current user..." is checked.
cameron rautmann

Outlook suddenly prompts for password / Exchange 2013

I just checked the internal DNS and the autodiscover record did not exist so I created it. The old server records were removed.I don't know if adding the record to internal DNS will solve the problem because all the clients are external.I also forgot to mention one more thing that I don't think its causing any problems but I have an additional accepted domain, so mydomain.org as the main one and mydomain.com as accepted too.So for autodiscover on the second domain I'm using redirect from autodiscover.mydomain.com to autodiscover.mydomain.orgSo for my internal DNS I have:autodiscover.mydomain.org - internal ipmail.mydomain.org - internal ipand for the External DNS I have:autodiscover.mydomain.org - public ipmail.mydomain.org - public ipautodiscover.mydomain.com - public secondary ipI will check if after doing this change on the DNS...

Hello everyone,I've upgraded an Exchange 2010 to Exchange 2013 but problems started when the Exchange 2010 was removed from the co-existence.The desktop clients suddenly disconnect from the server and prompt for the user credentials, some times if the user provides the credentials right away it fails, but if the user waits about 1 minute, it accepts it. This is happening with outlook 2010, outlook 2013, outlook 2011 for mac and even the new outlook 2016 (provided with office 365) and for some users is more frequent than for others.ActiveSync and OWA works fine, so this is an Outlook Anywhere issue, I've checked all settings that I think could be the reason but no luck so far.Something that I noticed with the TestExchangeConnectivity is that when I do the Outlook Connectivity test if I use manual server settings it works and look like...
This topic first appeared in the Spiceworks Community

Exchange 2013 + Outlook 2010, Security Alert

A small customer has Outlook 2010 connecting to Exchange Server 2013 on a Windows 2008
R2 server at a remote site. Recently, the users began receiving a security
alert ("The identity of this web site or the integrity of this connection
cannot be verified", "The name on the security certificate is invalid
or does not match the name of the site"). This occurs every time a user
opens Outlook, and when they click on "Yes" they are able to use
Outlook normally. <o:p></o:p>
This problem began not long after 1) the wildcard ssl certificate was renewed and 2)
Exchange 2013 was updated to the most recent SP and CU. It is noteworthy that
the PCs being used are not members of the domain. The users also receive this
error if they use Outlook to connect from their home PCs. <o:p></o:p>
The Exchange server passes connectivity and autodiscover tests. I have checked all the URLs
in Exchange Server. I have tried changing authentication, re-enabling the the
*.domain.ca certificate, I have not been able to reproduce the error on my own
laptop from the customer's site. <o:p></o:p>
This problem is not critical, but it is annoying for the users, and I have tried
just about everything I can find on the Internet to resolve it. <o:p></o:p>
Any suggestions? <o:p></o:p>

Hi,
Please run the following command to set the CertPrincipalName parameter which specifies the Secure Sockets Layer (SSL) certificate principal name required for connecting to Exchange from an external location to have a try:
Set-OutlookProvider EXPR -CertPrincipalName msstd:*.domain.ca
If the issue persists, please follow the steps below to check Exchange services for the problematic users :
Open Outlook - press CTRL key - right click on the Outlook icon from right bottom corner taskbar -
Test Email AutoConfiguration. Put your email address - uncheck use guessmart and secure guessmart authentication - click Test to check your Autodiscover service.
Please collect the information in the Log tab and Results tab.
Regards,
Winnie Liang
TechNet Community Support

Exchange 2013 / Outlook 2010+ Attachment size limit

I have an issue with my Exchange 2013 deployment. I am unable to send attachments over 10MB. I know, I know not another one of those threads, but I promise I have searched for a solution to my issue as best I can before posting.
So in the EMC I have set the Send/Receive connectors to unlimited, I have set the organizational limits to unlimited, I have even set both the Internal and ExternalDsnMaxMessageAttachSize
to 2047MB.
I have restarted the the Exchange Transport service, failing that I restarted the Exchange Box. I have closed and opened my Outlook Client Several times but when ever
I select an attachment over 10MB I get the message "The Attachment size exceed the allowable limit"
There must be something I am missing but I can't see it. I did also check my (and other) user accounts to confirm that no limits had somehow been set, they are all unconfigured or
blank in the EMC which my research has told means there is no limit on the account.
Now I know in in non exchange environment there are limits on the client, but attached to an exchange server these limits are supposed to be driven by exchange.
Here is the output of Get-TransportConfig
AddressBookPolicyRoutingEnabled : False
AnonymousSenderToRecipientRatePerHour : 1800
ClearCategories : True
ConvertDisclaimerWrapperToEml : False
DSNConversionMode : UseExchangeDSNs
JournalArchivingEnabled : False
ExternalDelayDsnEnabled : True
ExternalDsnDefaultLanguage :
ExternalDsnLanguageDetectionEnabled : True
ExternalDsnMaxMessageAttachSize : 1.999 GB (2,146,435,072 bytes)
ExternalDsnReportingAuthority :
ExternalDsnSendHtml : True
ExternalPostmasterAddress :
GenerateCopyOfDSNFor : {}
HygieneSuite : Standard
InternalDelayDsnEnabled : True
InternalDsnDefaultLanguage :
InternalDsnLanguageDetectionEnabled : True
InternalDsnMaxMessageAttachSize : 1.999 GB (2,146,435,072 bytes)
InternalDsnReportingAuthority :
InternalDsnSendHtml : True
InternalSMTPServers : {}
JournalingReportNdrTo : <>
LegacyJournalingMigrationEnabled : False
LegacyArchiveJournalingEnabled : False
LegacyArchiveLiveJournalingEnabled : False
RedirectUnprovisionedUserMessagesForLegacyArchiveJournaling : False
RedirectDLMessagesForLegacyArchiveJournaling : False
MaxDumpsterSizePerDatabase : 18 MB (18,874,368 bytes)
MaxDumpsterTime : 7.00:00:00
MaxReceiveSize : Unlimited
MaxRecipientEnvelopeLimit : 500
MaxRetriesForLocalSiteShadow : 2
MaxRetriesForRemoteSiteShadow : 4
MaxSendSize : Unlimited
MigrationEnabled : False
OpenDomainRoutingEnabled : False
RejectMessageOnShadowFailure : False
Rfc2231EncodingEnabled : False
SafetyNetHoldTime : 2.00:00:00
ShadowHeartbeatFrequency : 00:02:00
ShadowMessageAutoDiscardInterval : 2.00:00:00
ShadowMessagePreferenceSetting : PreferRemote
ShadowRedundancyEnabled : True
ShadowResubmitTimeSpan : 03:00:00
SupervisionTags : {Reject, Allow}
TLSReceiveDomainSecureList : {}
TLSSendDomainSecureList : {}
VerifySecureSubmitEnabled : False
VoicemailJournalingEnabled : True
HeaderPromotionModeSetting : NoCreate
Xexch50Enabled : True
Thanks in advance for any assistance.
Carl

I have an issue with my Exchange 2013 deployment. I am unable to send attachments over 10MB. I know, I know not another one of those threads, but I promise I have searched for a solution to my issue as best I can before posting.
So in the EMC I have set the Send/Receive connectors to unlimited, I have set the organizational limits to unlimited, I have even set both the Internal and ExternalDsnMaxMessageAttachSize
to 2047MB.
I have restarted the the Exchange Transport service, failing that I restarted the Exchange Box. I have closed and opened my Outlook Client Several times but when ever
I select an attachment over 10MB I get the message "The Attachment size exceed the allowable limit"
There must be something I am missing but I can't see it. I did also check my (and other) user accounts to confirm that no limits had somehow been set, they are all unconfigured or
blank in the EMC which my research has told means there is no limit on the account.
Now I know in in non exchange environment there are limits on the client, but attached to an exchange server these limits are supposed to be driven by exchange.
Here is the output of Get-TransportConfig
AddressBookPolicyRoutingEnabled : False
AnonymousSenderToRecipientRatePerHour : 1800
ClearCategories : True
ConvertDisclaimerWrapperToEml : False
DSNConversionMode : UseExchangeDSNs
JournalArchivingEnabled : False
ExternalDelayDsnEnabled : True
ExternalDsnDefaultLanguage :
ExternalDsnLanguageDetectionEnabled : True
ExternalDsnMaxMessageAttachSize : 1.999 GB (2,146,435,072 bytes)
ExternalDsnReportingAuthority :
ExternalDsnSendHtml : True
ExternalPostmasterAddress :
GenerateCopyOfDSNFor : {}
HygieneSuite : Standard
InternalDelayDsnEnabled : True
InternalDsnDefaultLanguage :
InternalDsnLanguageDetectionEnabled : True
InternalDsnMaxMessageAttachSize : 1.999 GB (2,146,435,072 bytes)
InternalDsnReportingAuthority :
InternalDsnSendHtml : True
InternalSMTPServers : {}
JournalingReportNdrTo : <>
LegacyJournalingMigrationEnabled : False
LegacyArchiveJournalingEnabled : False
LegacyArchiveLiveJournalingEnabled : False
RedirectUnprovisionedUserMessagesForLegacyArchiveJournaling : False
RedirectDLMessagesForLegacyArchiveJournaling : False
MaxDumpsterSizePerDatabase : 18 MB (18,874,368 bytes)
MaxDumpsterTime : 7.00:00:00
MaxReceiveSize : Unlimited
MaxRecipientEnvelopeLimit : 500
MaxRetriesForLocalSiteShadow : 2
MaxRetriesForRemoteSiteShadow : 4
MaxSendSize : Unlimited
MigrationEnabled : False
OpenDomainRoutingEnabled : False
RejectMessageOnShadowFailure : False
Rfc2231EncodingEnabled : False
SafetyNetHoldTime : 2.00:00:00
ShadowHeartbeatFrequency : 00:02:00
ShadowMessageAutoDiscardInterval : 2.00:00:00
ShadowMessagePreferenceSetting : PreferRemote
ShadowRedundancyEnabled : True
ShadowResubmitTimeSpan : 03:00:00
SupervisionTags : {Reject, Allow}
TLSReceiveDomainSecureList : {}
TLSSendDomainSecureList : {}
VerifySecureSubmitEnabled : False
VoicemailJournalingEnabled : True
HeaderPromotionModeSetting : NoCreate
Xexch50Enabled : True
Thanks in advance for any assistance.
Carl
1. If you send a message larger than 10MB from an external client to your org, does it bounce back because its over the limit?
2. Do you see the same problem sending internally with OWA?
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Exchange 2010 - Exchange 2013 Outlook 2010 resolves wrong server

Hello,
We are upgrading from exchange 2010 to 2013.
Now I have migrated a testmailbox, but when I try to configure it in outlook it tries to connect to the Exchange 2010 server instead of the Exchange 2013 server.
I have configured outlook manually like described on the following url:
http://www.zerohoursleep.com/2013/02/manual-outlook-configuration-with-exchange-2013/
At the "Check Name" step, it will not resolve the Exchange 2013 server guid but the Exchange 2010 server... but the mailbox is migrated to Exchange 2013...
When I try to launch outlook an error occurs: Cannot open your default e-mail folders. You must connect to Microsoft Exchange with the current profile before you can synchronize your folders with your Outlook data
file (.ost)."
Can someone help me out please?
Thx!

Are you sure the mailbox move completed? What happens when you log into OWA? Are you having AD replication issues in your environment?
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread

Shared folders (Windows file shares) show access denied and do not prompt for credentials

Scenario:
Like other admins, I log on and work as a 'standard user' (usera) with no admin rights anywhere in the domain, to perform admin tasks I have another account (userb) which I authenticate with as and when required. userb has been allocated/delegated permissions
as required.
Problem:
When trying to connect to shared folders on servers (2008 R2) using a UNC patch via Windows Explorer (Win 7 Ent.), I see an access denied error and do not get an option to supply alternative credentials.
If I try to connect to the admin shares on the same server (\\server\C$ or \\server\e$) I get an access denied message AND get prompted for credentials. I supply my admin account and gain access as expected.
If I check share and storage management when attempting to connect, I see that Windows is trying to connect me to each share as usera (which has no access). I understand why I get access denied at this point, but not why it can't just prompt me to supply an
account that does have access. When trying the admin shares I also see the usera account, but I get a prompt to supply a user who does have access.
Share permissions on the folders are for example 'Everyone' Full Control. NTFS permissions are 'userb' has modify (read, execute, list, traverse etc) via a 'Server Admins' AD Universal security group.
Note: If I do a NET USE from CMD and use the /USER switch, I can access the shares fine. But this is not great for accessing shared folders on the fly from various computers.
How can I get the other shares on the server to prompt me, rather than just say access denied?
Many thanks.

Try to disable guest user from the server
If you found this post helpful, please give it a "Helpful" vote. If it answered your question, remember to mark it as an "Answer". This posting is provided "AS IS" with no warranties and confers no rights! Always test ANY
suggestion in a test environment before implementing!

Exchange 2013/2010 Co-existance Outlook Users Always Prompted for Password

Hello,
We are in the process of attempting to migrate to Exchange 2013, but during the migration time, we need to coexist with the two versions. Our outlook clients are a mix of Office 2007, 2010, and 2013. When a user is migrated from 2010 to 2013,
they start getting prompted for their password in Outlook every few minutes. They can click cancel and continue working, but they continue to get prompts for their password. If they click the update folder button in outlook, it updates fine, and
the password prompt goes away for awhile.
Most topics on this state that this is caused by a certificate issue. We have an internally deployed CA, with the Root certificate trusted by all clients. The exchange 2013 server has a certificate that was created by this CA.
I believe that this is caused by OAB (address book) still being hosted on the Exchange 2010 server (with a self signed cert), that is causing the connection to fail. Is there anyway to test this without breaking outlook connections for the users that
are on Exchange 2010? Or is there any other reason that this would occur?
Thanks for any assistance.

Sorry for taking so long to reply, other items came up that rank higher then this migration.
I ran the Test-OutlookWebServices CMD and got this result:
[PS] C:\Windows\system32> Test-OutlookWebServices
Source                              ServiceEndpoint
Scenario                       Result Latency
(MS)
EXCHANGE13.company.local           exchange10.company.local           Autodiscover: Outlook Provider Failure     229
EXCHANGE13.company.local
Exchange Web Services          Skipped       0
EXCHANGE13.company.local
Availability Service           Skipped       0
EXCHANGE13.company.local
Offline Address Book           Skipped       0
I
am currently thinking that this may be the error. Is there a way to
change the first failing result to the hostname of the
exchange13.company.local without breaking the current settings for the
exchange10.company.local autodiscover?

Outlook 2013 continually prompting for credentials on new domain

Greetings,
I first posted this in the Office365 community forums and was directed here.
We are experiencing an issue where Outlook 2013 (Office365 install) is prompting for user credentials every time it is opened, despite checking the option to remember the credentials. So far we've tried a number of troubleshooting steps, but nothing
has resolved the issue. The issue is happening to multiple users on multiple computers.
We are running:
Outlook 2013 (32-bit) (Office 365 install)
Windows 7.1 Professional (x64)
Computer is domain joined (Server 2012 R2 Domain Controllers)
Mail is hosted on Office 365
We've tried:
Clearing the Outlook and Office credentials from Credential Manager.
Removing the mail profile and the saved credentials from Credential Manager, then re-adding the mail profile.
We've tried adding the mail profile with both a manual configuration of the server settings and allowing Outlook to automatically configure them.
Ensuring that "Always prompt for logon credentials" is unchecked.
Setting "Always prompt for logon credentials" to disabled via registry (see
http://support.microsoft.com/kb/2984912)
Confirming that Autodiscover is able to connect (http://www.microsoft.com/en-us/showcase/details.aspx?uuid=e8db028a-06f4-45fb-aff1-e8ac896d29c5)
Deleting the Autodiscover.xml file so that it is recreated
Doing an Online Repair of Office 365.
Reinstalling Office 365
Recreating the user's Windows profile.
Ensuring all applicable Windows updates and Office updates are installed.
Changing Proxy Authentication from Basic to NTLM (will not connect with NTLM)
The machines this is occurring on are on a new domain that we are in the process of setting up. The user accounts are still on the old domain. Cross-domain trusts are set up in both directions and all other services are working fine. GPO settings across
both domains have been set up to be identical. The issue occurs on computers that were built directly on the new domain as well as computers built on old domain and migrated over. Machines that are not domain joined or are still on the old domain are not experiencing
the issue.
If any of you could provide any insight or other steps that we could try I'd greatly appreciate it.
Thanks

Hi,
For the issue that Outlook keeps prompting for password, I usually suggest users follow the steps in this article below, but apparently you have tried almost all the steps:
Why does Outlook keep prompting for password
I've seen some similar issues that were caused by an old "network driver", which for some reason caused a wrong server name to propagate up from the network layer to the application layer. Updating the network driver would fix the issue, I'm
not sure if this works in your scenario though.
Regards,
Melon Chen
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs. Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Outlook 2013 on Windows 8.1 keeps prompting for username and password.

Hi,
I have a HP Pavillion TouchSmart laptop with MS Windows 8.1 OS. I had installed MS Outlook 2013 Standard. This laptop is joined to the domain like many of my users, however, it keeps prompting for username and password. The emails are still able to send
and receive without any problem.
I have tried to check the connectivity, both cables and wireless are well connected.
I have tried to reinstall the Outlook 2013, but it still occurs.
Attempted to recreate profile but it still occurs.
For the configuration:
I have selected negotiate authentication, and have unchecked the box that states
"Always prompt for login credentials"
Please advise.
Thank you.

Hi,
We can also follow this forum FAQ to troubleshoot this problem:
Why does Outlook keep prompting for password
http://social.technet.microsoft.com/Forums/en-US/bcd2d9c2-1a1b-4446-bf32-69fee8cdf11b/why-does-outlook-keep-prompting-for-password?forum=outlook
Regards,
Melon Chen
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.

Outlook 2013 Continually Prompting For Credentials

After migrating to Office 365 & installing Pro Plus 2013, Outlook 2013 (32-bit) continues to prompt for credentials even though it shows the mailbox as connected to Exchange.
To stop this prompt, I've done the following:
Removed Outlook credentials from credential manager
Removed/recreated Outlook profiles & renamed "outlook" folder found at C:\User\"username"\AppData\Local\Microsoft\ to "Outlook.old" so Outlook will recreate the folder upon restart.
Checked Security tab of "more settings" of the mailbox to make sure "Always prompt for logon credentials" isn't checked.
Please someone give me guidance as to what else the issue could be.

Hello,
How did you set the Logon network security under More Settings on the Microsoft Exchange
Security tab? Please make sure it's not set to a value other than
Anonymous Authentication.
To verify this, please follow these steps:
1. Launch Control Panel.
2. In Control Panel, locate and click
Mail.
3. Click Show Profiles, select your Outlook profile, and click
Properties.
4. Click E-mail Accounts, select
Account Settings and on the E-mail tab, click Change.
5. In the Change Account dialog, click
More Settings.
6. In the Microsoft Exchange dialog, select the
Security tab.
7. From the Login network security
dropdown, select Anonymous Authentication and click
OK.
8. Click Next and click
Finish, and then click Close on the Account Settings dialog.
9. Click Close on the
Mail Setup dialog, and click OK to close the Mail control panel.
Please let me know the result.
Reagrds,
Steve Fan
Forum Support
Come back and mark the replies as answers if they help and unmark them if they provide no help.
If you have any feedback on our support, please click
here

Office Web App Prompting For Credentials Externally Only

We deployed an office web app server and it works great internally, but whenever we try to access documents externally, we are prompted for credentials. Even if we put our credentials in, we always get a 401 forbidden error. Also note that
we can access the hosting/discovery page fine internally, but not externally. Any help is appreciated.

Hi,
According to your description, I think this issue is more related to SharePoint, I suggest that you could post it to
SharePoint forum.
Regards
Starain
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Outlook Anywhere Prompts for Credentials only for Outlook 2010, not Outlook 2013

I'm having a heck of a time with this one. We have Exchange 2010 on premise, with our filtering through EOP. Clients that are using Outlook 2010 Professional Plus are continuously getting prompted for credentials when off network and relying
on Outlook Anywhere.
I've read many threads about configuring credential manager appropriately for the internal domain and our external domain. I can get them to authenticate just fine, and email flows, but they continue to be prompted everytime they connect again.
Here is the kicker: When I install Outlook 2013 on the same computer, outlook anywhere functions just fine, no problems, no authentication prompt.
Like I said I have read a plethera of articles and threads about this, I have gone through all settings on Exchange, our edge server, our firewall, our certificate. The MSSTD string matches our "Issued To" string. NTLM authentication
is configured on both the client and the server. Appropriate settings are configured on the firewalls.
Anyone know why Outlook 2010 would have this problem, but not Outlook 2013 on the same computer, same user, same mailbox database?
Thanks in advance!!!

I'd still Echo Ed's original question.
Do you have Outlook 2010 patched up? At this time you need to be on SP1, and SP2 by October the 14th.
Also I expect you to have a recent update ontop of that as well.
http://blogs.technet.com/b/rmilne/archive/2014/04/14/office-2010-sp2_1320_-do-you-need-to-upgrade_3f00_.aspx
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter:   LinkedIn:
  Facebook:
  XING:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Windows XP Machines Always Prompt for Credentials (Exchange 2013, Outlook 2010)

Similar Messages

Maybe you are looking for