Solved

Kerberos authentication error accessing local exchange 2010 server

Posted on 2016-09-23
2
125 Views
Last Modified: 2016-09-23
Getting the attached.  
I noticed this after a reboot of one of my not so important exchange servers.  
Running powershell i get:

         Welcome to the Exchange Management Shell!

Full list of cmdlets: Get-Command
Only Exchange cmdlets: Get-ExCommand
Cmdlets that match a specific string: Help *<string>*
Get general help: Help
Get help for a cmdlet: Help <cmdlet name> or <cmdlet name> -?
Show quick reference guide: QuickRef
Exchange team blog: Get-ExBlog
Show full output for a command: <command> | Format-List

Tip of the day #21:

Sometimes it's useful to convert the output of a cmdlet to a string to interoperate with native cmdlets. For example, type:

 Get-Mailbox | Out-String | Findstr "Administrator"

VERBOSE: Connecting to exchange.domain.local
New-PSSession : [exchange.domain.local] Connecting to remote server exchange.domain.local failed with the following error message : Logon failure:
unknown user name or bad password. For more information, see the about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotingTransportException
    + FullyQualifiedErrorId : LogonFailure,PSSessionOpenFailed
VERBOSE: Connecting to exchange.domain.local
New-PSSession : [exchange.domain.local] Connecting to remote server exchange.domain.local failed with the following error message : Logon failure:
unknown user name or bad password. For more information, see the about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotingTransportException
    + FullyQualifiedErrorId : LogonFailure,PSSessionOpenFailed
WARNING: No Exchange servers are available in the Active Directory site London. Connecting to an Exchange server in another
Active Directory site.
VERBOSE: Connecting to exchange.domain.local
New-PSSession : [exchange.domain.local] Connecting to remote server exchange.domain.local failed with the following error message : Logon failure:
unknown user name or bad password. For more information, see the about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotingTransportException
    + FullyQualifiedErrorId : LogonFailure,PSSessionOpenFailed
VERBOSE: Connecting to exchange-DR.domain.local
VERBOSE: Connected to exchange-DR.domain.local.
[PS] C:\Windows\system32>(Get-User <administrator>).RemotePowershellEnabled
At line:1 char:11
+ (Get-User <administrator>).RemotePowershellEnabled
+           ~
The '<' operator is reserved for future use.
    + CategoryInfo          : ParserError: (:) [], ParentContainsErrorRecordException
    + FullyQualifiedErrorId : RedirectionNotSupported

[PS] C:\Windows\system32>Get-User <administrator>).RemotePowershellEnabled
At line:1 char:10
+ Get-User <administrator>).RemotePowershellEnabled
+          ~
The '<' operator is reserved for future use.
At line:1 char:25
+ Get-User <administrator>).RemotePowershellEnabled
+                         ~
Unexpected token ')' in expression or statement.
    + CategoryInfo          : ParserError: (:) [], ParentContainsErrorRecordException
    + FullyQualifiedErrorId : RedirectionNotSupported

[PS] C:\Windows\system32>Get-User <administrator>).RemotePowershellEnabled

If i try and connect to the server from another exchange server via EMC it works fine.  ive followed this: https://blogs.technet.microsoft.com/exchange/2010/12/07/resolving-winrm-errors-and-exchange-2010-management-tools-startup-failures/ but not helping..
EMC-Kerberos-1.jpg
EMC-Kerberos-2.jpg
0
Comment
Question by:CHI-LTD
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
2 Comments
 
LVL 1

Author Comment

by:CHI-LTD
ID: 41812432
Windows PowerShell
Copyright (C) 2012 Microsoft Corporation. All rights reserved.

PS C:\Users\administrator.domain> cd .\Desktop
PS C:\Users\administrator.domain\Desktop> .\EMTshooter.ps1

