Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 175
  • Last Modified:

Kerberos authentication error accessing local exchange 2010 server

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
CHI-LTD
Asked:
CHI-LTD
  • 2
1 Solution
 
CHI-LTDAuthor Commented:
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
 
CHI-LTDAuthor Commented:
Was credential manager crap causing this
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now