Security warning
Run only scripts that you trust. While scripts from the internet can be useful, this script can potentially harm your
computer. Do you want to run C:\Users\administrator.domain\Desktop\EMTshooter.ps1?
D Do not run  R Run once  S Suspend  ? Help (default is "D"): r

Security warning
Run only scripts that you trust. While scripts from the internet can be useful, this script can potentially harm your
computer. Do you want to run C:\Users\administrator.domain\Desktop\EMTConnectFunctions.ps1?
D Do not run  R Run once  S Suspend  ? Help (default is "D"): r

Security warning
Run only scripts that you trust. While scripts from the internet can be useful, this script can potentially harm your
computer. Do you want to run C:\Users\administrator.domain\Desktop\EMTErrorHandler.ps1?
D Do not run  R Run once  S Suspend  ? Help (default is "D"): r

Welcome to the Exchange Management Troubleshooter!

We recommend that you run the troubleshooter after making changes to
IIS to ensure that connectivity to Exchange Powershell is unaffected.

Checking IIS Service...

Checking the Exchange Install Path variable...

Checking the Powershell Virtual Directory...

Checking the Powershell vdir SSL setting...

Checking the Powershell vdir path setting...

Checking HTTP Port 80...

Checking HTTP Port 80 Host Name...

Testing for errors...

VERBOSE: Connecting to exchange.domain.local


new-pssession : exchange.domain.local Connecting to remote server exchange.domain.local failed with the following error message : Logon failure: unknown user name or bad password. For more information, see the about_Remote_Troubleshooting Help topic.
At C:\Users\administrator.domain\Desktop\EMTConnectFunctions.ps1:177 char:15
+             $session = new-pssession -connectionURI "http://$fqdn/powershell?serializatio ...
+    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) New-PSSession, PSRemotingTransportException
    + FullyQualifiedErrorId : LogonFailure,PSSessionOpenFailed
Exception setting "buffersize": "Cannot set the buffer size because the size specified is too large or too small.
Parameter name: value
Actual value was 120,3000."
At C:\Users\administrator.domain\Desktop\EMTConnectFunctions.ps1:191 char:4
+             $pswindow.buffersize = $newsize
+             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) , SetValueInvocationException
    + FullyQualifiedErrorId : ExceptionWhenSetting

The Exchange Management Troubleshooter successfully completed connecting to:

exchange.domain.local

Failed to connect to any Exchange Server in the current site.
Exception setting "buffersize": "Cannot set the buffer size because the size specified is too large or too small.
Parameter name: value
Actual value was 120,3000."
At C:\Users\administrator.domain\Desktop\EMTErrorHandler.ps1:229 char:2
+     $pswindow.buffersize = $newsize
+     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) , SetValueInvocationException
    + FullyQualifiedErrorId : ExceptionWhenSetting


Problem found:

Looking for error...

Unknown Error

After each error is resolved, close this window and re-run the tool to check for additional problems.

PS C:\Users\administrator.domain\Desktop>
0
 
LVL 1

Accepted Solution

by:
CHI-LTD earned 0 total points
ID: 41812552
Was credential manager crap causing this
0

Featured Post

Turn Insights Into Action

You’ve already invested in ITSM tools, chat applications, automation utilities, and more. Fortify these solutions with intelligent communications so you can drive business processes forward.

With xMatters, you'll never miss a beat.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

My attempt to use PowerShell and other great resources found online to simplify the deployment of Office 365 ProPlus client components to any workstation that needs it, regardless of existing Office components that may be needing attention.
This article describes how to import an Outlook PST file to Office 365 using a third party product to avoid Microsoft's Azure command line tool, saving you time.
Polish reports in Access so they look terrific. Take yourself to another level. Equations, Back Color, Alternate Back Color. Write easy VBA Code. Tighten space to use less pages. Launch report from a menu, considering criteria only when it is filled…
There are cases when e.g. an IT administrator wants to have full access and view into selected mailboxes on Exchange server, directly from his own email account in Outlook or Outlook Web Access. This proves useful when for example administrator want…

696 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question